Skip to main content

Twilio Changelog

Additions and changes to the Twilio platform

Filter by:Clear all

The change we announced in March 2022 to API response headers for all SMS and MMS messages sent via Twilio’s Messaging APIs has been canceled. The updates to our terms and policies, which were jointly announced with the potential pending content verification API response header change, are unaffected by this announcement and remain in effect.

Twilio continues to strive for high message deliverability and to keep consumers safe. Thank you for doing your part in promoting trusted communications by ensuring your compliance with Twilio’s Acceptable Use Policy and Messaging Policy and securing proper consent from senders and recipients before messages are sent.


Programmable Voice

Updates to IBM Watch Speech to Text AddOn Language Models GA

The previous-generation language models that are currently available with IBM Watson Speech to Text AddOn will be deprecated and stop functioning as of March 3rd 2023. To avoid any issues with transcribing your call recordings use IBM Speech To Text AddOn, please update to use next-generation language models as soon as possible. 

The following table has the mapping between previous generation language models, and the next generation language models to make it easier for you to make appropriate changes. We recommend that you make this change at your earliest convenience. 

Previous Generation ModelNext Generation Model
en-US_NarrowbandModelen-US_Telephony
en-GB_NarrowbandModelen-GB_Telephony
es-ES_NarrowbandModeles-ES_Telephony
pt-BR_NarrowbandModelpt-BR_Telephony
zh-CN_NarrowbandModelzh-CN_Telephony

While you can continue to use the previous generation models until March 3rd 2023, going forward you will only be able to select next generation models with any new installation of IBM Watson Speech to Text Addon


To learn more about the changes, please visit IBM Speech to Text documentation.


Twilio SendGrid Platform

Twilio SendGrid Releases Domain Connect Support for GoDaddy GA

Twilio SendGrid has launched support for Domain Connect with GoDaddy to improve the Domain Authentication process. The updated Twilio SendGrid user interface eliminates the need to manually copy and paste CNAME records from Twilio SendGrid to GoDaddy, allowing you to onboard more quickly and start sending mail. Customers are now able to click a button and sign into their GoDaddy accounts from within the SendGrid platform. Twilio SendGrid will then authenticate their domains automatically by making the necessary DNS entries for them.

There are no other changes to existing capabilities. No action is required for customers at this time.


We are keeping your runtime up to date in accordance with industry standards. Based on the Node.js support schedule, Node.js v14 will no longer be in Maintenance long-term support (LTS) status after April 30, 2022. Production applications should only use releases of Node.js that are Active LTS or Maintenance LTS.

Your currently deployed functions will continue to execute on the existing Node.js v14 runtime if no changes are made

Follow these instructions to upgrade, test, and deploy your code and ensure a safe transition to Node.js v16.


This release improves Flex UI’s resiliency by updating functionality used in conferences, outbound calling and voice transfers to remove dependencies.


Programmable Messaging

[U.S. A2P 10DLC] Updates to the Campaign Creation Process Beta

Twilio has released changes to the US A2P 10DLC Campaign creation process in the Twilio API and Twilio Console to reflect the latest ecosystem guidelines. These changes include collection of new fields regarding user consent (e.g., opt-out keywords and auto-reply messages), as well as enforcement of length requirements to existing and new fields. Please read more about this change from the Twilio support article, and check out code samples and API guidelines from Twilio docs.


Twilio C# Helper Library major version 6.x is now available.We ensured that you can upgrade to the 6.x version without any breaking changes

Behind the scenes C# Helper is now auto-generated via OpenAPI with this release. This enables us to rapidly add new features and enhance consistency across versions and languages.

To learn more about the C# Helper Library, check out our docs.


Twilio Alarms, a near real-time monitoring and alerting experience for Twilio customers, is now Generally Available (GA).

The first full scale implementation of Alarms supports Error Logs. This enables you to proactively monitor error logs at the minute level and receive a notification whenever there is a spike in errors, warnings, or informational events of interest, across your Twilio applications.

You can learn how to create and use Alarms with this Twilio guide or watch this demo.

We are sunsetting our old Alert Triggers product. If you have created Alerts on our old platform, they have already been migrated onto this new Alarms platform. You will be able to access these in the Manage Alarms page


In 2H 2023 Twilio will be updating the media IPs and port ranges for Frontline calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you may need to update your internal network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so could result in one-way audio and dropped calls.


In 2H 2023 Twilio will be updating the media IPs and port ranges for Flex calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000 to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.


Elastic SIP Trunking

Upcoming changes to Twilio Voice Media IP Addresses GA

In 2H 2023 Twilio will be updating the media IPs and port ranges for Elastic SIP Trunking calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.


Programmable Voice

Upcoming changes to Twilio Voice Media IP Addresses GA

In 2H 2023 Twilio will be updating the media IPs and port ranges for SIP and Voice SDK calls in all regions. We will be moving from a per-region IP range allocation to a single global range; 168.86.128.0/18. Additionally, we will be expanding the media port range from 10000-20000, to 1024-65535.

We are making this change to provide flexibility, reliability, and scalability. There is no action required at this time, and we will provide a more precise timeline approximately six months before the change. At that time you will need to update your network infrastructure to ensure that you have whitelisted the full IP and port ranges. Failure to do so will result in one-way audio and dropped calls.


Programmable Voice

Upcoming changes to withheld caller ID behavior for <Dial> calls GA

Twilio is changing how we persist caller ID information for <Dial> calls where the inbound caller ID is withheld; e.g. ANONYMOUS, RESTRICTED, etc. Today Programmable Voice translates the alpha string into digits. This behavior will change and we will begin to persist the alpha string from the inbound call to the outbound <Dial> leg for calls where the caller ID is withheld by the calling party.

This represents a significant change in the behavior of our APIs and developers will need to ensure that their systems can gracefully handle alpha characters in the To and From fields for requests and responses to the /Calls API, in TwiML,webhooks, and in status callbacks.

If the callerId parameter is used with the <Dial> verb, the outbound caller ID will reflect what was provided with callerId, regardless of the caller ID on the inbound call.


Twilio SendGrid Platform

Twilio SendGrid is Updating our Mailbox Provider Stats Features GA

Twilio SendGrid has always grouped your email statistics by mailbox provider in our console. This allows you to easily see how your email is performing at Yahoo compared to Microsoft, for example. Our system also helps clean up this data by grouping mailbox providers together. On November 16, 2022, Twilio SendGrid will release an update to our current Mailbox Provider groupings that will make this part of our application even more powerful. Specifically, we will be adding more mailbox providers to our list, increasing from 50 to almost 250. This will result in far less data being lumped into the “Other” bucket when you review your mailbox provider statistics.  Check out our blog post to learn more about the change and see examples for more information.


We are launching a new attribute `requireMatchingInputs` within <Prompt> verb which is used in conjunction with the `for` attribute to prompt the caller to enter a specific payment detail twice. The first <Prompt> verb prompts the user to enter a given payment information. 

The second <Prompt> which contains `requireMatchingInputs` set to `true` will give the caller a different prompt asking the caller to enter the information again. Once the customer enters the information, both inputs are validated against each other and if they match, they will be sent to the downstream payment gateway for processing. 

This attribute works for ACH-debit <pay> transactions of type purchase/tokenization that require users to enter a bank account number or routing number. This enhancement was introduced to catch any user input errors upfront, reducing the error rates reported by payment gateways to meet the error thresholds defined by NACHA.

For more information about this feature, check out the API Docs.


CSV Download for Super SIM Usage Insights in Console Beta

Super SIM Usage Insights now lets you export a CSV file containing your SIMs’ usage record data. With just the click on a button, you can download an extract of the table currently being displayed in the browser. Having this data in the form of a CSV allows you the flexibility to perform subsequent analysis using any application of your choice – a database, spreadsheet, or data visualization tool.

All of the Usage Insights tabs support the CSV Download feature:

  • Usage by Time
  • Usage by SIM
  • Usage by Fleet
  • Usage by Country
  • Usage by Network

Access CSV Download for Super SIM Usage Insights in Console by navigating to Monitor > Insights > Super SIM and clicking on the button labeled “Export CSV”.

usage-insights-csv-download


Conversations

Conversations API Chat channel now available in Ireland GA

We are excited to announce that the Conversations API is now generally available in Ireland (chat only). The availability of Conversations API in Ireland gives you control over where you data is processed and stored. It also offers data processing that is closer to your applications, therefore reducing latency and improving performance.

Click here to learn more on how to get started with Conversations API in Ireland.


Microvisor

Twilio Microvisor now in Public Beta Beta

Twilio Microvisor is now in Public Beta. Microvisor provides managed connectivity as well as managed security for the lifetime of IoT devices. With Microvisor, you can continuously debug and improve a connected hardware product after it has been mass-manufactured and deployed to the field – by offering unbrickable over-the-air firmware updates and secure remote line-by-line debugging live on deployed devices. Microvisor leverages Arm TrustZone to achieve security and failsafe connectivity through hardware-level separation of communications and application and a hypervisor architecture.

Microvisor_ConceptualDiagram_withTwilio

The Public Beta release includes:

For a peek into how Microvisor works in action, watch this video. For more background on the Microvisor architecture and feature set, read our blog post. For pricing, please review this page.


The Virtual Agent for Google DialogFlow CX is now available in public beta. This connector supports integration with Google’s DialogFlow CX edition benefiting from its advanced functionalities such as detecting the welcome intent, barge-in, DTMF, support for multiple languages, custom voice models, status callbacks that contain sentiment scores, intents triggered, call status, etc. 

After this release, we have 2 connectors available for customers based on their needs - Virtual Agent connector for Google DialogFlow ES and Virtual Agent connector for Google DialogFlow CX/CCAI connector.

In order to access Google DialogFlow CX capabilities, create a new Dialogflow CX agent in your Google Cloud Platform (GCP) project, and grant Twilio service account permissions to execute the virtual agent through Google’s one-click integration feature which allows for easier onboarding of Dialogflow CX Connector containing agent details. You can then connect your Twilio phone number to the Studio widget or TwiML to invoke the Dialogflow CX Virtual Agent.

More information available here.

Learn more about this feature in our API docs.


When requesting a Super SIM eSIM Profile from the /ESimProfile API, you can now request that the eSIM profile be reserved with a matching ID by setting the new generate_matching_id request parameter to true. When you reserve a profile this way, you don’t need to provide the EID of the eSIM that will use the profile, which depending on your use case may be very difficult to know ahead of time or obtain. 

When you want to download and install the eSIM profile, you will need to provide the matching ID to your device along with the SM-DP+ URL, both of which can be read from the ESimProfile when your reserved profile is available. The combined SM-DP+ URL and matching ID is often referred to as an “activation code” and often provided to end users via a QR code that they scan with their device during the workflow to add a new eSIM profile. 

Refer to the docs to learn more about eSIM Profiles and different eSIM download methods.


Show more