Twilio Changelog

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.

The Functions V2 UI now allows users to automatically include latest dependencies by adding * or latest in version text box. This will include the latest version and keep your functions up to date with each deploy.

You can now delete specific variations of an A/B test for a Single Send. If there is only one variation remaining after a second is deleted, the A/B test will turn off and the remaining variation will become the default.

Voice Insights Call Summary records now include the queue time parameter in properties.queue_time. Queue time is the estimated time between the API request to create a new call and when the call actually begins. Programmable Voice calls are queued when the rate of call creation via API exceeds the calls per second (CPS) setting of the account.

Warning-level events have been also updated to include the warning event trigger threshold and the detected values that resulted in the warning being raised by the SDK. These details are available under sdk_edge.metric.threshold and sdk_edge.metric.values and can help developers fine tune when to display visual indicators of quality degradation in their apps or identify calls whose performance exceeds a defined condition without needing to look at the underlying Metrics.

For more information see our Call Summary and Events docs.

The Voice Insights Subaccount Dashboard has been updated with a new graph that displays the subaccounts with the highest average queue time. Queue time is the estimated time between the API request to create a new call and when the call actually begins.

Programmable Voice calls are queued when the rate of call creation via API exceeds the calls per second (CPS) setting of the account. Subaccounts with high average queue times may indicate suboptimal CPS settings. CPS can be adjusted in the Programmable Voice Settings section of Console.

For more information see our docs.

As of December 17, 2021, we will be sunsetting support for the Twilio Programmable Fax offering.

We are sincerely sorry for any disruption this may cause. To ensure a smooth transition, existing customers may continue to use our Programmable Fax API until December 17, 2021. Additionally, we’ve partnered with mFax by Documo to offer a migration plan to prevent disruption.

For any question please read through the FAQ.