@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

Replying to an incoming message

Handling incoming SMS/MMS/WhatsApp

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`SMS,WhatsApp,MMSLC, TF, SC	The unique identifier for the message.
`From`SMS,WhatsApp,MMSLC, TF, SC	The source number of the incoming message — the phone number from which the message originated.
`To`SMS,WhatsApp,MMSLC, TF, SC	The Plivo number on which the message was received.
`Text`SMSLC, TF, SC	The content of the message. Note that Plivo automatically concatenates multipart long messages before forwarding them to your `message_url`.
`Body`WhatsApp,MMSLC, TF	The text content (if any) in the multimedia message (MMS). Together, `Body` and `Media` should not exceed 5MB. For WhatsApp, any inbound text content (with or without media) will be populated here.
`Type`SMS, WhatsApp,MMSLC, TF, SC	Allowed values: `sms`, `mms`, `whatsapp` Defaults to sms.
`Units`SMS, MMSLC, TF, SC	The number of parts in which the incoming message was received. This is > 1 for multipart long messages. For `whatsapp`, this is always 1.
`TotalRate`SMS,WhatsApp,MMSLC, TF, SC	The charge applicable per incoming message unit.
`TotalAmount`SMS,WhatsApp,MMSLC, TF, SC	Total charge for receiving the SMS (TotalRate * number of Units)
`MessageIntent`SMSLC, TF	Set to `optout` if the incoming message matches with one of the standard opt-out keywords. Set to `optin` if the incoming message matches with one of the standard opt-in keywords. Set to `help` if the incoming message matches with one of the standard help keywords. Left blank in all other cases.
`PowerpackUUID`SMS, MMSLC, TF, SC	The UUID of the Powerpack associated with the `To` phone number. If the phone number does not belong to a Powerpack, this field is empty.
`MediaCount`MMSLC, TF	The number of media files attached with this MMS message.
`Media<count> ex: Media1, Media2 ...`MMS LC, TF	The URL to a specific media file associated with the MMS message. The integer suffixes range from 1 to the count of media files received.
`ContentType`WhatsAppLC, TF	WhatsApp only attribute Specifies the content type of inbound message. Possible values are `test`, `media`, `unknown`
`MimeType`WhatsAppLC, TF	WhatsApp only attribute Valid for inbound `media` only. Specifies the type of media file. ex: video/mp4
`ErrorCode`WhatsApp,MMSLC, TF	The Plivo error code that identifies the reason for the inbound message delivery failure. This parameter is only defined for “failed” or “undelivered” messages.

​Attributes

​Replying to an incoming message

Attributes

Replying to an incoming message