Twilio Changelog

As of September 5, 2025 the Legacy Boku Identity APIs Infrastructure in Indonesia will be migrated.

We would like to inform you about upcoming changes to Legacy Boku Identity API’s production infrastructure in Indonesia. These changes will not impact your current service. Our goal is to minimize impact to your current integration to our services. These updates are part of our ongoing commitment to improving performance, scalability, and reliability for all our customers.

If you have whitelisted or hardcorded our IP addresses instead of URLs, please make a note of our new IP addresses. These new IP addresses will take effect once we perform the switchover to AWS cloud services.

Our support team is available to assist you with any questions or concerns at accsec-onboarding@twilio.com.

Thank you for choosing Twilio. We appreciate your partnership and look forward to continuing to provide you with exceptional service.

Compliance Toolkit is now available in Public Beta, allowing you to use Artificial Intelligence and machine learning to help manage compliance obligations with respect to certain local regulatory or compliance requirements.

To start using Compliance Toolkit, Opt in through the Twilio Console and review the detailed setup instructions in our developer documentation.

A faster, more reliable, and user-friendly way to port US local numbers now available in Public Beta. This does not impact the previous experience "Port a Number" which can continue to be used.

Earlier in May 2025, geolocation data was temporarily removed from the IP Access Management (IPAM) feature and related API endpoints on Twilio SendGrid. 

This feature has now been reintroduced. IP-based location data is now provided in the console and through API.

• SendGrid Console:
  • The location field in Settings > IP Access Management > Locations
• API:
  • The IPAM logs API endpoint    

We’ve made an important update to A2P 10DLC Phone Number Registration events in Twilio Event Streams — now including the Messaging Service SID in all related events.

With this enhancement, you can directly identify which A2P Campaign a phone number is associated with by referencing the messaging_service_sid field in the 2.0 schema version. This improves traceability and helps streamline debugging, monitoring, and automation workflows tied to number registration.

The following Event Streams now include the messaging_service_sid field:
- com.twilio.messaging.compliance.number-deregistration.pending
- com.twilio.messaging.compliance.number-deregistration.successful
- com.twilio.messaging.compliance.number-registration.pending
- com.twilio.messaging.compliance.number-registration.successful

To learn more about A2P Notifications through Event Streams , check out our guide docs.

Requests made to the Recording Transcription resource for .csv and .html response formats will return an HTTP 404 error.

You can now select permissions for Usage Records and Event Streams API while creating a Restricted API Key. The product already supports permissions for Messaging, Phone Numbers, Studio, Voice, Task Router, Monitor, Lookup and Verify APIs.

Restricted API Keys allow you to decide which Twilio API Resources an API Key can access, and which action(s) the API Key is allowed to take on those API Resources.

We’ve made a key improvement to Authentication+ to support programmatically triggering a new 2FA verification email for A2P 10DLC Brand registrations that have failed. 

Alongside the endpoint, we’re introducing a set of dedicated 2FA error codes that surface precise failure reasons and point you to the fastest remedy, so your users can complete brand verification with fewer support tickets and less manual work.

To learn more about Authentication+, check out our Support Article and Twilio API Docs.
 

Twilio will now support RCS Title and description text in twilio/card. We will support backwards compatability to ensure no existing templates fail to deliver based on channel limitations. 

No changes will occur in WA translations. 

• Twilio supports RCS title via the title field in twilio/card
  • Up to 200 characters for RCS title
  • Twilio will translate twilio/card title to description if twilio/card title is greater than 200 characters
• Twilio supports RCS description with the body field in twilio/card
  • twilio/card subtitle will also be appended onto the body to form RCS description