Twilio Changelog

Twilio's response to POST to /Participants API will now return a queue_time parameter, which provides an estimated time the call will be queued before it is executed. 

The latest Twilio Voice mobile SDKs (iOS and Android) now expose a new AudioOptions API. This gives developers fine-grained control of their app’s audio experience by enabling audio processing operations on the local audio source. The following webRTC options are now exposed via the new API:

• Noise suppression
• High pass filtering
• Set jitter buffer max size
• Set jitter buffer min delay
• (Android only) Echo cancellation
• (Android only) Automatic gain control

Check out the docs (iOS and Android) for more information on how to use the new functionality in your application. We can’t wait to see what you build!

HTTP callbacks (webhooks) for inbound WhatsApp messages that originate from a Meta Click-to-WhatsApp advertisement now include a new ReferralCtwaClid parameter. This parameter contains the unique identifier generated by Meta representing the WhatsApp message conversation initiated by a user’s ad click. Customers can now use this parameter to integrate their WhatsApp business messaging events with Meta’s Conversions API (see ctwa_clid) to optimize Meta’s ads targeting and performance measurement.

Learn more about how to create Click-to-WhatsApp advertisements with Twilio from our blog post.

Twilio Messaging MaxPrice API parameter will be deprecated starting June 3, 2024. 

Effective April 11, 2024, new certificates will be deployed for all our REST API endpoints (e.g., api.twilio.com), including all regional edge locations. 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.

The certificate will be available on the testing domain ( https://tls-test.twilio.com ) on March 11, 2024.

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 Apr 8, 2024. You can follow the information mentioned on the official documentation.

We are excited to announce an enhancement in the A2P 10DLC Brand registration process. In our ongoing efforts to streamline and improve the user experience, we now have standardized error codes for any failures or issues encountered during Brand registration. These error codes will be directly available through the errors attribute on the Brand. 

With this release, it’s important to note that brand_feedback and failure_reason will be deprecated in an upcoming release.  If you have used these attributes in your integrations, we strongly advise transitioning to the new errors attribute due to its pending deprecation and limited information. 

Check out the updated Brand registration Twilio docs for more information. or a detailed list of all error codes please visit Twilio Error and Warning Dictionary.  

SendGrid and Segment are rolling out an updated signup experience that will route new customers to a shared Twilio signup page. This will provision a new SendGrid or Segment account in which a user will share a single identity and user settings will be managed on Twilio. No action is required for customers at this time. 

This change allows all new signups across Twilio products to easily sign up for another product and have a seamless cross-product navigation experience.

Starting March 11, 2024 Twilio Console and services.twilio.com will no longer support TLS version 1.1 and older, and outdated cipher suites. This is part of an important security upgrade to our systems. Customers running older operating systems or legacy network software may need to upgrade their systems to be compatible with these changes.

The following cipher suites that will no longer be supported in Twilio Console:

• ECDHE-ECDSA-AES256-SHA
• ECDHE-RSA-AES128-SHA
• ECDHE-RSA-AES256-SHA
• AES256-SHA
• AES128-SHA

Cipher suites in services.twilio.com will not be changed