Twilio Changelog

With Twilio Sync moving to General Availability, you have guaranteed service-level agreements for your two-way, real-time communication between browsers, mobiles, and the cloud. Use Twilio Sync to get your apps in sync with only a few lines of code away. You don't have to worry about setting up the databases, managing queues, and thinking about how to build secure apps at scale with end-to-end encryption. Sync handles all that for you.

The per-minute price of Twilio Bring Your Own Carrier Trunking Origination (outbound to carrier) has been reduced from $0.007 to $0.004 per minute. You do not need to do anything; you will automatically be charged at the lower rate.

For more details on Twilio Bring Your Own Carrier Trunking, please visit our documentation.

We intend to sunset the Programmable Chat API on July 25, 2022 to focus on the next generation of chat, the Twilio Conversations API. Twilio Conversations is a unified API for cross-channel group messaging and includes support for chat, WhatsApp, SMS. While you will need to update your application code, most functionality will remain the same. Additionally, your existing Channels in Programmable Chat will migrate to Twilio Conversations and all of your Channels are visible in Conversations.

The Chat API will continue to work within Flex applications beyond this date.

We are sincerely sorry for any disruption this may cause and have prepared this Migration Guide to assist with the transition to the Conversations API before July 25, 2022.

Programmable Voice now returns the SHAKEN/STIR attestation given by Twilio to your outbound call in a StatusCallback, so that you can store it in your internal system. This will help you to ensure that you have configured your Twilio local and toll free numbers correctly to receive full attestation which will increase answer rates and reputation of your calls. Learn more here.

The Studio REST API v2 with Flow publishing support is now Generally Available. Now developers can create, publish, and manage Flows programmatically -- without having to log in to Twilio Console -- and all with the backing of Twilio's service level agreement.

With the Flows endpoint you can

• Integrate Flow publishing into your CI/CD pipeline to automate Studio deployments
• Programmatically move Flows between accounts or subaccounts
• Create your own custom, branded Studio front-end UI

To learn more, read the announcement on our blog or try the quickstart.

You can now clone variations of an A/B test for a Single Send. You can have a maximum of 6 variations per test.

Twilio accounts now support the creation of up to 1,000 IP Access Control Lists (ACLs). Each Access Control List can hold up to 100 IP ranges. You can review the user docs for more information.

You can now purchase Twilio Super SIMs in the MFF2 form factor in Console. These SIMs, often referred to as "embedded SIMs", come in a smaller form factor, are solderable to the device, and can operate under wider temperature ranges compared to plastic SIM cards. Embedded (MFF2) Super SIMs are available in packs of 10, 100, and 1000.

In order to enhance security for all of our users, Twilio SendGrid now requires customers on free plans to use API Key authentication on all API requests and SMTP configurations. Customers impacted by this breaking change will experience authentication errors when making API calls or SMTP requests using basic authentication with their username and password. Customers must also enable Two-Factor Authentication (2FA) for all users. Visit our docs for more information on Upgrading to API Keys and Enabling Two-Factor Authentication. If you did not receive notifications about this change please update your account email address.

You can now manually select the winner of an A/B test for a Single Send. The ability to manually select a test winner allows you to make more nuanced decisions about how to best engage your audience and prioritize the metrics that are most important to you, such as unsubscribes, spam reports, or conversions. To learn more about A/B testing, see A/B Testing Your Single Send.