Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
Twilio Edge Locations

This release includes support for the expansion of Twilio’s Global Infrastructure via Edge Locations which allows connectivity control into and out of Twilio’s platform. The Voice Client JS SDK uses these Edges to connect to Twilio’s infrastructure via the new parameter Twilio.Device.Options.edge. This new parameter supersedes the now deprecated Twilio.Device.Options.region. See Twilio.Device.Options.edge API documentation for more information.

Example

const device = new Device(token, { edge: 'ashburn' });

Support for Edge Fallback (Beta)

Deployments designed to connect to multiple Twilio Edge locations can take advantage of the new fallback mechanism. To enable the edge fallback, specify an array of edge names via Twilio.Device.Options.edge. When enabled and a connection failure is encountered, the SDK will reattempt the connection to the next Edge location in the array. For more details about how the fallback works, see the Edge fallback documentation.

Example

const device = new Device(token, { edge: ['ashburn-ix', 'san-jose-ix', 'roaming' ] });

For download instructions see this page

To get started with Twilio Voice Client JS SDK, see our quickstart


Twilio Conference resource now includes two additional fields that describe the reason why the conference has ended. A Voice Conference can end for several reasons. It can end when all participants have left, when the moderator has left, or it may also end programmatically via an API request. It can sometimes be difficult to determine the reason why the Conference ended. The new fields reason_conference_ended and call_sid_ending_conference on the Conference resource will make it easier to troubleshoot why the conference ended either via API or console.

Click here to learn more about the different reasons a conference can end in our Conference Resource documentation.


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

This Flex UI release brings the following new features to Flex:

  • Support for using Yarn as a package manager: Developers can manage their project dependencies using Yarn package manager. Yarn is now supported in the client libraries Flex UI 1.19 and Flex WebChat UI 2.4. Yarn can be used by updating any plugins to use the latest version of the Flex Plugin Builder. Visit our Yarn documentation for more details.
  • Data sorting for Real-time Queues View: Developers have more control over the sorting and customization options for columns they add to the Real-time Queues View. You can learn more about this feature within our documentation.
  • Handlebars dependency upgrade: We have upgraded Handlebars to 4.7.3 to fix critical security vulnerabilities exposed in previous versions of Handlebars. This may be a breaking change if you use certain undocumented Handlebars features. You can find more information about this change in the Handlebars changelog.
  • Flex UI and WebChat API Reference: API references describe all available public interfaces, methods and properties. Refer to the Flex UI API Reference and Webchat API Reference for more details. This is currently available as a Pilot feature.

For a full changelog, visit client libraries release notes:

Flex UI 1.19

Flex WebChat 2.4

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


Twilio SendGrid Platform

Signed Event Webhook Requests and OAuth for Event Webhook in Public Beta Beta

Twilio SendGrid now provides two security features that allow you to verify that email event data is being posted by Twilio SendGrid: a Signed Event Webhook and OAuth 2.0. These security features are independent of one another and can be used together.

Twilio SendGrid’s Signed Event Webhook uses the Elliptic Curve Digital Signature Algorithm to sign requests. The signature allows customers to verify that event data is being posted by Twilio SendGrid.

OAuth 2.0 for the Twilio SendGrid Event Webhook allows customers to verify that Twilio SendGrid is properly authorized by them to post to their URLs using the Client Credentials grant type.

To learn more about these new features in Beta, visit our documentation.


Marketing Campaigns

New image editing options GA

The email editors within Marketing Campaigns now support more options for formatting your images. You can crop, flip and rotate your images, add filters, or make adjustments like contrast or opacity all from within your email editing workflow. These editing options are also available within the Design Library under Your Images. Learn more.


Programmable Messaging

Upcoming changes to log availability for Messages

Starting August 15, 2020 you will be able to view message logs in Console--and retrieve the resources via GET to the /Messages endpoint--for thirteen months after the resource is created. This represents a significant change as these logs are currently permanently stored by Twilio and retrievable via Console and API.  

Before this change goes into effect we will provide a Bulk Export utility in Console and via API. Bulk Export will generate S3 files containing one day of data per file and deliver the download link via webhook, email, or Console. Records older than thirteen months will only be able to be retrieved via Bulk Export.

If you view logs in Console there is no follow up action, but just be aware that messages will now only display logs for 13 months.

If you perform log extraction via API on a rolling basis, it is important to verify that you are pulling the logs at a frequency that will remain unaffected by this change. 


Programmable Voice

Upcoming changes to log availability for Calls and Conferences GA

Starting August 15, 2020 you will be able to view call and conference logs in Console--and retrieve the resources via GET to the /Calls, /Conferences, and /Participants endpoints--for thirteen months after the resource is created. This represents a significant change as these logs are currently stored indefinitely by Twilio and retrievable via Console and API.  

Before this change goes into effect, we will provide a Bulk Export utility in Console. Bulk Export will generate S3 files containing one day of data per file and deliver the download link via webhook, email, or Console. Records older than thirteen months will only be able to be retrieved via Bulk Export.

If you view logs in Console there is no follow up action, but just be aware that calls and conferences will now only display logs for the previous 13 months.

If you perform log extraction via API on a rolling basis, it is important to verify that you are pulling the logs at a frequency that will remain unaffected by this change.


Programmable Voice

Emergency Caller ID for SIP Interfaces GA

Emergency Caller ID is now available for Programmable Voice SIP Interfaces. Customers are now able to set a single phone number on a SIP Domain as the Caller ID to be used as the Emergency callback number on that domain. This is the phone number that will be used by emergency responders as the callback number in case the call gets disconnected.

Click here to learn more.


Serverless

Studio and Functions are now HIPAA Eligible GA

Studio and Functions can now be used to develop compliant healthcare applications that contain protected health information (PHI) for organizations that are subject to the Health Insurance Portability and Accountability Act (HIPAA). Twilio will sign Business Associate Addendums (BAA) with covered entities and business associates for HIPAA Eligible Products and Services.

Learn more about how to build on Twilio for HIPAA compliance.


Embedding VoIP calling functionality on Android requires adding support for Audio Device switching and routing. This functionality is complex as it requires development and testing to support various Android versions and the variety of input and output device types available.

The new open source Twilio AudioSwitch Library for Android removes this complexity and can be easily embedded in just a few lines of code to handle switching to and selecting the built-in, wired, or Bluetooth mics and speakers seamlessly.

This library is available in open source format and can be found here.

See Video Android quickstart and Twilio Video App for examples of how to utilize this library.


Embedding VoIP calling functionality on Android requires adding support for Audio Device switching and routing. This functionality is complex as it requires development and testing to support various Android versions and the variety of input and output device types available.

The new open source Twilio AudioSwitch Library for Android removes this complexity and can be easily embedded in just a few lines of code to handle switching to and selecting the built-in, wired, or Bluetooth mics and speakers seamlessly.

This library is available in open source format and can be found here

See the Android Voice quickstart for an example of how to utilize this library.


Programmable Voice

Twilio Client JS SDK - End of Support for Microsoft Edge Legacy Browser Deprecated

Twilio Voice Client JS SDK (twilio.js) will officially end support for Microsoft Edge Legacy on September 1st, 2020. After this date, Twilio Client apps used with Microsoft Edge Legacy will no longer be able connect to Twilio to place or receive calls.

For continuity of service, Microsoft Edge Legacy users should upgrade to the latest version of Microsoft Edge or another supported browser, before September 1st, 2020.

For more information and FAQ, check this advisory.


Phone Numbers

Regulatory Bundle Evaluations via Public API Beta

Twilio’s Evaluations API resource is in public beta so you can receive transparent feedback to understand the evaluation and failure reason(s) of your Regulatory Bundle via API.

Resources:


Marketing Campaigns

Single Sends API update GA

The Marketing Campaigns Single Sends API has been updated to simplify the steps to create, schedule, and send Single Sends via the API. Users no longer need to create a template first. To create and save a new Single Send, all that is required is a name. For complete details, please see our overview page and the API reference documentation.


Twilio conference log console page has been updated to reflect the correct duration of conference and participants. Previously, conference and participant durations were displayed based on the duration of the underlying call(s), which did not accurately calculate the duration for scenarios where a call leg spanned more than one conference (i.e. call transfers). Conference duration will now be displayed as the time between conference creation and conference completion. Participant duration will now be displayed as the total time between when the participant joined the conference and left the conference. This is strictly a change to the Twilio console, and does not impact how conferences are billed.


We have added the Task property task_queue_entered_date to all relevant TaskRouter Events to enhance historical reporting and TaskQueue insights.

When retrieving TaskRouter Events history, the task_queue_entered_date is now included with the following Events’ data:

  • task.created
  • task.updated
  • task.canceled
  • task.wrapup
  • task.completed
  • task.deleted
  • task.system-deleted
  • reservation.created
  • reservation.accepted
  • reservation.rejected
  • reservation.timeout
  • reservation.canceled
  • reservation.rescinded
  • reservation.completed
  • reservation.wrapup
  • reservation.failed
  • task-queue.entered
  • task-queue.timeout
  • task-queue.moved
  • task.transfer-attempt-failed
  • task.transfer-canceled
  • task.transfer-completed
  • task.transfer-failed
  • task.transfer-initiated
  • workflow.entered
  • workflow.target-matched
  • workflow.timeout
  • workflow.skipped

To learn more about the Task property task_queue_entered_date, please refer to our documentation on Task properties.
To learn more about the TaskRouter Events resource, please refer to our documentation on TaskRouter Events.


Programmable Voice

Client Insights Preview API End-of-Life Deprecated

The Client Insights preview API is officially end-of-life May 1, 2020 and will no longer respond to API requests. The preview API also powered the Client Insights Dashboard which has been removed from Console and now redirects to the Voice Insights Dashboard.

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

  • Client Call Summary
    • https://preview.twilio.com/insights/Calls/{call_sid}/Summary
    • Call summaries for all call types are now provided via the Summary API
  • Client Events
    • https://preview.twilio.com/insights/Calls/{call_sid}/Events
    • Call events for all call types are now provided via the Events API
  • Client Metrics
    • https://preview.twilio.com/insights/Calls/{call_sid}/Metrics
    • Call metrics for all call types are now provided via the Metrics API
  • Client Reports
    • https://preview.twilio.com/insights/Calls/Report
    • The Reports API is not being directly replaced at this time

If you need assistance moving your application over to the new endpoints we have created a migration guide to assist. For more information, see the initial end-of-life changelog entry and the preview API shutdown documentation.


Marketing Campaigns

Search and filter Single Sends GA

Single Sends in Marketing Campaigns are now easier to find using new search and filter functionality. Users can search for a Single Send by name, or can filter to view all Single Sends by a particular status (draft, scheduled, or triggered) as well as by category.


With Flow publishing support built into the Studio REST API v2, you can now create, publish, and manage your Flows programmatically without having to log in to Twilio Console.

Flow definitions are exposed as JSON schemas and can be easily updated via the Twilio helper libraries and Twilio CLI.

With the new Flows endpoint you can

  • Integrate Flow publishing into your CI/CD pipeline to automate Studio deployments
  • Programmatically move Flows between accounts or subaccounts
  • Create your own custom, branded Studio front-end UI 

The Studio REST API v2 is now available on all customer accounts.

To learn more, read the announcement on our blog or try the quickstart.


Programmable Voice

BYOC Trunking for Programmable Voice is now Generally Available GA

Twilio Bring Your Own Carrier (BYOC) Trunking for Programmable Voice is now Generally Available.  BYOC Trunking is a distinct new offering that allows you to use your existing PSTN Voice Carrier partner(s), keep your phone numbers with that Carrier, and add Twilio Programmable Voice capabilities at your own pace.


  • Add programmability to your existing Phone Numbers by redirecting incoming calls delivered by your PSTN Carrier to Twilio (Termination).  
  • Send outgoing calls directly to your PSTN Carrier, including redundancy and load-balancing across multiple SIP destinations, and use Twilio’s Super Network as a fallback (Origination).  
  • No porting is necessary.

Click here to learn more about BYOC Trunking.


Show more