As of November 8, 2023, unverified toll-free numbers cannot send messages to users in the US and Canada. These messages will be rejected by carriers.
API Endpoint
Base URL
Use Cases
The following use cases are supported for toll-free verification:| Use Case | Description |
|---|---|
| 2FA | Two-factor authentication with passcodes used to unlock accounts |
| ACCOUNT_NOTIFICATION | Notifications sent to account holders about account changes |
| CUSTOMER_CARE | Customer care interactions by support and customer-facing teams |
| DELIVERY_NOTIFICATION | Updates about delivery of products and services |
| FRAUD_ALERT | Notifications of suspicious behavior identified by the business |
| HIGHER_EDUCATION | Messages sent by colleges, universities, and educational institutions |
| MARKETING | Communications related to time-bound events and sales |
| POLLING_VOTING | Surveys, polling, and voting campaigns for non-political purposes |
| PUBLIC_SERVICE_ANNOUNCEMENT | Messages aimed at creating awareness about important topics |
| SECURITY_ALERT | Notifications that alert users about potential security breaches |
Opt-in Types
You must specify how users consent to receive messages:| Opt-in Type | Requirements |
|---|---|
| VERBAL | Include sample verbal consent collection in a document linked via optin_image_url |
| WEB_FORM | Include link to the web form in optin_image_url |
| PAPER_FORM | Include link to the paper form (can be scanned image) in optin_image_url |
| VIA_TEXT | Describe the keyword campaign in a document linked via optin_image_url |
| MOBILE_QR_CODE | Include the QR code in a document linked via optin_image_url |
Volume Tiers
Specify your expected monthly message volume using one of these values:| Volume |
|---|
| 1,000 |
| 10,000 |
| 100,000 |
| 250,000 |
| 500,000 |
| 750,000 |
| 1,000,000 |
| 5,000,000 |
| 10,000,000+ |
Provide a value that accommodates projected growth for the next six to eight months.
The Verification Object
Attributes
The unique identifier for the verification request.
The unique identifier of an existing Plivo profile.
The toll-free number for which verification is being initiated.
The messaging use case(s) for which the toll-free number will be used. One use case is mandatory; multiple use cases can be added as a list of strings.
Explanation of how messaging will be used on this toll-free number by your business.
Sample message(s) that your business will send to end users. Multiple samples are allowed.
A valid URL where you submit images explaining the opt-in process. Multiple URLs are allowed as a list of strings.
Describes how a user opts into receiving text messages.
An estimate of the monthly volume of messages you will send from the toll-free number.
Any additional information related to the website, such as terms of service or privacy policy links.
Any additional information for your own internal reference.
The status of the toll-free verification request.
The reason for toll-free verification rejection (if applicable).
A valid URL where verification-related callbacks will be sent.
The date when the verification request was created.
The date when the verification request was last modified.
Example Verification Object
Verification Statuses
| Status | Description |
|---|---|
| SUBMITTED | The carrier has accepted the submission and is reviewing the request. |
| APPROVED | The request has been verified by the carrier. |
| REJECTED | The carrier has rejected the verification request. The use case cannot be submitted for verification anymore. |
| UPDATE_REQUIRED | The carrier has requested additional data to validate the request. You must provide this information via the Update API within six days, or the request will be rejected. |
Create a Verification Request
Create a new toll-free verification request. You must first create a Plivo profile before starting the verification process.Arguments
The unique identifier of an existing Plivo profile.
The toll-free number in E.164 format for which verification is being initiated. Only US and Canadian toll-free numbers are accepted. Only one number per request.
The messaging use case(s). Multiple use cases can be added as a comma-separated string.
Example:
"2FA, CUSTOMER_CARE"Explanation of how messaging will be used (max 500 characters).
Sample message(s) that you will send to end users (max 1000 characters).
A valid URL where you submit images demonstrating the opt-in process. Multiple URLs allowed as comma-separated string.
How users opt in to messages. Values:
VERBAL, WEB_FORM, PAPER_FORM, VIA_TEXT, MOBILE_QR_CODEExpected monthly message volume. Must be one of the allowed volume tier values.
Additional information such as terms of service or privacy policy links (max 500 characters).
Information for your internal reference (max 100 characters).
A valid URL where verification-related callbacks will be sent.
Response
Retrieve a Verification Request
Get details of a specific toll-free verification request.Arguments
The unique identifier of the verification request.
Response
List All Verification Requests
Get the status of all toll-free verification requests for your account.Query Parameters
Filter by a single toll-free number.
Filter by verification status.
Filter by profile UUID.
Filter by use case(s) in comma-separated format. This is an exact match.
Filter by creation date (YYYY-MM-DD format). Supports
created__gt, created__gte, created__lt, created__lte for range queries. Default window is 7 days; maximum is 30 days.Number of results per page (1-20). Default: 20.
Number of records to skip for pagination.
Response
Update a Verification Request
Update an existing toll-free verification request. Only requests with statusSUBMITTED or UPDATE_REQUIRED can be updated.
Arguments
The unique identifier of the verification request.
The unique identifier of an existing Plivo profile.
The messaging use case(s) in comma-separated format.
Explanation of how messaging will be used (max 500 characters).
Sample message(s) that you will send (max 1000 characters).
A valid URL demonstrating the opt-in process.
How users opt in to messages. Values:
VERBAL, WEB_FORM, PAPER_FORM, VIA_TEXT, MOBILE_QR_CODEExpected monthly message volume.
Additional information (max 500 characters).
Information for your internal reference.
A valid URL for verification callbacks.
Response
Delete a Verification Request
Delete an existing verification request. Only requests with statusSUBMITTED, PROCESSING, or UPDATE_REQUIRED can be deleted.
Arguments
The unique identifier of the verification request to delete.
Callbacks
A callback is sent to thecallback_url (if specified) whenever the verification status changes:
- From
SUBMITTEDtoAPPROVED,REJECTED, orUPDATE_REQUIRED - From
UPDATE_REQUIREDtoAPPROVEDorREJECTED
Callback Parameters
The unique identifier of the verification request.
The toll-free number associated with the verification request.
The current status of the verification request.
Error or rejection reason (if applicable).