Last updated
Last updated
A toll-free number can be used to send messages in US & Canada once it passes an additional verification process. Users who don’t verify their toll-free numbers will be blocked from sending messages as of November 8, 2023.
A verified toll-free number ensures that the business owning the number is identified, and that the message's content has been reviewed and does not oppose the Disallowed Content Policy. This process ensures better deliverability and less filtration.
To set up a new channel to send SMS messages using a toll-free number the following steps are required.
The following API requests can only be made using a valid access key, and attached to an access role, with an access policy that at least specifies the permissions to the resources outlined in each section below. Learn more about .
If you do not already have a US or Canadian toll-free number available in your workspace you can find one to purchase.
use the search parameter types=toll-free
to only search for Toll Free Numbers
Once you have found an available number you can purchase this by providing the numberStockItemIds
matching the id
your previous call returned
A successful request to this endpoint will start a recurring monthly subscription based on the monthly cost of the number.
Before you can use a toll-free number to send SMS messages, you must submit a toll-free number verification request and wait for it to be approved.
To reduce the likelihood of rejection, ensure you are familiar with TFN registration examples and best practices. Specifically
Most TFN rejections are caused by unclear or incomplete useCaseSummary and/or optInWorkflowDescription
You can submit one toll-free number per verification request.
You are not allowed to submit the same number twice, unless the previous submission was resolved with status Rejected or Verified.
To make this call, you must provide following parameters:
Message Volume can only be of this type:
Fields below are not required for the submission:
201: Created
422: Unprocessable Entity (Invalid verification submission)
400: Bad request
Once you submit your verification request, you must wait for it to be reviewed. You will be informed about the status of your submission in the portal, but you can also use the API to fetch your verification request status.
200 OK:
404 Not Found:
If verification is rejected, some information will be provided in the DeclineReasonDescription if is in Progress, and any additional details have been required by the reviewing authority, you can find details in the Message
field
You can update verification submission with new information in two cases:
Authority has requested to add additional information. Your input is required.
Provide more accurate verification information without request of an authority.
200 OK:
404 Not Found:
422: Unprocessable Entity
A TFN may have multiple verifications (example the firs submission was rejected by the reviewing authority ) but only one of them can be active
Check for tips on how to write an effective useCaseSummary
Check on how to write an effective optInWorkflowDescription
Always check the ResubmissionAllow filed in the StatusMessage before using this method