plivo / plivo-php
A PHP SDK to make voice calls & send SMS using Plivo and to generate Plivo XML
Installs: 2 110 595
Dependents: 20
Suggesters: 4
Security: 0
Stars: 110
Watchers: 48
Forks: 117
Open Issues: 42
Requires
- php: >=7.1.0
- firebase/php-jwt: >=5.2
- guzzlehttp/guzzle: ^6.3 || ^7.0
Requires (Dev)
- justinrainbow/json-schema: ^5.2
- phpunit/phpunit: ^8.1.5
- dev-master
- v4.66.2
- v4.66.1
- v4.66.0
- v4.65.3
- v4.65.2
- v4.65.1
- v4.65.0
- v4.64.0
- v4.63.0
- v4.62.0
- v4.61.0
- v4.60.0
- v4.59.2
- v4.59.1
- v4.59.0
- 4.58.0
- 4.57.1
- v4.57.0
- v4.56.0
- v4.55.0
- v4.54.0
- v4.53.0
- v4.52.0
- v4.51.0
- v4.50.1
- v4.50.0
- v4.48.0
- v4.47.1
- v4.47.0
- v4.46.0
- v4.45.0
- v4.44.2
- v4.44.0
- v4.43.1
- v4.43.0
- v4.42.1
- v4.42.0
- v4.41.0
- v4.40.0
- v4.39.0
- v4.38.0
- v4.37.1
- v4.37.0
- v4.36.1
- v4.36.0
- v4.35.1
- v4.35.0
- v4.34.0
- v4.33.0
- v4.32.0
- v4.31.0
- v4.30.0
- v4.29.0
- v4.28.1
- v4.28.0
- v4.27.2
- v4.27.1
- v4.27.0
- v4.26.0
- v4.25.2
- v4.25.1
- v4.25.0
- v4.24.1
- v4.24.0
- v4.23.0
- v4.21.3
- v4.21.2
- v4.21.1
- v4.21.0
- v4.20.0
- v4.19.2
- v4.19.1
- v4.19.0
- v4.18.3
- v4.18.2
- v4.18.1
- v4.18.0
- v4.17.1
- v4.17.0
- v4.16.0
- v4.15.1
- v4.15.0
- v4.14.0
- v4.13.0
- v4.12.0
- v4.11.1
- v4.11.0
- v4.10.0
- v4.9.1
- v4.9.0
- v4.8.1
- v4.8.0
- v4.7.1
- v4.7.0
- v4.6.0
- v4.5.0
- v4.4.2
- v4.4.1
- v4.4.0
- v4.3.9
- v4.3.8
- v4.3.7
- v4.3.6
- v4.3.5
- v4.3.4
- v4.3.3
- v4.3.2
- v4.3.1
- v4.3.0
- v4.2-beta1
- v4.1.5
- v4.1.4
- v4.1.3
- v4.1.2
- v4.1.1
- v4.1.0
- v4.0.0
- v4.0.0-beta1
- v1.1.7
- v1.1.6
- v1.1.5
- v1.1.4
- v1.1.3
- v1.1.2
- v1.1.1
- v1.1.0
- v1.0.1
- v1.0.0
- v1.0.0-rc
- dev-VT-8202
- dev-PHONUM-3795
- dev-update_date_sms-6930
- dev-SMS-6066-message-sdks
- dev-PHONUM-2893_corrected
- dev-PHONUM-2893
- dev-PHONUM-2833
- dev-VT-5270
- dev-fix-tests
- dev-php-version
- dev-php_version
- dev-issue-278
- dev-localTestingBranch
- dev-SUP-2788
- dev-VT-3661
- dev-VT-3652
- dev-add_exeption_handling
- dev-test_auth_failure
- dev-ns_build_fix
- dev-revert-202-PHONUM-1734
- dev-regulatory
- dev-testlocal
- dev-testrc
- dev-retrieve_phlo_run
- dev-upgrade_guzzle_pacakge
- dev-mms-powerpack
- dev-fix-empty-requestbody
- dev-mms-bug-fix
- dev-VT-1641-app-cascade-delete
- dev-tollfree-sdk-fix
- dev-post-feedback
- dev-dtmf_fix
- dev-upload_api
- dev-mms-support
- dev-mms_powerpack_release
- dev-get-input
- dev-SSML_feature
- dev-invalid_number_sms
- dev-FixMessageInterface
- dev-phone_number_validation
- dev-build-container
- dev-ci
- dev-voice_number_validation
- dev-validation
- dev-validation_review
- dev-StatusCode
- dev-fix_messageCreate_response
- dev-revert_response
- dev-beta
- dev-nov_2018_release
- dev-oct_2018_release
- dev-feature-hangup-party
- dev-feature-queued-call
This package is auto-updated.
Last update: 2024-10-23 06:27:11 UTC
README
The Plivo PHP SDK makes it simpler to integrate communications into your PHP applications using the Plivo REST API. Using the SDK, you will be able to make voice calls, send SMS and generate Plivo XML to control your call flows.
Supported PHP Versions: This SDK works with PHP 7.3+.
Installation
To install Composer
Globally in Mac
-
Download the latest version of Composer.
-
Run the following command in Terminal:
$ php ~/Downloads/composer.phar --version
-
Run the following command to make it executable:
$ cp ~/Downloads/composer.phar /usr/local/bin/composer $ sudo chmod +x /usr/local/bin/composer $ Make sure you move the file to bin directory.
-
To check if the path has /usr/local/bin, use
$ echo $PATH
If the path is different, use the following command to update the $PATH:
$ export PATH = $PATH:/usr/local/bin $ source ~/.bash_profile
-
You can also check the version of Composer by running the following command:
$ composer --version.
Globally in Linux
-
Run the following command:
$ curl -sS https://getcomposer.org/installer | php
-
Run the following command to make the composer.phar file as executable:
$ chmod +x composer.phar
-
Run the following command to make Composer globally available for all system users:
$ mv composer.phar /usr/local/bin/composer
Windows 10
-
Download and run the Windows Installer for Composer.
Note: Make sure to allow Windows Installer for Composer to make changes to your php.ini file.
-
If you have any terminal windows open, close all instances and open a fresh terminal instance.
-
Run the Composer command.
$ composer -V
Steps to install Plivo Package
-
To install the stable release, run the following command in the project directory:
$ composer require plivo/plivo-php
-
To install a specific release, run the following command in the project directory:
$ composer require plivo/plivo-php:4.14.0
-
To test the features in the beta release, run the following command in the project directory:
$ composer require plivo/plivo-php:v4.2-beta1
-
Alternatively, you can download this source and run
$ composer install
This generates the autoload files, which you can include using the following line in your PHP source code to start using the SDK.
<?php require 'vendor/autoload.php'
Getting started
Authentication
To make the API requests, you need to create a RestClient
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:
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient();
Alternatively, you can specifiy the authentication credentials while initializing the RestClient
.
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<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:
<?php $client->resources->create($params) # Create $client->resources->get($id) # Get $client->resources->update($id, $params) # Update $client->resources->delete($id) # Delete $client->resources->list() # List all resources, max 20 at a time
You can also use the resource
directly to update and delete it. For example,
<?php $resource = $client->resources->get($id) $resource->update($params) # update the resource $resource->delete() # Delete the resource
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
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient(); $message_created = $client->messages->create([ "src" => "+14156667778", "dst" => "+14156667777", "text" =>"Hello, this is a sample text from Plivo" ]);
Make a call
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient(); $call_made = $client->calls->create( '+14156667778', ['+14156667777'], 'https://answer.url' );
Lookup a number
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>", "<auth_token>"); $response = $client->lookup->get("<number-goes-here>");
Generate Plivo XML
<?php require 'vendor/autoload.php'; use Plivo\XML\Response; $response = new Response(); $response->addSpeak('Hello, world!'); echo($response->toXML());
This generates the following XML:
<?xml version="1.0" encoding="utf-8"?> <Response> <Speak>Hello, world!</Speak> </Response>
Run a PHLO
<?php /** * Example for API Request */ require 'vendor/autoload.php'; use Plivo\Resources\PHLO\PhloRestClient; use Plivo\Exceptions\PlivoRestException; $client = new PhloRestClient("<auth_id>", "<auth_token>"); $phlo = $client->phlo->get("<phlo_id>"); try { $response = $phlo->run(["field1" => "value1", "field2" => "value2"]); // These are the fields entered in the PHLO console print_r($response); } catch (PlivoRestException $ex) { print_r($ex); } ?>
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:
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $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" } ] } ] }'; $response = $client->messages->create([ "src" => "+14156667778", "dst" => "+14156667777", "type"=> "whatsapp", "template"=> $template, "url"=> "https://foo.com/wa_status/" ]); print_r($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:
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "text"=> "Hello, this is sample text", "type"=> "whatsapp", "url"=> "https://foo.com/wa_status/" ]); print_r($response); ?>
Free Form Media Message
Example:
<?php require 'vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "text"=> "Hello, this is sample text", "type"=> "whatsapp", "media_urls"=> ["https://sample-videos.com/img/Sample-png-image-1mb.png"], "url"=> "https://foo.com/wa_status/" ]); print_r($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:
<?php require '/usr/src/app/vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $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" } ] } }'; $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "type"=> "whatsapp", "interactive"=> $interactive ]); print_r($response); ?>
Interactive Lists
Interactive lists allow you to present customers with a list of options.
Example:
<?php require '/usr/src/app/vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $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" } ] } ] } }'; $response = $client->messages->create( [ "src"=> "+14156667778", "dst"=> "+14156667777", "type"=> "whatsapp", "interactive"=> $interactive ] ); print_r($response); ?>
Interactive CTA URLs
CTA URL messages allow you to send links and call-to-action buttons.
Example:
<?php require '/usr/src/app/vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $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" } ] } }'; $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "type"=> "whatsapp", "interactive"=> $interactive ]); print_r($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:
<?php require '/usr/src/app/vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $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" } } ] } ] }'; $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "type"=> "whatsapp", "template"=> $template ]); print_r($response); ?>
Non-Templated Location Messages
Example:
<?php require '/usr/src/app/vendor/autoload.php'; use Plivo\RestClient; $client = new RestClient("<auth_id>","<auth_token>"); $location = '{ "longitude": "122.148981", "latitude": "37.483307", "name": "Pablo Morales", "address": "1 Hacker Way, Menlo Park, CA 94025" }'; $response = $client->messages->create([ "src"=> "+14156667778", "dst"=> "+14156667777", "type"=> "whatsapp", "location"=> $location ]); print_r($response); ?>
More examples
More examples are available here. Also refer to the guides for configuring the PHP laravel 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.
- 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>
- 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.
- The above command will print the docker container id (and instructions to connect to it) to stdout.
- The testing code can be added to
<sdk_dir_path>/php-sdk-test/test.php
in host
(or/usr/src/app/php-sdk-test/test.php
in container) - 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.
To use the local code in the test file, import the sdk in test file using:
require /usr/src/app/vendor/autoload.php
(Local sdk code will be mounted at/usr/src/app
inside the container andvendor
directory will be created by setup script while installing dependencies).
- To run test code, run
make run CONTAINER=<cont_id>
in host. - 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
andmake test
respectively. (CONTAINER
argument should be omitted when running from the container)