Download the PHP package plivo/plivo-php without Composer

plivo-php

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

1. Download the latest version of Composer.

2. Run the following command in Terminal:

   $ php ~/Downloads/composer.phar --version

3. 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.

4. 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 

5. You can also check the version of Composer by running the following command:

   $ composer --version.       

Globally in Linux

1. Run the following command:

   $ curl -sS https://getcomposer.org/installer | php

2. Run the following command to make the composer.phar file as executable:

   $ chmod +x composer.phar

3. Run the following command to make Composer globally available for all system users:

   $ mv composer.phar /usr/local/bin/composer

Windows 10

1. 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.

2. If you have any terminal windows open, close all instances and open a fresh terminal instance.

3. 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.

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:

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

The Basics

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

You can also use the resource directly to update and delete it. For example,

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

Make a call

Lookup a number

Generate Plivo XML

This generates the following XML:

Run a PHLO

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:

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:

Free Form Media Message

Example:

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:

Interactive Lists

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

Example:

Interactive CTA URLs

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

Example:

Location Messages

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

Templated Location Messages

Example:

Non-Templated Location Messages

Example:

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.

1. Export the following environment variables in your host machine:

2. 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.

3. The above command will print the docker container id (and instructions to connect to it) to stdout.
4. 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)
5. 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 and vendor directory will be created by setup script while installing dependencies).

6. To run test code, run make run CONTAINER=<cont_id> in host.
7. 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)