Twilio Changelog

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

This release of Flex UI introduces an improved troubleshooting experience for Flex UI users. Users of Flex UI will now be able to get error notifications via a Debugger UI and will be able to download a report with full error descriptions and logs. Flex UI developers will now be able to retrieve errors and logs programmatically to implement customized error monitoring and reporting. This Debugger UI is now in Pilot and can be enabled for your account on the Feature Settings Page.

To learn more about Flex UI troubleshooting, Debugger UI, and programmatic access to errors and logs, visit our Flex docs.

Other notable changes include

• Initial audio device check (previously in Pilot release) is now in GA and will be enabled by default for all accounts.
  

For a full changelog, visit the release notes for our client libraries:

Flex UI 1.25

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

You can now query for information about your calls in the Elastic SIP Trunking Call Log using the SIP Call ID found in your SIP network.

Developers can now use the standard ETag and If-Match HTTP headers when interacting with TaskRouter tasks. This allows developers to avoid conflicts when multiple systems are concurrently updating task attributes.

• When creating, updating or fetching a task in TaskRouter via the RestAPI, developers can now retrieve the version information for the task from the ETag header in the HTTP response.
• When updating a task via the RestAPI, developers can now provide the version information for the task in the If-Match header of the HTTP request to make the request conditional upon a version match.

To learn more about the new feature and the Task resource, please refer to our documentation.

Video Log Analyzer API is now generally available.

This API 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 developer docs and our blog post Getting to Know Video Log Analyzer.

Product discovery and refinement are still in progress. We will keep providing service to the existing customers, but we won't be accepting new customers during Q2 and Q3. Stay tuned for the next Branded Calls update in Q3 2021.

The new Get Contacts by Email endpoint allows you to retrieve one or more contacts by their email or alternate email addresses. This endpoint should be used when you know the email(s) you are searching for. If you need access to a larger set of contacts, please continue to use the export contacts functionality.

Twilio will be discontinuing the Authy API’s Sandbox on September 30, 2021. This feature allows customers to run continuous integration tests against a mock Authy API. The rest of the Authy API product will continue working as-is.

You will only be affected if you are using the Sandbox in your own application or test suite.

For more information please read this article on how we are discontinuing the Sandbox.

In order to enhance security for all of our users, Twilio SendGrid now requires customers on all paid plans to use API Key authentication on all API requests and SMTP configurations. Customers must also enable Two-Factor Authentication (2FA) for all users, including teammates. 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.

The new Recording Rules API is now Generally Available. Previously, the video recording system would record all Room participants or none based on your initial decision. As such, it did not allow any changes to the recording while the Room was in progress until it was concluded.

Using the new Recording Rules API, you can programmatically introduce a set of rules which will give you more granular control over what you choose to record in every possible situation. You will be able to start and stop the recording of the Room tracks at any moment in time and as many times as you want. You will also be able to record either video, audio or both tracks from any of the participants in the Room.

Please visit the Recording Rules API documentation page to learn more about it, including code samples for making it easier for you to use.

Twilio Mobile Core now uses a set of fixed IP ranges for traffic originating from Super SIM enabled devices. This enables you to set up filters on your firewall to accept traffic only from these IP ranges, instead of accepting traffic from anywhere on the Internet. To obtain the list of fixed IP ranges, please reach out Twilio Support.