Skip to main content

Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all
SendGrid Email API

Bounce Classifications now in Twilio SendGrid Event Webhook GA

Bounce Classifications are now included in the Twilio SendGrid Event Webhook. The event webhook is a powerful way for you to consume event level data to gather more insight to your email performance. Twilio SendGrid's Event Webhook will allow you to use a data aggregator of your choice and notify a URL via HTTP POST with information about events that occur as Twilio SendGrid processes your email. The addition of Bounce Classifications to the Bounce and Deferral event payloads will provide additional insight as to why an email was bounced, blocked, or deferred.


Twilio SendGrid Platform

Limitations to Category Statistics for All Customers GA

Twilio SendGrid started limiting category statistics for new customers only on March 16, 2022. Beginning May 16, 2022, Twilio SendGrid will limit category statistics for all customers on a seven-day rolling basis. This means all categories will be available for the first seven days. After seven days, the top 100 categories will be retained for free customers, and the top 1,000 will be retained for paying customers.

Customers who require access to all category statistics can use the Event Webhook to retrieve and retain the data on their own systems as long as they save it within seven days of first sending the event.

Twilio SendGrid accounts created before March 16, 2022 will temporarily retain access to all category statistics created before May 16, 2022. However, access to unlimited category data is transitory and should not be expected to persist.

For more information about how this change works, please see the "Limitations" section of our "Working with Categories" documentation.

Many customers find that Unique Arguments, which are not limited, are the best solution for their needs. See the "Categories vs Unique Arguments: Benefits & Limitations" blog post to better understand these two tracking tools.


The Marchex Transcription with Conversation Intent and Outcome is now available in Twilio’s Marketplace Add-ons catalog. This Marketplace Add-on identifies the most important attributes of your phone calls such as the primary intent of the caller and outcome of the conversation, using Marchex’s AI powered conversation intelligence capabilities. To learn more about this Add-on and how to enable it for your application, visit the Marketplace Marchex Add-on in the Twilo Console.


Programmable Voice

External Storage for Call Recording is now available GA

External storage for call recordings is now available for all voice customers. Call recordings will remain to be stored at Twilio by default. Alternatively, customers can enable external storage and automatically upload recording files directly to an AWS S3 bucket without additional charges.

To determine whether the recording’s media file is stored externally or at Twilio, a new property mediaUrl has been added to the call recording resource with the full URL location of the file; this will apply also to existing RecordingUrl property from the RecordingStatusCallback. When external storage is enabled, recording files from two-party calls get uploaded as dual-channel regardless if they are requested to be mono or dual-channel. Recording resource metadata is available at Twilio until explicit deletion.

Prior to this release, recording status callbacks could be used for automating recording file download and deletion but required additional software development and additional API requests by customers to set up this workflow.

Learn more.


You can now manage the configurations related to a unique address (i.e. a WhatsApp or SMS phone number) within Conversations. This resource allows you to specify which addresses should auto-create a Conversation upon receiving an inbound message.

With this feature, you can also automatically attach a Conversation-scoped Webhook to the auto-created conversation.

Explore the Address Configuration API documentation and give it a try!


On May 3rd, 2022 responses to API requests for CSV representation of Incoming Phone Number and Outgoing Caller ID resources for both list and instance will change; specifically the order of the columns may be different.

The order of the columns in the CSV is not defined and may change when new fields are added to the API response. Your application design should be resilient to changes in the order of the columns in the CSV response.

See our docs for more information about how to leverage CSVs with Twilio.


Elastic SIP Trunking

Diversion header validation for termination calls GA

When Twilio receives termination traffic from your communications infrastructure to the PSTN, your SIP message can sometimes include SIP Diversion headers if the call was previously forwarded. Twilio will forward SIP Diversion headers it receives to the carriers.

To combat any malicious addition of Diversion headers, Twilio will now check all Diversion headers it receives that contain the Twilio domain. Twilio will verify that the phone number included in the header matches one associated with your Twilio account (either a Twilio number owned by the account or a verified Caller ID). If the header fails this check, Twilio will remove the header.

See the docs for more information.


Programmable Voice

Reminder: Upcoming changes to Programmable Voice behavior GA

As previously communicated, we are continuing to roll out Enhanced Programmable SIP Features to all accounts. This could represent a behavior change for some call flows, including calls that do not use Programmable SIP. For more information, see our docs page detailing the changes in Programmable Voice behavior.


Programmable Voice

Conference Insights General Availability GA

Every conference on Twilio is now being analyzed and aggregated by Conference Insights to provide visibility into participant behavior and offer prescriptive recommendations for resolving common quality and configuration issues. 

Conference and Participant Summaries provide multiple views into conference metadata which allow users to see conference parameters, investigate participant event timelines, and understand detected quality issues. Both summary records return useful metadata about the conference and its performance.

Conference and Participant Summaries are available via Console, API and Event Streams.

Conference and Participant Summaries are included with all conferences at no additional cost via Console. Voice Insights Advanced Features are required for API and Event Stream access. 

For more information see docs.


Programmable Voice

Regional Voice is now Generally Available in Australia GA

Twilio’s home region in Australia is now generally available, with Twilio Voice being the first available product. This gives you control over where Voice data is ingested, processed, and stored, enabling you to keep personal data at rest within the region of your choice. It also offers data processing that is closer to your applications, thus reducing latency and improving application performance for highly interactive, real time interactions.

To learn more on how to get started with Twilio Voice in Australia, head over to our developer docs.

Click here for documentation about Twilio Regions.


Usage Insights by SIM for Super SIM in Console Beta

The new Usage by SIM tab added to Super SIM Insights displays a per-SIM breakdown of your Super SIM data usage. Each row in the table shows how much data a SIM downloaded or uploaded and the total amount. Because the rows are sorted by total amount, you can easily identify which of your Super SIMs have exchanged the most data over a specified time period. View the top entries in the table to quickly single out any outliers. Filter the results by Fleet, Country, or Network to further slice-and-dice your usage.

In addition, the rightmost column contains spending information for each record. This data allows you to better understand your per-device spend on Super SIM usage. You can draw various insights, such as which of your SIMs have incurred the highest costs. It is particularly helpful to decouple data consumption and monetary spend into separate entries because different networks charge different rates. As such, although one SIM might be consuming less data than the other, it could still have incurred higher costs if it were operating on a more expensive network.  

Access Usage Insights by SIM in Console via Monitor > Insights > Super SIM and select the “Usage by SIM” tab.

usage-insights-by-sim-for-super-sim-in-console


Frontline

Voice is now HIPAA Eligible on Twilio Frontline Beta

Voice can now be used on Twilio Frontline 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 Voice in Twilio Frontline and how to build on Twilio for HIPAA compliance.


Twilio sells Call per second (CPS) which allows customers to increase the rate at which Twilio will execute new calls created via the Calls API. CPS is sold and billed in us1 and the CPS value is replicated to other Regions (e.g. au1/ie1) at no additional cost to allow customers to operate across all timezones. The replication of the CPS value also allows services to fallback to a different Region in the event that a Region becomes unavailable. Twilio has updated the Acceptable Use Policy regarding concurrent utilization of CPS across Regions; specifically persistent maximum utilization of CPS in multiple Regions concurrently is prohibited. For more information, see the Programmable Voice: No Concurrent Voice Calls per Second in Multiple Home Regions section of the AUP.


Twilio has completed validation of the integration between Flex and Lionbridge Language Cloud real-time language translation solution. Using a database of over 110 languages, this integration enables your agents to send SMS, Chat or WhatsApp messages in their native languages, and have customers read them and send return messages in their native languages.

To learn more about Lionbridge capabilities and how to enable it for your application, visit our integration documentation.


Programmable Voice

Programmable Voice 2008 API End-of-Life Deprecated

As previously communicated, the 2008 version of our Programmable Voice API has reached end-of-life and requests made to 2008 endpoints or resources will not receive responses. We have discovered a small subset of requests to 2008 resources that were not entirely shut down during the previously communicated end-of-life timeframe. Starting May 2, 2022 all requests to any 2008 Voice endpoint will receive a 404 response from Twilio.


When users message a business from a "Click to WhatsApp" advertisement, Twilio will now pass additional information to inbound message webhook regarding the advertisement the user clicked on. This allows businesses to create workflows in WhatsApp that intelligently respond based on the originating advertisement. Businesses can also better understand their advertisement’s performance by tracking user responses to an advertisement.

To learn more about the new properties that are included on our request to your webhook, visit https://www.twilio.com/docs/messaging/guides/webhook-request#whatsapp-specific-parameters.


Programmable Video

Video Insights is Now Generally Available GA

Video Insights brings self-service tooling to the Twilio Console to help you observe application usage and quality, discover trends across all your rooms and participants, and troubleshoot end-user issues. You can use Video Insights to build higher-quality video experiences for your customers, reduce churn, and scale confidently. 

As part of the general availability launch, you will now have a revamped experience to filter and explore your rooms, dropdowns for segmenting your participants by signaling_region and end_reason via the Insights Dashboard, and much more. 

Get started now by visiting Video Insights in the Twilio Console or refer to our blog post to learn more.


Elastic SIP Trunking

Elastic SIP Trunking TLS v1.0/1.1 Deprecation

As per Internet Engineering Task Force (IETF) recommendations, Twilio strongly recommends the use of TLS version 1.2, and has deprecated default support for TLSv1.0 and TLS v1.1 when connecting your SIP Infrastructure to Twilio Elastic SIP Trunking.  If your infrastructure requires TLSv1.0 or TLSv1.1, you can configure your Twilio Account to allow these deprecated versions in your console under Voice → Settings → Allow Deprecated SIP/TLS versions.

In order to reduce service disruptions for existing customers, we have already applied this configuration to existing accounts that have used or provisioned SIP Domains and/or Elastic SIP Trunks. You can review the setting in your Twilio console, and disable the configuration, if your SIP server is already using TLSv1.2.  New accounts will not have this configuration applied, meaning that these accounts will be configured to use only TLSv1.2 by default. The ability to “Allow Deprecated SIP/TLS Versions” is available to these accounts, but if so, this configuration needs to be enabled in the account’s console.

For more information, see our documentation.


Programmable Voice

Programmable Voice SIP TLS v1.0/1.1 Deprecation

As per Internet Engineering Task Force (IETF) recommendations, Twilio strongly recommends the use of TLS version 1.2, and has deprecated default support for TLSv1.0 and TLS v1.1 when connecting your SIP Infrastructure to Twilio Programmable Voice.  If your infrastructure requires TLSv1.0 or TLSv1.1, you can configure your Twilio Account to allow these deprecated versions in your console under Voice → Settings → Allow Deprecated SIP/TLS versions.

In order to reduce service disruptions for existing customers, we have already applied this configuration to existing accounts that have used or provisioned SIP Domains and/or Elastic SIP Trunks. You can review the setting in your Twilio console, and disable the configuration, if your SIP server is already using TLSv1.2.  New accounts will not have this configuration applied, meaning that these accounts will be configured to use only TLSv1.2 by default. The ability to “Allow Deprecated SIP/TLS Versions” is available to these accounts, but if so, this configuration needs to be enabled in the account’s console.

For more information, see our documentation.


Programmable Voice

Generic Pay Connector now available in Public Beta Beta

The Generic Pay Connector is now available in Public Beta. The Generic Pay Connector is responsible for collecting sensitive payment information in a PCI compliant manner and passing it downstream to the payment processor of your choice - configured by you within the connector.

This connector supports 2 transaction types: charge and tokenization. The API provides flexibility to the payment processors to define the nature of the transaction taking place. 

With the release to Public Beta, a new generic endpoint “/” is available and the transaction type is now a method within the generic endpoint. With that, legacy endpoints - “/charge” and “/tokenize” available in the Generic Pay Connector are going to be deprecated in the next 30 days. Applications using legacy endpoints in private beta would need to be modified to consume from the root endpoint “/”.

With this release, there is also support for passing custom parameters in the request to the payment processor. These features are supported for both <Pay> verb and Agent Assisted Pay.

Learn more about this feature in our API docs.


Show more