Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
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.


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 https://www.twilio.com/pci-compliance


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.


Show more