Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

Phone Numbers Product Releases, Regulatory Compliance Features

All references to “phone numbers” below refer to Twilio phone number types requiring regulatory compliance (RC) information (such as Address and/or Supporting Documents). Note that approximate timeframes for important milestones are included below and will be updated as dates are finalized.

Upcoming changes


  • We will continue to review phone number data looking for missing or inaccurate information. We will notify you when action needs to be taken or information needs to be reviewed on your phone numbers. Twilio is committed to helping you meet the governmental and industry regulatory requirements for phone number provisioning and usage.

Previous Changes

July 30, 2019

  • For existing phone numbers
    • Existing phone numbers in your current inventory should have been brought into compliance. If you have not already taken this necessary action, your phone numbers are at risk of being reclaimed due to ongoing carrier and regulatory enforcement activity. Twilio will not proactively reclaim phone numbers that are out of compliance at this time, except where forced to do so by regulators or carriers. We strongly urge all our valued customers to prioritize bringing all existing phone numbers into compliance if you haven't already done so.
  • For new phone numbers provisioned in Console
    • Provisioning new phone numbers through the Twilio Console requires you provide the needed regulatory information as outlined here for each phone number type. We will review submitted documents and information within 3 business days.
  • For new phone numbers provisioned through the existing API
    • There is no change in behavior to the API. You must subsequently upload required regulatory documents and information via the Twilio Console or with the RC Pilot APIs.
  • New Regulatory Compliance (RC) APIs are available in Pilot
    • Using our new APIs (“V1” Regulatory Compliance APIs in Pilot), you will be able to programmatically submit and manage RC information for your Twilio phone numbers completely through this single API set.

August 6, 2019

  • Full walkthrough of our RC Intelligence Platform
    • The Twilio Phone Numbers Product Team will walk through our new RC Platform in a public talk at the SIGNAL Conference in San Francisco, highlighting the new APIs and timeline. This talk will be recorded and made available to anyone not able to attend SIGNAL, shortly after the event.

August 20, 2019

  • For new phone numbers provisioned through the existing API
    • We will disallow blank addresses between 12:00 a.m. and 3:00 a.m. Pacific Time (PDT) for newly provisioned regulated phone numbers. This action is to alert those who are failing to provide addresses when provisioning new phone numbers via the API. If you would like to be exempted from this brownout, please notify us here.
    • Note that this brownout was originally scheduled for August 12 and has been pushed back to allow you additional time to request to be exempted from the brownout and avoid potential disruption.

September 10, 2019

  • For new phone numbers provisioned through the existing API
    • Address requirements will be enforced via the API, provided through an AddressSid. This means you will be required to provide addresses for newly provisioned regulated phone numbers. API calls to provisioned phone numbers that do not submit a valid address will fail with error code 21631.
    • Note this was originally planned for August 26 and has been delayed in order to provide sufficient time for you to make the necessary changes to your application(s) after the August 20 brownout.

December 11, 2019

  • Release: “V2” Regulatory Compliance API in Beta
    • Request Regulations requirements via API for a given country, phone number type, and end-user type.
    • Maintain a library of uploaded End-User information, Supporting Documents, and Regulatory Bundles.
    • Granular error handling of Regulations.
    • Final API contract for Regulatory Compliance management (contract will not change moving forward).
  • Who has access
    • All customers. The V2 RC APIs will be mandatory by Q2 2020 (GA).
  • Known migration requirements or incompatibilities
    • The previous versions of this v1 RC API will stop functioning on December 11, 2019.
  • Documentation

February 12, 2020

March 2020

  • Release: The Regulations API resource makes 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.
  • Who has access
    • All users
  • Known migration requirements or incompatibilities
    • None
  • Documentation

May 2020

  • Release: The Evaluations API resource makes it possible to understand whether a Regulatory Bundle Evaluation passed or failed and provide the specific field-level failure reasons.
  • Who has access
    • All users
  • Known migration requirements or incompatibilities
    • None
  • Documentation

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd browsing the Twilio tag on Stack Overflow.