Twilio Changelog

With Verify’s TOTP (Soft Token) channel you can support authentication through software-based authenticator apps like Authy or Google Authenticator. It’s great for businesses looking for a more secure and lower-cost option compared to SMS OTP that works offline and doesn’t require a phone number. With this release, the API is publicly available and supports production-scale workloads. Learn more here.

On October 23, 2023, the certificate for Osaka Regional Edge Ingress of the Rest API products (e.g. chat.osaka.*.twilio.com) has been rotated successfully. The root, intermediate certificate (ICA) has been renewed, as well as the certificate serial number has been changed. 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.

For customers who are pinning certificates or are managing them manually, please add these new certificates now, if these have not been added already when the communication was sent in September 2023.

As a reminder, effective December 15, 2023, Twilio will End of Life (EOL) the 2008 version of Twilio API. We previously communicated about this migration in April 2022.

As part of our goal to provide you with highly operational and available APIs, the 2008 version was deprecated on May 2, 2022 and it has not been receiving updates. After December 15, 2023, any requests sent to Twilio’s 2008 API will fail with 404 responses. 

To avoid disruption to your application, switch to the 2010 version of Twilio API. You can follow the steps in our Upgrade from Twilio's v2008 API guide to migrate away from the 2008 version of the API to 2010.

We previously communicated that CNAME for unauthenticated access to HTTP Voice recording media URLs would be deprecated on February 5, 2024. As part of security and reliability initiatives, we’re rolling-out some important architecture changes to our Edge Infrastructure and this date is being pulled forward to November 1, 2023. 

Google Business Messages ("GBM") is available in Public Beta. GBM lets people contact your business directly from Google Search, Google Maps and other entry points of your choosing. GBM chats happen on Google's Messages app on Android, and through Google Maps on iOS. 

To use Google Business Messages, head to Twilio Console's "Channels" area and create a brand and sender. You can receive and respond to GBM messages using Conversations API, Programmable Messaging API and Twilio Flex. Learn how to set up Google Business Messages.

Facebook Messenger and Google Business Messages channels are available for Flex Conversations in Public Beta. When configured, agents in your contact center can use these channels to send and receive messages from your customers. For information about how to enable these channels, see the documentation about using Flex with Facebook Messenger and Google Business Messages. 

To use Facebook Messenger and Google Business Messages channels, you must upgrade to Flex UI 2.4.0 or later. For more details about these features and other Flex UI 2.4.0 updates, see the Flex UI Release Notes for v2.x.x.

Inbound Programmable Voice and Elastic SIP Trunking calls to phone numbers in Twilio Trial Accounts are now required to be from numbers which have been Verified in that Trial Account.

The Real-time Queues View now offers four new metrics to better manage your contact center: average speed of answer (ASA), average handle time (AHT), missed invitations, and average abandon time. 

These new metrics are available in Flex UI 2.4.0 and later. For more details about this feature and other Flex UI updates, see the Flex UI Release Notes for v2.x.x.

Branded Calling is now available in Public Beta. Customers can create a Branded Calling Trust Product in the Twilio Trust Hub using the Trust Hub REST API and enable displaying of the Company Name in the caller ID for outbound calls made to cell phones. Customers need to onboard to Voice Integrity as a prerequisite to Branded Calling. 

If you are currently using Branded Calling, you will need to update the Branded Calling End User in code.

To learn more about Branded Calling, please check our docs. 

Read more about Branded Calling in this blog post.