Today we are excited to announce that the Phone Numbers Evaluations API resource has moved to public beta.
As you may know, Phone Numbers with compliance requirements for documentation require Regulatory Bundles. With the Evaluations API, Twilio makes it possible to understand whether a Regulatory Bundle Evaluation passed or failed and provide the specific field-level failure reasons. The granular failure reasons provide specific call-to-actions for you or your customers to fix before a submission can be accepted, making it faster and easier for you to create and manage bundles.
Accessing Evaluation results and information via API
To provision a phone number with regulatory compliance requirements, you must follow local requirements of the country or territory, providing End-User information and Supporting Documents. To do this you must create a Regulatory Bundle and bundle together all of the End-User information, Supporting Document(s), and Address(es).
Once a Regulatory Bundle has …
Today we are excited to announce that the Regulations API Resource has moved to Public Beta.
With the Regulations Resource, Twilio is making it simpler to understand the regulatory compliance requirements for phone numbers in regulated geographies by allowing customers to reference the regulations with a single API call.
Accessing Regulatory Compliance requirements via API
To provision phone numbers with regulatory compliance requirements, you must follow local requirements of the country or territory, providing End-User information and Supporting Documents. Using the Regulations API Resource, you can view each geography’s telecom requirements. The Regulation list includes all countries in the Phone Number Regulations Guidelines.
You can either request the regulations for a specific SID or a list of regulations that can be filtered based on ISO country (2 digit codes published by the International Organization for Standardization for the names of countries, dependent territories, and special areas of …