plivo vs messagebird vs nexmo vs twilio
SMS and Communication APIs
plivomessagebirdnexmotwilioSimilar Packages:

SMS and Communication APIs

SMS and communication APIs are essential tools for developers looking to integrate messaging, voice, and video capabilities into their applications. These packages provide robust solutions for sending SMS, making voice calls, and enabling real-time communication features. They are designed to simplify the process of connecting with users through various channels, offering scalability, reliability, and ease of use. Each package comes with its unique features, pricing models, and target use cases, making it crucial for developers to choose the right one based on their specific needs.

Npm Package Weekly Downloads Trend

3 Years

Github Stars Ranking

Stat Detail

Package
Downloads
Stars
Size
Issues
Publish
License
plivo29,197103954 kB4213 days agoMIT
messagebird0109244 kB253 years agoBSD-2-Clause
nexmo041494 kB1-MIT
twilio01,51815.2 MB5213 days agoMIT

Feature Comparison: plivo vs messagebird vs nexmo vs twilio

Multi-Channel Support

  • plivo:

    Plivo offers SMS and voice capabilities but lacks support for email and chat channels. It is best suited for businesses focused on these two communication methods.

  • messagebird:

    MessageBird excels in providing multi-channel communication options, including SMS, voice, chat, and email. This allows businesses to reach customers through their preferred channels, enhancing engagement and customer experience.

  • nexmo:

    Nexmo primarily focuses on SMS and voice services but also offers some support for chat applications. While it may not be as versatile as others, it provides reliable messaging capabilities.

  • twilio:

    Twilio stands out with its extensive multi-channel support, covering SMS, voice, video, chat, and even email. This makes it a go-to choice for businesses needing a comprehensive communication strategy.

Ease of Integration

  • plivo:

    Plivo is designed for quick integration, with a simple API and comprehensive documentation. It also offers SDKs that help developers get started quickly.

  • messagebird:

    MessageBird provides a user-friendly API with clear documentation and SDKs for various programming languages, making integration straightforward for developers of all skill levels.

  • nexmo:

    Nexmo offers a well-documented API that is easy to integrate, with numerous code samples and libraries available, facilitating a smooth onboarding process for developers.

  • twilio:

    Twilio is known for its exceptional documentation and extensive resources, including tutorials and sample applications, making it one of the easiest platforms to integrate into existing applications.

Pricing Model

  • plivo:

    Plivo is known for its cost-effective pricing, especially for high-volume SMS and voice services. It provides transparent pricing that helps businesses budget effectively.

  • messagebird:

    MessageBird employs a pay-as-you-go pricing model, with costs varying based on the destination and type of message. This flexibility allows businesses to manage costs effectively as they scale.

  • nexmo:

    Nexmo offers competitive pricing for SMS and voice services, with a straightforward pay-as-you-go model. This makes it accessible for startups and small businesses looking to control costs.

  • twilio:

    Twilio's pricing is based on usage, with different rates for SMS, voice, and other services. While it can be more expensive than some alternatives, its extensive features often justify the cost.

Global Reach

  • plivo:

    Plivo offers global SMS and voice services, but its coverage may not be as extensive as some competitors. It is best suited for businesses targeting specific regions.

  • messagebird:

    MessageBird boasts a strong global presence, allowing businesses to send messages to over 200 countries. Its extensive network ensures reliable delivery and compliance with local regulations.

  • nexmo:

    Nexmo provides global coverage for SMS and voice services, making it suitable for businesses with an international customer base. It also offers local numbers in various countries.

  • twilio:

    Twilio has an extensive global reach, supporting messaging and voice services in numerous countries. Its infrastructure is designed for high reliability and compliance with local laws.

Customer Support

  • plivo:

    Plivo offers customer support primarily through email and documentation. While responsive, it may not provide the same level of personalized support as some competitors.

  • messagebird:

    MessageBird offers robust customer support, including live chat and dedicated account managers for enterprise clients. Their support team is known for being responsive and helpful.

  • nexmo:

    Nexmo provides solid customer support through various channels, including email and chat. Their documentation is also comprehensive, helping users troubleshoot issues independently.

  • twilio:

    Twilio is renowned for its excellent customer support, offering multiple channels for assistance, including phone support for enterprise customers. Their community forums and extensive documentation also provide valuable resources.

How to Choose: plivo vs messagebird vs nexmo vs twilio

  • plivo:

    Opt for Plivo if you require a cost-effective solution with a focus on voice and SMS capabilities. Plivo is known for its competitive pricing and ease of integration, making it a good choice for businesses looking to scale their communication needs without breaking the bank.

  • messagebird:

    Choose MessageBird if you need a versatile platform that supports multiple communication channels beyond SMS, including voice, chat, and email. It is ideal for businesses looking for a unified communication solution with global reach and strong customer support.

  • nexmo:

    Select Nexmo (now part of Vonage) if you prioritize a strong focus on SMS and voice services with a developer-friendly API. It offers excellent documentation and a straightforward pricing model, making it suitable for startups and small businesses.

  • twilio:

    Choose Twilio if you want a comprehensive and highly customizable communication platform with extensive features. Twilio offers a wide range of APIs for SMS, voice, video, and more, making it suitable for complex applications that require advanced functionalities.

README for plivo

Plivo Node.js library

Version codecov UnitTests

The Node.js SDK simplifies the integration of communications into your Node.js applications through the Plivo REST API. You will be able to use the SDK to make voice calls, send SMS, and generate Plivo XML to manage your call flows.

Installation

Install the SDK using npm

$ npm install plivo

If you have the 0.4.1 version (a.k.a legacy) already installed, you may have to first uninstall it before installing the new version.

For features in beta, use the beta branch:

$ npm install plivo@beta

Getting started

Authentication

To make the API requests, you need to create a Client and provide it with authentication credentials (which can be found at https://console.plivo.com/dashboard/).

We recommend that you store your credentials in the PLIVO_AUTH_ID and the PLIVO_AUTH_TOKEN environment variables, so as to avoid the possibility of accidentally committing them to source control. If you do this, you can initialise the client with no arguments and it will automatically fetch them from the environment variables:

let plivo = require('plivo');
let client = new plivo.Client();

Alternatively, you can specifiy the authentication credentials while initializing the Client.

let plivo = require('plivo');
let client = new plivo.Client('<auth_id>', '<auth_token>');

The basics

The SDK uses consistent interfaces to create, retrieve, update, delete and list resources. The pattern followed is as follows:

client.resources.create(name,params); // Create
client.resources.get(id); // Get
client.resources.update(params); // Update
client.resources.delete(id); // Delete
client.resources.list({limit:5,offset:0}); // List all resources, max 20 at a time

Also, using client.resources.list() would list the first 20 resources by default (which is the first page, with limit as 20, and offset as 0). To get more, you will have to use limit and offset to get the second page of resources.

Examples

Send a message

let plivo = require('plivo');
let client = new plivo.Client();

client.messages.create({
    src: '+14156667778',
    dst: '14156667777',
    text: 'Hello, this is a sample text from Plivo',
}).then(function(response) {
    console.log(response)
});

Make a call

let plivo = require('plivo');
let client = new plivo.Client();

client.calls.create(
  '+14156667778',
  '+14156667777',
  'http://answer.url'
).then(function(response) {
  console.log(response)
});

Lookup a number

let plivo = require('plivo');
let client = new plivo.Client('<auth_id>', '<auth_token>');

client.lookup.get('<number-goes-here>')
.then(function(response) {
    console.log(response);
});

Generate Plivo XML

let plivo = require('plivo');
let response = new plivo.Response();
let speak_body = "Hello, world!";

response.addSpeak(speak_body);
console.log(response.toXML());

This generates the following XML:

<Response>
  <Speak>Hello, world!</Speak>
</Response>

Run a PHLO

let plivo = require('plivo');
var PhloClient = plivo.PhloClient;
var phloClient = phlo = null;

phloClient = new PhloClient('<auth-id>', '<auth-token>');
phloClient.phlo('<phlo_id>').run().then(function (result) {
console.log('Phlo run result', result);
});

WhatsApp Messaging

Plivo's WhatsApp API allows you to send different types of messages over WhatsApp, including templated messages, free form messages and interactive messages. Below are some examples on how to use the Plivo Go SDK to send these types of messages.

Templated Messages

Templated messages are a crucial to your WhatsApp messaging experience, as businesses can only initiate WhatsApp conversation with their customers using templated messages.

WhatsApp templates support 4 components: header , body, footer and button. At the point of sending messages, the template object you see in the code acts as a way to pass the dynamic values within these components. header can accomodate text or media (images, video, documents) content. body can accomodate text content. button can support dynamic values in a url button or to specify a developer-defined payload which will be returned when the WhatsApp user clicks on the quick_reply button. footer cannot have any dynamic variables.

Example:

var plivo = require('plivo');

var client = new plivo.Client("<auth_id>", "<auth_token>");

const template = { 
            "name": "template_name",
            "language": "en_US",
            "components": [
                {
                    "type": "header",
                    "parameters": [
                        {
                            "type": "media",
                            "media": "https://xyz.com/s3/img.jpg"
                        }
                    ]
                },
                {
                    "type": "body",
                    "parameters": [
                        {
                            "type": "text",
                            "text": "WA-Text"
                        }
                    ]
                }
            ]
          }
client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  template:template,
  url: "https://foo.com/wa_status/"
}).then(function (response) {
  console.log(response);
});

Templated WhatsApp Messages With Named Parameter

This guide shows how to send templated WhatsApp messages with named parameters.

Example:

var plivo = require('plivo');

var client = new plivo.Client("<auth_id>", "<auth_token>");

const template = { 
            "name": "template_name",
            "language": "en_US",
            "components": [
                {
                    "type": "header",
                    "parameters": [
                        {
                            "type": "text",
                            "parameter_name": "header_title",
                            "text": "WA-header"
                        }
                    ]
                },
                {
                    "type": "body",
                    "parameters": [
                        {
                            "type": "text",
                            "parameter_name": "user_name",
                            "text": "Saurabh"
                        }
                    ]
                }
            ]
          }
client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  template:template,
  url: "https://foo.com/wa_status/"
}).then(function (response) {
  console.log(response);
});

Free Form Messages

Non-templated or Free Form WhatsApp messages can be sent as a reply to a user-initiated conversation (Service conversation) or if there is an existing ongoing conversation created previously by sending a templated WhatsApp message.

Free Form Text Message

Example:

var plivo = require('plivo');

var client = new plivo.Client("<auth_id>", "<auth_token>");
client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  text: "Hello, this is sample text",
  url: "https://foo.com/wa_status/"
}).then(function (response) {
  console.log(response);
});

Free Form Media Message

Example:

var plivo = require('plivo');

var client = new plivo.Client("<auth_id>", "<auth_token>");
client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  text: "Hello, this is sample text",
  media_urls:["https://sample-videos.com/img/Sample-png-image-1mb.png"],
  url: "https://foo.com/wa_status/"
}).then(function (response) {
  console.log(response);
});

Interactive Messages

This guide shows how to send non-templated interactive messages to recipients using Plivo’s APIs.

Quick Reply Buttons

Quick reply buttons allow customers to quickly respond to your message with predefined options.

Example:

let plivo = require('plivo');

var client = new plivo.Client("<auth_id>","<auth_token>");

const interactive = {
        "type": "button",
        "header": {
            "type": "media",
            "media": "https://xyz.com/s3/img.jpg"
        },
        "body": {
            "text": "Make your selection"
        },
        "action": {
            "buttons": [
                {
                    "title": "Click here",
                    "id": "bt1"
                },
                {
                    "title": "Know More",
                    "id": "bt2"
                },
                {
                    "title": "Request Callback",
                    "id": "bt3"
                }
            ]
        }
    }

client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  interactive:interactive
}).then(function (response) {
  console.log(response);
});

Interactive Lists

Interactive lists allow you to present customers with a list of options.

Example:

let plivo = require('plivo');

var client = new plivo.Client("<auth_id>","<auth_token>");

const interactive = {
        "type": "list",
        "header": {
            "type": "text",
            "text": "Welcome to Plivo"
        },
        "body": {
            "text": "You can review the list of rewards we offer"
        },
        "footer": {
            "text": "Yours Truly"
        },
        "action": {
            "buttons": [{
                "title": "Click here"
            }],
            "sections": [
                {
                    "title": "SECTION_1_TITLE",
                    "rows": [
                        {
                            "id": "SECTION_1_ROW_1_ID",
                            "title": "SECTION_1_ROW_1_TITLE",
                            "description": "SECTION_1_ROW_1_DESCRIPTION"
                        },
                        {
                            "id": "SECTION_1_ROW_2_ID",
                            "title": "SECTION_1_ROW_2_TITLE",
                            "description": "SECTION_1_ROW_2_DESCRIPTION"
                        }
                    ]
                },
                {
                    "title": "SECTION_2_TITLE",
                    "rows": [
                        {
                            "id": "SECTION_2_ROW_1_ID",
                            "title": "SECTION_2_ROW_1_TITLE",
                            "description": "SECTION_2_ROW_1_DESCRIPTION"
                        },
                        {
                            "id": "SECTION_2_ROW_2_ID",
                            "title": "SECTION_2_ROW_2_TITLE",
                            "description": "SECTION_2_ROW_2_DESCRIPTION"
                        }
                    ]
                }
            ]
        }
    }

client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  interactive:interactive
}).then(function (response) {
  console.log(response);
});

Interactive CTA URLs

CTA URL messages allow you to send links and call-to-action buttons.

Example:

let plivo = require('plivo');

var client = new plivo.Client("<auth_id>","<auth_token>");

const interactive = {
        "type": "cta_url",
        "header": {
            "type": "media",
            "media": "https://xyz.com/s3/img.jpg"
        },
        "body": {
            "text": "Know More"
        },
        "footer": {
            "text": "Plivo"
        },
        "action": {
            "buttons": [
                {
                    "title": "Click here",
                    "cta_url": "https:plivo.com"
                }
            ]
        }
    }

client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  interactive:interactive
}).then(function (response) {
  console.log(response);
});

Location Messages

This guide shows how to send templated and non-templated location messages to recipients using Plivo’s APIs.

Templated Location Messages

Example:

let plivo = require('plivo');

var client = new plivo.Client("<auth_id>","<auth_token>");

const template = {
        "name": "plivo_order_pickup",
        "language": "en_US",
        "components": [
            {
                "type": "header",
                "parameters": [
                    {
                        "type": "location",
                        "location": {
                            "longitude": "122.148981",
                            "latitude": "37.483307",
                            "name": "Pablo Morales",
                            "address": "1 Hacker Way, Menlo Park, CA 94025"
                        }
                    }
                ]
            }
        ]
    }

client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  template:template
}).then(function (response) {
  console.log(response);
});

Non-Templated Location Messages

Example:

let plivo = require('plivo');

var client = new plivo.Client("<auth_id>","<auth_token>");

const location = {
        "longitude": "122.148981",
        "latitude": "37.483307",
        "name": "Pablo Morales",
        "address": "1 Hacker Way, Menlo Park, CA 94025"
    }

client.messages.create({
  src:"+14156667778",
  dst:"+14156667777",
  type:"whatsapp",
  location:location
}).then(function (response) {
  console.log(response);
});

More examples

More examples are available here. Also refer to the guides for configuring the Express server to run various scenarios & use it to test out your integration in under 5 minutes.

Reporting issues

Report any feedback or problems with this version by opening an issue on Github.

Local Development

Note: Requires latest versions of Docker & Docker-Compose. If you're on MacOS, ensure Docker Desktop is running.

  1. Export the following environment variables in your host machine:
export PLIVO_AUTH_ID=<your_auth_id>
export PLIVO_AUTH_TOKEN=<your_auth_token>
export PLIVO_API_DEV_HOST=<plivoapi_dev_endpoint>
export PLIVO_API_PROD_HOST=<plivoapi_public_endpoint>
  1. Run make build. This will create a docker container in which the sdk will be setup and dependencies will be installed.

The entrypoint of the docker container will be the setup_sdk.sh script. The script will handle all the necessary changes required for local development. It will also package the sdk and reinstall it as a dependecy for the test program.

  1. The above command will print the docker container id (and instructions to connect to it) to stdout.
  2. The testing code can be added to <sdk_dir_path>/node-sdk-test/test.js in host
    (or /usr/src/app/node-sdk-test/test.js in container)
  3. The sdk directory will be mounted as a volume in the container. So any changes in the sdk code will also be reflected inside the container. However, when any change is made, the dependencies for the test program need to be re-installed. To do that:
    • Either restart the docker container
    • Or Run the setup_sdk.sh script
  4. To run test code, run make run CONTAINER=<cont_id> in host.
  5. To run unit tests, run make test CONTAINER=<cont_id> in host.

<cont_id> is the docker container id created in 2. (The docker container should be running)

Test code and unit tests can also be run within the container using make run and make test respectively. (CONTAINER argument should be omitted when running from the container)