Twilio Changelog

Twilio now provides Bulk Export capabilities in Console for Calls resources as well as an API for programmatic access to the export utility.

Bulk Export generates S3 files containing one day of data per file and delivers the download link via webhook, email, Console, or API. Twilio Enterprise Edition customers can also set daily exports.

You can now import up to 1 million contacts or 5GB of data, whichever is less, using compressed CSV files via the Contacts API. The import endpoint also supports gzipped CSV files.

Twilio now provides Bulk Export capabilities in Console for Calls, Conferences, and Participants resources, as well as an API for programmatic access to the export utility.

Bulk Export generates S3 files containing one day of data per file and delivers the download link via webhook, email, Console, or API. Twilio Enterprise Edition customers can also set daily exports.

Starting February 5, 2021 you will be able to view call logs in Console--and retrieve the resources via GET to the /Calls endpoint--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.

Twilio provides 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.

Starting February 5, 2021 you will be able to view call and conference logs in Console--and retrieve the resources via GET to the /Calls and /Conferences 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.

We 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.

Voice Insights Dashboard can now be filtered by call direction and edge location.

Direction filtering allows you to compare call behavior between different call flows. For example, you can now investigate differences in network performance between Trunking Originating or Trunking Terminating calls.

Media region filtering has been available for some time, but we have updated the labeling to reflect the new Edge Location format; e.g. Ashburn (us1).

With Twilio Functions invocations moving to General Availability, you now have guaranteed service level agreements for functions and assets that you invoke. Twilio Functions replaces the need to host or stand up your own web server to serve TwiML or any other HTTP responses, underpinned by your own infrastructure and programming logic. Functions gives you the ability to develop programmatic logic to handle the orchestration of discrete tasks with the convenience of pre-built cloud infrastructure.

You can now perform inbox rendering tests across new devices and inbox providers. Inbox rendering tests help you ensure that your emails are displaying as intended across your customers’ preferred device types and inbox providers.

Customers can now view the time taken by Twilio to process their messages via the Latency report visible in the Programmable Messaging Insights console.

Message latency is calculated as "Time Twilio sent the message - Time customer made message request API call." Customers can also view the limits applied to their individual senders, messaging services, and accounts via Modals in the Insights report.

This blog contains details about the product and this new guide explains how applications can be built to handle scale from the beginning.

The Plugins Dashboard now displays all legacy plugins currently enabled for your agents. With this feature, the Plugins Dashboard is the source of truth for all plugin information in Flex. This makes it easier for admins to track the migration of their legacy plugins to the latest Plugins API. Admins can access the Plugins Dashboard via the Admin UI.