Twilio Changelog

We have added new functionality for you to be able to choose whether you will receive your monthly Invoice PDF and/or CSV supplement to Invoice, via emails. This new “self service” option gives you an easier way to choose your notification preferences for receiving these documents via email. You can select the Notifications tab in Billing Preferences on console to set your notification preferences.

Twilio is now fully live with Verizon 10DLC A2P's service and carrier fees are in effect. You can read more about the change in our FAQ here.

Twilio Authy now supports delivering time-based one-time passwords via email, this expands upon its existing set of SMS, Voice and Authy app authentication channels. Email delivery is achieved through an integration with Twilio Sendgrid.

You can read more here.

Twilio Verify adds Email to its existing SMS and Voice channels for one-time password delivery, leveraging an integration with Twilio Sendgrid. With this addition, you now have one API to verify all your users, even those without phone numbers.

You can read more here.

Voice Insights Dashboard in Console has added the ability to filter on multiple aspects of call data to return more precise results when investigating call issues.

Previously users could filter results by one of the following: Phone Number, Carrier, Country Code, Number Prefix, Device Type, SIP Response, and Call State.

With the release of multidimensional queries, users can filter on multiple aspects, so instead of merely filtering calls to Norway, you can now filter on calls to Norway, that reached mobile phone destinations, within specific prefixes, that resulted in a particular SIP response code, etc.

For more information see the Voice Insights Dashboard docs.

To warn end-users against man-in-the-middle phishing attacks, we have added a feature to append a security warning to the end of your verification SMS body in Verify v2. This can be enabled by setting do_not_share_warning_enabled to true when creating your v2 Service via the API or in the Console on your Service settings page.

Verify v2 now supports passing an app_hash for Android developers using the SMS Retriever API. With this feature, you can perform SMS-based user verification in your Android app automatically, without requiring the user to manually type verification codes, and without requiring any extra app permissions. Support for this already exists in Verify v1 and has now been added to Verify v2. Please see the Verify v2 API docs for details on the verification request parameters.

The Programmable Voice Calls REST API now accepts TwiML when making outbound calls. Prior to this change, you were required to provide an absolute URL that Twilio would use to retrieve TwiML from your application. This change allows you to provide TwiML instructions when initiating a call with the REST API so that when the call is answered, Twilio immediately starts executing the TwiML instructions. This reduces webhook related delays and provides a simplified call set up mechanism. For more details on passing TwiML when launching an outbound call, check out How To Make Outbound Phone Calls.

Voice Insights Events and Metrics are now available via API allowing near-real time access to call quality data for all call types.

Voice Insights Events include call progress events like ringing and completed for carrier and SIP calls, and quality events like network quality warnings and audio level alerts for Voice SDK calls.

Voice Insights Metrics provide a time series view of key performance indicators like jitter and packet loss to help identify the precise timing and severity of quality issues on calls.

Voice Insights Events and Metrics API access is included as part of Voice Insights Advanced Features which can be enabled in Voice Insights Settings.

Voice Insights has updated the jitter and packet loss thresholds for Voice SDK calls to reduce the number of false positives and improve the diagnostic capability of Voice Insights data.

Previously tags were applied to Voice SDK calls in response to network and audio warning events fired by the SDK. We have updated the tagging scheme for these calls to use the same thresholds as our gateway metrics for jitter and packet loss, and to use the cumulative metrics for the entire call instead of samples.

As a result of these changes consumers of the Voice Insights Call Summary API should expect to see a significant reduction in the number of calls tagged with SDK edge tags.

Note: the SDK events will continue to fire at the previously defined thresholds, and the events will continue to be sent to Voice Insights Event stream. This allows application developers to continue to provide the same level of proactive notification and prescriptive instruction in their applications to ensure optimal call quality.