The Twilio Regulatory Compliance REST API allows you to view and understand Regulations. Regulations are requirements based on End-Users and Supporting Documents set for by each country's government.
A Regulation dictates the Regulatory Bundles composition of Item Assignments.
Regulations can and do change. Please make sure not to hardcode any regulation within your application. The Regulation resource is for you to call and populate the values required for regulatory compliance.
A human-readable description that is assigned to describe the Regulation resource. Examples can include Germany: Mobile - Business.
The type of phone number restricted by the regulatory requirement. For example, Germany mobile phone numbers provisioned by businesses require a business name with commercial register proof from the Handelsregisterauszug and a proof of address from Handelsregisterauszug or a trade license by Gewerbeanmeldung.
The type of End User the regulation requires - can be individual
or business
.
individual
business
The SID of an object that holds the regulatory information of the phone number country, phone number type, and end user type.
The absolute URL of the Regulation resource.
GET https://numbers.twilio.com/v2/RegulatoryCompliance/Regulations/{Sid}
A Regulation instance details the End-User Types and values along with Supporting Document Types.
GET https://numbers.twilio.com/v2/RegulatoryCompliance/Regulations
The Regulations list is extensive and covers all Twilio's countries in the Phone Number Regulations Guidelines.
The Regulations LIST
endpoint is filterable by IsoCountry
, NumberType
, and EndUserType
so you can select the correct instance of the collection of regulatory requirements.
The type of End User the regulation requires - can be individual
or business
.
individual
business
The type of phone number that the regulatory requiremnt is restricting.
How many resources to return in each list page. The default is 50, and the maximum is 1000.