Twilio Changelog

Starting January 6, 2025, Twilio phone numbers will automatically display all inbound messages in Messaging Logs and Insights, even without an inbound message URL configured. Additionally, all received inbound messages will be billed according to Twilio’s pricing list, even if no inbound message URL is configured.

Starting March 3, 2025, Twilio will rotate the end-user certificate and will update the list of supported cipher suites in all Twilio REST APIs. 

End-user Certificate Rotation

Only the end-user certificate will be renewed, as well as the certificate serial number. The root and intermediate certificates will remain the same. Such updates are common practice and do not impact customers that are using Twilio's services unless you are pinning certificates or are managing them manually. Customers using the official Twilio Helper Libraries should not experience any impact as they are designed to handle certificate rotations.

We highly discourage customers from pinning certificates as it exposes them to potential security risks and can cause downtimes for their services. Twilio customers using pinned certificates have a high probability of failed API Requests. These customers are advised to add the new certificates by March 3, 2025. 

Updates on the Cipher List

All our REST API endpoints will only support the cipher suites listed below. Support for any other cipher suite will be removed from that time.

Supported TLSv1.3 ciphers:

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256

Supported ECDSA ciphers (TLSv1.2):

• ECDHE-ECDSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES128-SHA256
• ECDHE-ECDSA-AES256-GCM-SHA384
• ECDHE-ECDSA-CHACHA20-POLY1305
• ECDHE-ECDSA-AES256-SHA384

Supported RSA ciphers (TLSv1.2):

• ECDHE-RSA-AES128-GCM-SHA256
• ECDHE-RSA-AES128-SHA256
• ECDHE-RSA-AES256-GCM-SHA384
• ECDHE-RSA-CHACHA20-POLY1305
• ECDHE-RSA-AES256-SHA384

Customers are advised to check that their infrastructure supports at least one of these cipher suites. Customers running older operating systems or legacy network software may need to upgrade their systems to be compatible with these changes.

Test your configuration

The new security configuration will be available on the testing domain ( https://tls-test.twilio.com ) on February 3, 2025. 

For more information on how to test the updated cipher list, we advise you to read Monitoring Updates to Twilio REST API Security Settings. 

Twilio is now selecting the “Secondary DCA Sharing Status” for all carriers in The Campaign Registry (TCR), including AT&T, Verizon, T-Mobile, US Cellular, Interop, and Clearsky.

What’s New for Customers:
Campaigns registered via TCR, externally registered campaigns, will now receive the CAMPAIGN_DCA_COMPLETE webhook from TCR. This webhook confirms that the campaign has been vetted and approved by all designated DCAs.

Starting December 3, 2024:
Twilio will backfill the Secondary DCA Sharing Status for existing campaigns registered for US Cellular, Interop, and Clearsky in TCR. This process will also trigger the CAMPAIGN_DCA_COMPLETE webhook for these campaigns.

As of November 21st, we have released a new messaging status update schema in Event Streams. Status update responses now include the number of message segments and the status update timestamp in ISO 8601 format.

Flex Insights (Historical Reporting) now offers Agent Copilot-related metrics that capture the customer sentiment and disposition code of a Conversation. If you have Agent Copilot and Flex Insights, you can visualize this data on the new Agent Copilot dashboard in Insights. For more information, see the documentation for Agent Copilot metrics.

With Flex Conversations, agents can now seamlessly transfer messages to another agent or to a queue, with the option to add notes for extra context during the transfer.

Flex Insights (Historical Reporting) also now offers key transfer-related metrics like Total Transfers, Successful Transfers, Failed Transfers and Transfer Segments. These power a new out-of-the-box report on Messaging transfers.

The Conversation Transfer plugin remains available in the Plugin Library. You can choose between using the native Messaging transfers functionality with historical reporting or continuing to use the plugin, if it meets your needs.

For more information, see the Messaging transfers (Public Beta) documentation.

Customers can now seamlessly add Over-The-Top (OTT) channel senders to their Messaging Service using our API.

This set of APIs will help you automate the Porting process to bring your numbers from your current carrier to Twilio

Starting May 5, 2025, Twilio will officially end support for TLS 1.0 and TLS 1.1 protocols on Elastic SIP Trunking and Programmable Voice SIP interfaces.