Twilio Changelog

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.

Today we are announcing the Public Beta launch of the native integration between Twilio Programmable Voice and Dialogflow Essentials (ES). With this integration you can bring the power of conversational AI to your Twilio calls to provide rich and natural caller experiences within your Twilio IVR. This integration is powered by a new TwiML <VirtualAgent> which is also available as a Connect Virtual Agent Studio Widget. When executed, they connect a Twilio call to your configured Dialogflow ES Agent.

To get started, select Twilio as a “One-Click” telephony partner on the Dialogflow ES console and finish with selecting one or more Twilio phone numbers to associate with your Dialogflow ES agent. Callers calling into those numbers will then be connected directly to Dialogflow. You can always use TwiML and Studio to modify the call flow.

Learn more about the integration, <VirtualAgent> TwiML, and the Connect Virtual Agent Studio Widget.

The Flex Plugins CLI now provides the ability to archive a plugin, a plugin version, or a configuration. When archived, admins or developers can no longer enable the plugin for agents via the Plugins Dashboard or Plugins CLI. Developers can archive a configuration to prevent it from being redeployed. The archive command can be used to indicate that a plugin is no longer actively maintained or it has defects and should not be enabled. Information on archived plugins or configurations can still be viewed on the Plugins Dashboard and the Plugins CLI. For more details on this feature, refer to our documentation.

With this feature, you will be able to search Twilio Elastic SIP Trunk at ease. From the console, navigate to the Elastic SIP Trunking “Trunks” page and you can now use any of the filters such as Trunk SID, Trunk Name, Termination and Origination SIP URI to better search the trunk(s) of your interest. You can see more details here.

Every US(+1) Toll-Free number is now enabled with MMS capability, out-of-the-box. Starting today, you can use Toll-Free numbers to send and receive media messages from recipients in US and Canada.

To learn more about emerging use cases for media messaging, please visit our blog post.

You can now see detailed performance data on individual emails within an Automation. Stats include information on emails triggered, emails delivered, clicks, opens, unsubscribes, bounces, and spam over time. Click Tracking data and Email Details are also available.

To see performance data on emails in an Automation, navigate to the Automations section of Marketing Campaigns, click into the detail view for an Automation, and select View Stats from the action menu to the right of an individual email in the Automation.

To correctly end an Execution for an inbound Voice call, Studio needs the “hangup” event from the Voice status callback. When that event is not received, the Execution may be left open (or “stuck”) indefinitely.

To address this, Studio now automatically configures the status callback shortly after configuring your phone number for Studio. This ensures the final “hangup” event is always received. With this release, manually setting the status callback is no longer necessary and helps avoid “stuck” Executions for inbound calls.

To learn more, review our knowledge base article.

Twilio Elastic SIP Trunking now perform SHAKEN/STIR verification on incoming calls to your Twilio local phone numbers. It can be used to display a trust indicator or to make a routing decision, such as bypassing a voice captcha or IVR and directing the call to an end user.

A verified call that has been given the highest attestation under SHAKEN/STIR means that the carrier that originated the call both (1) knows the identity of the caller, and (2) knows the caller has the right to use the phone number as the caller ID.

There is a new header called X-Twilio-VerStat with the verification result. The new header is only present for incoming calls with SHAKEN PASSporT identity headers. Today, the United States is the only country where carriers instrument a call authentication framework like SHAKEN/STIR.