Twilio Changelog

The Programmable Voice Call Events for individual calls can now be retrieved using a new Call Events REST API. Previously individual call events were only available via the Twilio Console. Using the new REST API you can programmatically retrieve the event logs of a specific call for further analysis or to populate your own dashboard.

Call Events can be used to programmatically analyze the result of the call, errors related to webhooks, TwiML returned by your application, as well as DTMF or speech input provided at various points during the call.

Please visit the API documentation page to learn more about using the API, and to access code samples in different languages.

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 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.

We have updated all Flex projects that use Automatic Updates to Flex UI 1.23.

This release of Flex UI introduces usability improvements for the Conversation Screen. Now when users drill down to individual conversations they stay natively in the Flex UI. The former Conversation Screen is still available but will be deprecated.

Other notable changes:

The Teams View will now recover automatically from connection loss. Users will not need to refresh the page to recover their connection.

Several dependency packages have been upgraded to patch security vulnerabilities.

For a full Flex UI 1.23 changelog, visit the Flex UI release notes.

Reminder: You can pin to individual versions of the Flex UI or manage your Automatic Updates within the Flex Admin UI.

As of Dec 31st, 2020, Branded Calls will not be accepting new customers into the Private Beta program while we work with existing customers to refine the product based on their feedback and priorities. All current customers will continue to be supported. Stay tuned for the next Branded Calls update in Q1 2021.

Twilio launched Programmable Fax to allow developers to simply send and received faxes over the same reliable REST API you've come to expect.

Unfortunately, due to an influx of fraudulent traffic, we made the difficult decision to disable access to Programmable Fax for any new accounts and accounts that have not used it in the last 12 months.

Providing continued access to self-service onboarding presents support and security challenges for the Twilio team, preventing us from supporting current customers at the level they deserve. We recognize the challenges this decision might cause and will provide proactive communication as we work to improve the developer experience on Twilio.

Previously, segment samples did not refresh after initial segment creation (or after editing the conditions of a segment). With this release, segment samples are now refreshed hourly as long as Marketing Campaigns detects any changes as contacts enter or exit the segment. If no changes are detected, the next refresh will occur at 2 hours, and then 4, with a maximum delay to segment sample refresh of 24 hours.

For a real-time view of all contacts within your segment at any time, you can always export a CSV. This is not dependent on the sample refresh cadence.

For more information about the segment refresh cadence, see our segmentation documentation.

From the Contacts page, you can now see when the next scheduled segment will occur by hovering over the segment contact count. This same information can also be found on the segment detail page beneath the total contact count for that segment.

For a real-time view of all contacts within your segment at any time, you can always export a CSV. This is not dependent on the segment refresh cadence.

The sample refresh cadence has also been made available to Marketing Campaigns API users via the next_sample_update field.

This release of Flex UI introduces usability improvements for the Conversation Screen. Now when users drill down to individual conversations they stay natively in the Flex UI. The former Conversation Screen is still available but will be deprecated.

Other notable changes:

• The Teams View will now recover automatically from connection loss. Users will not need to refresh the page to recover their connection.
• Several dependency packages have been upgraded to patch security vulnerabilities.

For more details on this release, please visit the Flex UI release notes.

Following the release of Video Log Analyzer in Console, we have exposed a Video Log Analyzer API for retrieving Programmable Video Room and Participant details.

This resource allows developers to simplify troubleshooting and help identify commonalities in reported issues by programmatically retrieving critical metadata about Participant and Room behavior. The information provided includes: why a Participant left a Room, how the Room was ended, browser/operating system details, Participant error codes, and more.

For more information, see the docs.

Updating a Super SIM’s status to inactive now terminates any existing data sessions immediately and new connection attempts will be rejected. To resume using your Super SIM, change its status back to active to allow it to reconnect.