Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
@indigov/plivo
Advanced tools
A Node.js SDK to make voice calls and send SMS using Plivo and to generate Plivo XML
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.
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
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 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.
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)
});
let plivo = require('plivo');
let client = new plivo.Client();
client.calls.create(
'+14156667778',
'+14156667777',
'http://answer.url'
).then(function(response) {
console.log(response)
});
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);
});
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>
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);
});
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.
Report any feedback or problems with this version by opening an issue on Github.
Note: Requires latest versions of Docker & Docker-Compose. If you're on MacOS, ensure Docker Desktop is running.
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>
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.
<sdk_dir_path>/node-sdk-test/test.js
in host/usr/src/app/node-sdk-test/test.js
in container)setup_sdk.sh
scriptmake run CONTAINER=<cont_id>
in host.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
andmake test
respectively. (CONTAINER
argument should be omitted when running from the container)
FAQs
A Node.js SDK to make voice calls and send SMS using Plivo and to generate Plivo XML
The npm package @indigov/plivo receives a total of 2 weekly downloads. As such, @indigov/plivo popularity was classified as not popular.
We found that @indigov/plivo demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 14 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.