Twilio Changelog

Customers who are registering Brands, Campaigns and 10DLC Phone Numbers for A2P Messaging can now set up subscriptions to events which will notify them when a Brand, Campaign or Phone Number's status has changed. This setup and subscription is handled through Twilio's Event Streams product, which allows users to define a sink (in this case a webhook) to which an event notification will be sent for any events to which the user has subscribed - in this case, when a Brand or Campaign has been either successfully submitted or not, and whether successfully-submitted Brands and Campaigns are ultimately approved or rejected, or what a phone number’s status is in it’s A2P registration or deregistration process.

With these event notifications now 'pushed' to customers via the Event Streams framework, it will no longer be necessary to repeatedly query the Brand and Campaign creation APIs, be in limbo about the number’s registration status, or continually visit the A2P Console pages, in order to be kept up to date on registration status.

Check out the Event Streams product or documentation on how to utilize this new feature!

Twilio Programmable Voice now offers a React Native SDK to assist customers in building voice-powered mobile apps. React Native is a widely-adopted and actively maintained open source framework that allows web developers to create cross-platform applications using a single codebase that runs on both iOS and Android. The accompanying reference app reduces time to market by providing natively-styled UI elements out-of-the-box and demonstrates production-scale architectural best practices. The React Native SDK and Dialer reference app are both officially GA.

Additionally, we’ve added Public Beta support for the Call Message Events Voice SDK platform feature in the React Native SDK.

Check out the docs for more information, and please leave us any feedback you might have in the Twilio Voice React Native SDK Github repo. We can’t wait to see what you build!

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.