@font-face {
  font-family: 'Sora';
  src: url('https://cdn.jsdelivr.net/npm/@fontsource/sora@5.0.18/files/sora-latin-600-normal.woff2') format('woff2');
  font-weight: 600;
  font-style: normal;
  font-display: swap;
}

h1,
h2,
h3{
  font-family: 'Sora';
  letter-spacing: normal !important;
}

#integrately-embed {
  width: 40rem !important;
  margin: 2rem auto !important;
  max-width: 100% !important;
}

Attributes

Message Status Callbacks

Plivo

Overview

Number Porting

Plivo’s Quick Guide to Number Porting

PHP Quickstart

Get Started with PHP Using PHP Server

Plivo APIs are packaged and ready to use with Postman, an API testing tool that helps developers set up, test, and explore APIs.

Postman Collections

Get Started Using Postman Collections for Plivo SMS APIs

Programmatically interact with your customers globally over SMS using the Plivo SMS Platform.

These are some of the key features of the Plivo SMS Platform.

Supported Features

Here are some terms used throughout the Plivo documentation pages:

Terminology

SMS messaging in the US is governed by the [CTIA](https://www.ctia.org/). Strict rules are in place to regulate US messaging, which makes the right SMS implementation a deceptively challenging experience. This guide outlines the best practices to ensure your messaging is in compliance with regulatory and industry standards.

US and Canada Messaging

High-quality, well-formatted content is more likely to be opened and less likely to be mistaken as spam by consumers, operators, and carriers. Follow these guidelines to make sure your SMS content meets the standards for great messaging.

US Messaging Best Practices

Best Practices for A2P Messaging in the US

Get Started Using Postman Collections for Plivo Voice APIs

Plivo’s voice API platform lets you integrate voice calling into your applications

Here are some of the key features Plivo’s Voice API platform supports.

Features

Example section for showcasing API endpoints

Introduction

Returns all plants from the system that the user has access to

Get Plants

Create Plant

Deletes a single plant based on the ID supplied

`MessageUUID`	The unique ID for the message.
`To`	Phone number of the recipient.
`From`	The sender ID used as the source address for the message.
`Type`	The type of message. Allowed values: `sms`, `mms` ,`whatsapp`
`Status`	Status of the message. Allows values: `queued`, `sent`, `failed`, `delivered`, `undelivered`, `read` (WhatsApp only)
`Units`	Number of units into which a long SMS message was split.
`TotalRate`	The charge applicable per outbound SMS unit.
`TotalAmount`	Total charge for sending the SMS (TotalRate * number of Units)
`MCC`	Mobile Country Code of the To number.
`MNC`	Mobile Network Code of the To number. (See here for more details)
`ErrorCode`	The Plivo error code that identifies the reason for the message delivery failure. This parameter is only defined for “failed” or “undelivered” messages.
`ParentMessageUUID`reserved for future use	Same as the `MessageUUID`. This parameter is reserved for future use, and should be ignored for now.
`PartInfo`reserved for future use	This parameter is reserved for future use, and should be ignored for now.
`Sequence`	Use this attribute to track the sequence in which callbacks for this SMS were generated by the Plivo system.
`MessageTime`	The timestamp at which the SMS was initiated. Format: YYYY-mm-dd HH:MM:SS.SSSSSS
`QueuedTime`	The timestamp at which the SMS was queued. Format: YYYY-mm-dd HH:MM:SS.SSSSSS
`SentTime`	The timestamp at which the SMS was submitted to the downstream carrier for delivery. Format: YYYY-mm-dd HH:MM:SS.SSSSSS
`DeliveryReportTime`	The timestamp at which the delivery report for this SMS was received from the downstream carrier. Format: YYYY-mm-dd HH:MM:SS.SSSSSS
`requester_ip`	The IP address from which the message request originated. We recommend you monitor this field to identify possible account misuse and authentication credential takeovers.
`PowerpackUUID`	The SMS Powerpack UUID used for the message. This will be empty if a Powerpack was not used.
`ConversationExpirationTimestamp`	WhatsApp only attribute. Timestamp (Unix) when the current ongoing conversation expires.
`ConversationOrigin`	WhatsApp only attribute. Possible values: `utility`, `authentication`, `marketing`, `service` Describes how the WhatsApp conversation was initiated. This is determined if the conversation was initiated by a business or by user. `service` conversations are initiated when a user sends a message to the business. `utility` ,`authentication` , `marketing` conversations are initiated when a business sends the message to their users using a templates of category: `utility` ,`authentication` , `marketing` respectively
`ConversationID`	WhatsApp only attribute. Represents a unique identifier ID for a conversation to which the message belongs to. Can be null for inbound messages.

​Attributes

Attributes