@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;
}

Toll-free Verification Object

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

uuid string	The unique identifier for the verification request.
profile_uuid string	The unique identifier of an existing Plivo profile.
number string	The toll-free number for which verification is being initiated.
usecase list	The messaging use case(s) for which the toll-free number will be used. This should be set as one or more of the following options: 2FA ACCOUNT_NOTIFICATION CUSTOMER_CARE DELIVERY_NOTIFICATION FRAUD_ALERT HIGHER_EDUCATION MARKETING POLLING_VOTING PUBLIC_SERVICE_ANNOUNCEMENT SECURITY_ALERT One use case is mandatory. Multiple use cases can be added as a list of strings.
usecase_summary string	The explanation of how messaging will be used on the toll-free phone number(s) by your business.
message_sample string	Sample message(s) that your business will send to the end-user/mobile device. Multiple sample messages are allowed.
optin_image_url list	A valid URL where you submit images explaining details of the opt-in process for the end user. Multiple URLs are allowed as a list of strings. Note: This URL should align with the details added to the optin_type.
optin_type string	Describes how a user opts into receiving text messages. One of the following exact values should be provided: VERBAL WEB_FORM PAPER_FORM VIA_TEXT MOBILE_QR_CODE -VERBAL must include the sample verbal consent collection and examples in a document linked in the optin_image_url parameter. -WEB_FORM must include the link to the form in the optin_image_url parameter. -PAPER_FORM must include a link to the form in the optin_image_url parameter. It can be a scanned image. -VIA_TEXT must describe the keyword campaign in a document linked in the optin_image_url parameter. -MOBILE_QR_CODE must include the QR code in a document linked in the optin_image_url parameter. The sample submitted in the opt-in_image_url parameter should match the opt-in type selection.
volume string	An estimate of the monthly volume of messages you will send from the toll-free number. One of the following exact values should be provided: 1,000 10,000 100,000 250,000 500,000 750,000 1,000,000 5,000,000 10,000,000+ If your monthly volumes are expected to increase, it is advisable to provide a value that accommodates the projected growth and remains suitable for the next six to eight months.
additional_information string	Any additional information related to the website, such as a link to the terms of service (TOS) page or privacy policy, that can help clarify the verification request.
extra_data string	Any additional information that you would like to include for your own internal reference.
status string	The status of the toll-free verification request.
rejection_reason string	The reason for toll-free verification rejection.
callback_url string	A valid URL where verification-related callbacks will be sent.
created datetime	The date when the verification request was created.
last_modified datetime	The date when the verification request was last modified.