The v2 Regulatory Compliance APIs are powered by the new platform. The new platform is driven by the intelligence of the Regulations that dynamically evaluates Bundles
The following resources are available to be leveraged with the new v2 Regulatory Compliance platform. If you would like to know more about each resource, please click on the resource header.
The Twilio Bundles REST API allows you to create empty Regulatory Bundle containers. The Regulatory Bundles are Item Assignments of End-Users and Supporting Documents for regulatory compliance.
Depending on the configuration of the bundle, the bundle is being assessed against a Regulation (e.g., Germany local phone numbers for a business). Different Regulations need Item Assignments combinations of End-User Types and Supporting Document Types.
When Regulations are updated, customers and end-users are directed to begin updating their compliance information. To begin updating Bundles that are marked as information update required, the first step is to create a Bundle Copy to begin updating the relevant information. Once the new information has been approved, the next step is to replace the original Bundle Items. For more detailed information, please refer to the compliance information update API getting started guide.
When Regulations are updated, customers and end-users are directed to begin updating their compliance information. After creating a Bundle Copy and submitting the updated Bundles that are marked as information update required and the Bundle Copy being approved, Once the new information has been approved, the next step is to replace the original Bundle Items. For more detailed information, please refer to the compliance information update API getting started guide
The Twilio End-User REST API allows you to create End-Users to follow Regulations. The End-User is the entity that answers the phone call or receives the message of a phone number. An entity can be either an individual or a business. You can find more information about the possible End-Users by referencing End-User Type resource.
You will Assign Items to an End-User of a Regulatory Bundle with Supporting Documents. For applications that manage many End-Users, you will need to ensure that you assign the End-User instance to the correct Bundle instance to be in compliance with regulations.
End-User Types Resource API Doc
The Twilio End-User Type resource of Twilio's Regulatory Compliance API informs you which type of end-user you can create and what the values are. Once you know which end-user type you want to create and the required values, you will create using the End-User resource. Each End-User Type has a different set of values required to be compliant.
You will Assign Items to an End-User of a Regulatory Bundle with Supporting Documents. For applications that manage many End-Users, you will need to ensure that you assign the End-User instance to the correct Bundle instance to be in compliance with regulations.
Supporting Documents Resource API Doc
The Supporting Documents resource of Twilio's Regulatory Compliance APIs allows you to create new Supporting Documents with metadata to fulfill Regulations. Each Supporting Document Type may need different information to be compliant, so be sure to pass all of the correct values when creating a new Supporting Document Type.
A collection of Supporting Documents Assigned as Items to a Regulatory Bundle along with an End-User satisfies a Regulation.
Supporting Document Types Resource API Doc
The Supporting Document Type resource of Twilio's Regulatory Compliance API informs you which type of document you create and what the values are. You will then create a new Supporting Document with the correct type and values.
Each Supporting Document Type may need different information to be compliant. Supporting Documents Assigned as Items to a Regulatory Bundle along with an End-User satisfy a Regulation.
Item Assignments Resource API Doc
The Twilio Item Assignments REST API allows you to assign End-Users and Supporting Documents to Regulatory Bundles.
The configuration of the Regulatory Bundle must pass a Regulation (e.g., Germany local phone numbers for a business). Different Regulations need Item Assignments combinations of End-User Types and Supporting Document Types.
With the correct items assigned to the Regulatory Bundle, you can submit the bundle by changing its status. After submission, the Twilio regulatory reviewers will review the Regulatory Bundle.
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.
Note: 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.
The Evaluations Resource allows developers to understand what failed and why when a Regulatory Bundle is submitted to be evaluated against a Regulation. The synchronous request will provide error codes and instant feedback to fix the Regulatory Bundle.
[coming soon]