Twilio Changelog

The Warm Transfer feature is now generally available in Flex. 

With warm transfers, agents can:

• Call another agent or a queue for consultation about an ongoing customer call

• Start a conference call between another agent and a customer

• Transfer the customer to another agent

For more information, see: Warm Transfer - End User Guide.

Effective December 15, 2023, Twilio will End of Life (EOL) the API Explorer feature in Console used to explore the REST API. After this date, the API Explorer will be unavailable for all customers.

If you want to continue to explore our API, we recommend using our API Documentation or the Twilio OpenAPI Specification with third party vendors like Postman.

Twilio Content Template Builder, formerly known as the Content API and Content Editor is now generally available. 

The Content Template Builder enables you to create and manage rich messaging templates and utilize them across all supported messaging channels, including SMS, WhatsApp, Google’s Business Messages, and Facebook Messenger. Send engaging rich messages to users no matter where you reach them with the Content Template Builder.

Try out new features:

• Build rich conversational experiences with content templates in Studio
• Send personalized outbound campaigns and notifications at a future time using content templates sent with Message Scheduling
• Create content templates with dynamic header text for WhatsApp

Click here to learn more. 

Content Templates, Content Variables, and rich features from Content Template Builder are now supported in Studio.

Content Templates are currently available on WhatsApp, Facebook Messenger, SMS, MMS, and Google Business Messages. New channels will continually be added. 

Content Templates can be used for generating automated responses to your customers in Twilio supported channels. Content Templates enable the use of rich content and personalization via buttons, media, variables, and channel specific template types to drive greater engagement and streamlined messaging interactions.

Use Content Templates in Send and Send & Reply widgets. Use rich features in the Split widget. 

Variables in WhatsApp and other channels can now be specified using Content Variables via key-value pairs instead of body insertion in a simple deterministic structure.

See our public documentation to learn more.

ParticipantCallStatus and ReasonParticipantLeft are now being returned as attributes on the participant-leave Conference status callback event. 

Previously, discerning the reason for a given participant's departure from a conference could be challenging; for example, if a participant was added using the /Participants API but failed to answer the incoming call, the application would need to tie together the call’s status for its callbacks with the 'participant-leave' callback.

The participant-leave event callback now contains all of the information required to discern the underlying call status for a participant, as well as the cause of a participant's departure from the conference.

Developers can now provide a call token from an incoming Programmable Voice call when creating a new conference participant in order to reuse the caller ID from that incoming call.

Previously, call token support was only available for the /Calls API, and developers who wanted to use the /Participants API were limited to using Twilio phone numbers or verified caller IDs as the caller ID when doing a POST to /Participants. 

To reuse the caller ID from an inbound Programmable Voice call when creating a new conference participant simply pass the CallToken from the inbound call as a parameter to the /Participants API.

For more information, see our docs.

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.