Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
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.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
    • Call summaries for all call types are now provided via the Summary API
  • Client Events
    • Call events for all call types are now provided via the Events API
  • Client Metrics
    • Call metrics for all call types are now provided via the Metrics API
  • Client Reports
    • 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.

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.

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.

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.

Programmable Voice

Payment Card Industry (PCI) Compliant Voice Recordings GA

Twilio Programmable Call Recordings now allows PCI compliant call recordings within the Twilio Programmable Voice environment. By providing a public key to encrypt recordings and enabling PCI Mode in Console, call recordings can be captured in a PCI compliant manner.

Traditionally, call recordings are used to analyze agent and customer interactions. However, they require special handling when capturing credit card information. To continue to record your voice calls and maintain PCI compliance within Twilio, you must have PCI Mode, Voice Recording Encryption and PCI compliance for Voice Recording enabled using Voice Settings Console page.

Once these settings are enabled on a project, Call Recordings will only be stored by Twilio for 72 hours and must be retrieved within this period. Once deleted, these recordings will no longer be recoverable by either Twilio Console or API request. 

To learn more about Twilio PCI compliance and to access customer responsibility matrix, please vist

Programmable Messaging

Contact Card Support in WhatsApp (VCard) Beta

You can now send and receive contact cards, also known as VCards or VCF (Virtual Contact Files), via WhatsApp! Contact cards let people easily share and add new contacts to their phone book. 

When a user receives and taps on a vCard in WhatsApp, the app will render a preview and allow them to easily call or add the contact to their phone book. 

In WhatsApp, VCards are useful for businesses that send links to users, but have not yet been able to become an Official Business Account. For these businesses, links will only be clickable when the business has been added as a contact. 

To send a vCard, simply send it as a file as you would with any other media.

Flex UI and Flex WebChat UI API References are now available starting from Flex UI v1.19 and Flex WebChat UI v2.4 here:

These API references describe all available public interfaces, methods and properties. It also includes a full list of registered Actions and their payloads, as well as a list of programmable components.

API references are available as Pilot. The Flex team looks forward to hearing your feedback and making further improvements. To submit feedback, use the feedback widget which you can find on each page of the API Reference.

Previously for the Twilio console, we supported two factor authentication via SMS, Voice and the Authy app, to secure customer accounts. With this update, we added support for other TOTP-standard apps, so customers can bring their own authenticator apps to protect their Twilio account with 2FA. This expands the set of options available to customers to secure their login to the Twilio console. To use a TOTP-compliant app, you can enable two factor authentication (2FA) via User Settings, select ‘Another authenticator app’ for 2FA method and follow the steps for setup. For full details, read this help article.

Programmable Voice

Voice Android 5.2 - AudioDevice API GA

The AudioDevice API is an advanced API that can be used to create innovative and sophisticated in-app audio capabilities. For example, enable pre-recorded messages to be played in-call, or apply noise reduction algorithms before playing out the received audio.

An AudioDevice is a logical device that is used to capture and render audio. The captured audio is sent to the remote party, and the received audio is rendered locally. By default, the SDK uses DefaultAudioDevice which uses the mic for capturing and the local speaker/earpiece/headset for rendering. The AudioDevice API allows for the creation of custom audio capturers and renderers. See this example and API docs to learn more about custom audio devices.

Voice Android SDK 5.2.0 package: bintray

API Docs are available docs

Get started with the Quickstart Guide

This Flex UI release brings the following 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.

For a full changelog, visit client libraries release notes:

Flex UI 1.19

Flex WebChat 2.4

Programmable Voice

New Properties in Voice Insights API Responses GA

Voice Insights Call Summary API responses now include new properties for calls placed using the Twilio Voice SDKs. The new fields are:

 Property Description Represents the count of events by severity for the call Represents the count of events by the event group Represents the error code and number of occurrences Represents the user feedback gathered from the SDK
 sdk_edge.metrics.inbound.audio_out Represents the avg/max level for speaker audio
 sdk_edge.metrics.inbound.audio_in Represents the avg/max level for microphone audio
 sdk_edge.metrics.outbound.codec_name Friendly name of the RTP codec for the call
 sdk_edge.metrics.outbound.codec RTP profile number of the codec for the call Direction of the call from the perspective of the SDK Indicates whether DSCP was enabled Indicates if ICE restart was enabled

Voice Insights Metrics API now includes:

 Property Description
 sdk_edge.interval.packets_loss_percentage Represents the percentage of packets lost during the sampling window

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

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

  • Advanced Team View Filters: This feature allows supervisors to search or filter agents by name and activity. You can also define custom filter criteria like teams or skills. Advanced Team View Filters is currently available as a Pilot feature. To enable it, visit the Pre-Release Features Page. You can learn more about this feature within our documentation.
  • Outbound Dialing and Native Dialpad: This feature allows agents to place outbound calls, and developers can build click-to-dial capabilities. Outbound Dialing is currently available as a Public Beta and can be enabled via the Flex Settings page. You can learn more about this feature within our documentation.

For a full changelog, visit the Flex UI release notes.

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

Marketing Campaigns

Clearer test sends GA

Marketing Campaigns supports sending a test email to up to 10 email addresses at a time. Now, when users send a test email, Marketing Campaigns automatically adds “Test -” to the beginning of the subject line. This ensures test recipients know the email is a test and was not yet actually sent to the targeted list or segment.

Twilio Studio now supports programmatically ending an active Execution via the REST API and the Twilio helper libraries. This method is useful in cases where a new REST API-triggered Execution needs to override an existing Execution that is already active for the same Contact. Previously active Executions could only be ended via the Console.

To learn more, visit the API documentation for End an Active Execution.

Programmable Messaging

When lists are not enough - bulk export for messages Beta

A common request is to download large volumes of messaging data. Although this is possible using Twilio’s REST APIs, it can be slow. BulkExport allows you to download all of a day’s messages in a single file, rather than iterating on the list.

Now Enterprise Plan customers can request a date range, or enable automatic daily generation of files. Each file holds a day’s worth of messages exported in JSON. This enables customers who want to manage compliance or load into a warehouse to get a single file to feed to their processes. After Public Beta, this will be available to all Twilio accounts.

For more information on how to set this up, look at the BulkExport API Overview. Then you can start by requesting a day in the past, and getting all those messages in a single file

Updating some Voice settings including PCI Compliance, Call Recording Encryption, and Logging of TwiML, now require the user to have the Owner or Administrator role. A user with a Developer role can only view these settings. This change helps with your implementation of access controls and compliance processes.

To learn more about the roles available and their respective permissions, please click here.

Programmable Voice

Programmable Voice Mobile SDK 1.x EOL Announcement Deprecated

Twilio’s Programmable Voice Mobile SDK 1.x for iOS and Android will officially shut down on July 31st, 2020. After this date, all iOS and Android Apps that use Voice Mobile SDK 1.x for VoIP calls, will no longer be able to connect to Twilio to make or receive VoIP calls.

For continuity of service, upgrade to the latest SDKs and release your app in the App/Play Store, and have your users update before July 31st, 2020.

See this advisory for more information.

Show more