Twilio Changelog

The beta for Client Insights ended on August 5, 2019 and was superseded by the general availability of Voice Insights. The Client Insights Dashboard was removed from Console at that time, though we have continued to respond to requests made to the preview API. Twilio will cease responding to API requests to preview resources on May 1, 2020. Any HTTP requests to preview resources after this date will result in a 404 response from the API.

If your application is currently making requests to any of the preview API endpoints described below, you will need to migrate to the new Voice Insights API endpoints.

Twilio Functions lets you deploy NodeJS code into Twilio's serverless environment to handle communications events in support of your applications. Functions can be deployed via API or UI. Previously, Functions deployed via the API used NodeJS version 10, but Functions deployed via UI used NodeJS version 8. NodeJS version 8 is now End Of Life. From today all Functions deployed, either via UI or API use NodeJS version 10. Click here for more information about the upgrade.

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.