@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 Statuses

Toll-free verification statuses

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

TF verification status	Description
SUBMITTED	The carrier has accepted the submission and is reviewing the request.
APPROVED	TThe request has been verified by the carrier.
REJECTED	The carrier has rejected the toll-free verification request. The use case cannot be submitted for verification anymore.
UPDATE_REQUIRED	Verification submission has been put on hold and the carrier has requested additional data to validate the request. You need to provide this additional information via the Update API request. If you do not provide details within six days from when the status is posted, the open request will be closed and the toll-free verification status will change to REJECTED.