Changelog

Unified Login for SendGrid Marketplace Customers

Fri, 16 Oct 2026 02:00:00 -0400

SendGrid marketplace customers can now take advantage of the Unified Login feature that lets you create a Twilio login for every individual user accessing your SendGrid account. This provides a more secure access pattern with the ability to define permissions for each user instead of a single, shared admin permission set.

When accessing your SendGrid marketplace account from one of the marketplace integrations - Microsoft Azure, Google Cloud, Heroku, or Amazon Web Services - you will be prompted to provide an email address to create your Twilio login. If you already use another Twilio product and have an existing Twilio login, you can use that email address and password for SendGrid access.

This will be rolled out over the next couple weeks for all SendGrid marketplace customers. For more details, see the documentation here.

Twilio Cohorts for Native List Building and Bulk Messaging

Wed, 14 Oct 2026 03:00:00 -0400

Twilio Cohorts is now available in Private Beta, providing a set of APIs designed to handle list building, audience segmentation, and bulk execution natively within the Twilio platform. Set up your customer profiles, segment them, and trigger messages using your existing Twilio account.

Twilio Cohorts includes:

Dynamic List Building & Segmentation: Define customer traits and query dynamic audiences directly within Twilio.
Native High-Volume Delivery: Pass a single CohortID when triggering a send with the Twilio Email API or the Twilio Bulk Messaging API (supporting Email, SMS/MMS, RCS, and WhatsApp) without writing custom batching logic.
Unified Execution: Streamline multi-channel workflows and eliminate custom queuing or backend rate-limiting logic.

Coordinating high-volume delivery across Email, SMS, RCS, and WhatsApp alongside your native Twilio data has never been easier.

To request early access to the Private Beta, submit a request form. For API details and technical guidance, see the Twilio Cohorts documentation.

Intelligent Alerts in the new Twilio Console

Tue, 13 Oct 2026 01:00:00 -0400

Intelligent Alerts is now available in the new Twilio Console, giving Messaging customers a more unified and consistent way to investigate anomalous events. This update includes improved alert summaries, the ability to provide feedback on alerts, and a dynamic set up notifications prompt when email alerts have not yet been configured.

Voice Insights now tags HD audio calls

Fri, 09 Oct 2026 03:00:00 -0400

Voice Insights now tags calls as HD Audio when they connect with the AMR-WB or Opus codec.

Use the tag to confirm your endpoints negotiated what you configured, and to correlate HD usage with transcription accuracy, AI agent performance, and customer satisfaction.

Calls that carry HD audio are tagged as Downsampled when the longest portion of the call connects to a component or another endpoint that does not support HD. Twilio converts the audio to narrowband to keep the call connected.

Both tags appear in the Call Summary in Console, in the Voice Insights REST API, and through Event Streams. You can also filter the Call Insights dashboard by either one.

Learn more in our Call Summary documentation.

RCS messaging now supported on all major Canadian carriers

Thu, 08 Oct 2026 19:00:00 -0400

You can now send RCS messages to Rogers phone numbers, completing RCS coverage across Canada’s major carriers.

When requesting RCS Sender approval in Canada, Twilio will now submit the Sender for review across all major carriers, including Rogers. RCS Senders already approved by other Canadian carriers will automatically be submitted to Rogers for review and approval. No action is required.

To start sending branded RCS messages, go to the Twilio Console to create and submit an RCS Sender.

For more information, see our RCS documentation.

Live support coverage across the Twilio platform and Segment

Thu, 08 Oct 2026 00:00:00 -0400

Starting October 5, 2026, paid support customers can reach Twilio through live chat for help with Segment and all Twilio platform applications and products.

TaskRouter and Studio are now available in Public Beta in Ireland (IE1)

Tue, 06 Oct 2026 00:00:00 -0400

TaskRouter and Studio are now available in Public Beta in Twilio's Ireland (IE1) Region, giving you EU data residency and control over where your contact center routing and workflow automation data lives.

Traffic Optimization Engine (TOE) is now generally available

Tue, 06 Oct 2026 00:00:00 -0400

Traffic Optimization Engine (TOE) is now Generally Available for short code and toll-free traffic in North America and all sender types internationally, for customers to scale and send high volumes of traffic anywhere in the world.

Segment Conversation Memory Integration now in GA

Mon, 05 Oct 2026 14:30:00 -0400

The Segment Conversation Memory Integration is now in GA. You can now sync long-term customer profile data, like identity and lifetime value, from Segment into the sub-second recall of Conversation Memory, enabling both AI and human agents to instantly access unified context during live interactions. This eliminates cold starts, reduces repetitive questions, and delivers highly personalized, continuous customer experiences across all channels.

The integration continuously syncs long-term customer profile data, such as identity and historical traits, from Segment directly into Conversation Memory. Customers configure this transfer using either "Memory Sync" to rapidly import their entire profile database or "Memory Destination" to target specific user cohorts via Segment Audiences. During setup, Segment profile traits and identifiers are mapped to corresponding semantic trait groups within a Memory Store. Once active, trait updates flow in real time, allowing AI or human agents to instantly query the Memory Store for up-to-date customer context during live interactions.

To get started, read the Segment Conversation Memory Integration | Twilio, and browse the Conversation Memory (Actions) | Twilio.

Short Codes are now supported in Data Residency for SMS (EU)

Mon, 05 Oct 2026 19:00:00 -0400

Short Code numbers are now supported as SMS senders in Twilio's Ireland (IE1) region for EU data residency. When using this feature, SMS message personal data sent or received via Short Codes is stored and processed in the EU up to the point it reaches Twilio's connections with telecommunications providers.

With this release, the IE1 region supports the following features:

Short Code senders: Send and receive SMS messages with short codes in IE1.
Region Configuration API: Configure short codes for IE1 using the V3 region configuration API.
Short Codes API: Set IE1 inbound webhook configurations using the ShortCodes resource.
Messaging Services API: Add short codes to IE1 messaging services using the service ShortCodes subresource.

To learn more and get started, see the developer documentation.

Voice Insights now shows why carriers block your calls

Thu, 01 Oct 2026 03:00:00 -0400

Voice Insights now tells you why a carrier blocked your call and how to reach that carrier for redress.

The FCC requires carriers that block calls using analytics to return the reason header to the caller. It names the network that blocked the call and tells you how to contact them: a URL, a phone number, or an email address. Until now a blocked call showed you only a 603 response. Now you can see which network blocked it and petition them directly.

The reason header appears alongside Last SIP Response in the Call Summary, in Twilio Console, the Voice Insights REST API, and Event Streams.

If you are seeing a high volume of 603 responses, confirm your traffic is signed with STIR/SHAKEN and registered with Twilio Voice Integrity before you start filing redress requests.

Learn more in our Call Summary documentation.

Batch Transcription Configuration is now Generally Available!

Thu, 01 Oct 2026 03:00:00 -0400

Tune transcription without touching your code: engine, model, language, and destination live in a reusable configuration, so changing any of them is one update that every subsequent transcription picks up. Results are delivered via webhook or stored downstream in Conversation Orchestrator for persisted storage and Operator analysis.

Twilio Video Media SDK for Node.js now in Public Beta

Wed, 30 Sep 2026 19:00:00 -0400

The Twilio Video Media SDK for Node.js is now in Public Beta. Your server-side app can securely join a Video Group Room as a participant and work with decoded audio and video frames directly, so you can run AI and media processing such as transcription, computer vision, or compliance monitoring on your own infrastructure, without the overhead of a headless browser.

Your app reads decoded frames from other participants and publishes frames back into the Room as a virtual camera or microphone. This Media SDK shares the Room, Participant, Track, and Access Token model of the Video JavaScript SDK, so most concepts carry over. Install it from npm as @twilio/video-node-sdk. It requires Node.js 24 or later on x86-64 Linux, and the Media SDK participant counts and bills as a standard Group Room participant.

To get started, read the Video Media SDKs overview, follow the quickstart, and browse the AI/ML example applications.

Account Rate Limits on Content API

Wed, 30 Sep 2026 03:00:00 -0400

What is Changing?

To improve platform stability, endpoint reliability, and system performance, Twilio is introducing standardized rate limits for Content API requests.

Rate limits will be enforced at the account level. Requests exceeding these limits will receive an HTTP 429 Too Many Requests status code.

Rate Limits by Endpoint

Read Operations

Fetch Content (GET /v1/Content/{Sid}): 100 RPS
Fetch Approval (GET /v1/Approval/{Sid}): 100 RPS
List Content (v1 & v2) (GET /v1/Content): 20 RPS
List Content & Approvals (v1 & v2) (GET /v1/ContentAndApprovals): 20 RPS
List Legacy Content (GET /v1/LegacyContent): 20 RPS

Write Operations

Create Content (POST /v1/Content): 100 RPS
Create Content Approval Request (POST /v1/Approval): 100 RPS
Update Content (POST /v1/Content/{Sid}): 20 RPS
Delete Content (DELETE /v1/Content/{Sid}): 100 RPS
Update Content Approval Request (POST /v1/Approval/{Sid}): 20 RPS

What You Need to Do

Implement Exponential Backoff: Ensure your application can handle HTTP 429 status codes by incorporating backoffs and retries.
Audit High-Volume Pipelines: If your service executes bulk script operations (such as creating or deleting content templates in high-concurrency bursts), adjust your client throttling to remain within these thresholds.

WhatsApp Embedded Signup Version 4

Wed, 30 Sep 2026 02:00:00 -0400

We are excited to announce General Availability support for WhatsApp Embedded Signup Version 4. This release upgrades the existing WhatsApp Self Sign-Up onboarding flow in the Twilio Console, seamlessly aligning with WhatsApp’s recent account updates to deliver a cohesive, up-to-date sender registration process. The upgraded experience simplifies phone number setup and incorporates MM API Terms of Service acceptance directly within the flow. This update is required as part of WhatsApp’s planned deprecation of older versions, ensuring uninterrupted onboarding for WhatsApp senders.

On-demand rule execution and Conversation Metadata now generally available with Twilio Conversations

Sun, 27 Sep 2026 01:00:00 -0400

Today, we are launching two new capabilities with Twilio Conversations– On-demand rule execution for Conversation Intelligence and Conversation metadata for Conversation Orchestrator

Twilio Voice React Native SDK adds Expo Support

Fri, 25 Sep 2026 00:00:00 -0400

The Twilio Voice React Native SDK now supports Expo, the framework most new React Native apps start from.

Twilio Profiles widgets are now available in Studio

Thu, 24 Sep 2026 00:00:00 -0400

Twilio Studio now includes two widgets for working with Twilio Profiles directly from a flow: Resolve Profile and Create or Update Profile.

Conference list endpoint will default to in-progress conferences only on September 30, 2026

Wed, 23 Sep 2026 00:00:00 -0400

Starting September 30, 2026, the Conference list endpoint (GET /2010-04-01/Accounts/{AccountSid}/Conferences.json) will default to returning only in-progress conferences.

Introducing Provider Failover and “Auto” mode Provider selection for Real-Time Transcriptions on October 22, 2026

Tue, 22 Sep 2026 02:00:00 -0400

Starting October 22, 2026, Twilio Real-Time Transcriptions automatically starts transcription sessions on a second speech provider when a customer’s primary provider doesn’t connect. Failover is enabled for all existing Real-Time Transcriptions accounts on that date, and it routes only within a customer’s existing region. Use of failover is optional and can be opted out of per sub-account in Console.

Verify Events: Verification Attempt DLR event type will be discontinued

Tue, 22 Sep 2026 01:00:00 -0400

The Attempt DLR event type will be discontinued after September 22, 2026 at 10:00PM UTC. Learn more about using discontinued Event Types in Discontinued Event Types. From this point on, Twilio may stop sending new events for the Attempt DLR event types, even if you have a subscription to them. You will continue receiving events normally from any other Event Types in your subscriptions.

Twilio Heightened Awareness Period (HAP) – November 19, 2026 - January 4, 2027

Thu, 17 Sep 2026 02:00:00 -0400

Between Thursday, November 19, 2026 and Monday, January 4 2027, Twilio will enter a Heightened Awareness Period (HAP) to help ensure reliable message delivery during peak traffic times, such as Black Friday and Cyber Monday.

During this period, message sending rates to U.S. destinations will be monitored and may be limited at the account level for toll-free, short code, and 10DLC numbers.

Accounts that send high volumes of messages from short codes or toll-free numbers may be temporarily migrated to Market Throughput during the HAP. Customers will be notified via email if their account is affected. Market Throughput doesn’t affect 10DLC numbers, which will continue to live on Account Based Throughput.

For more information on how throughput limits may be impacted and what actions to take, customers can reach out to their Twilio account team.

Twilio integration with Salesforce Service Cloud Voice is now Omnichannel

Thu, 17 Sep 2026 01:00:00 -0400

We’re excited to announce that Twilio integration with Salesforce Service Cloud Voice now supports WhatsApp and SMS, alongside existing support for Voice and listed on the AppExchange.

This release comes with the following enhancements:

Route SMS and WhatsApp conversations through Twilio TaskRouter into the Salesforce Omni-Channel widget, using the same presence, skills, and capacity model as voice
Handle messaging conversations and voice calls concurrently in a single agent console, with agent presence synchronizing across all channels on work acceptance

To learn more about setup, please see the setup guide.

ElevenLabs Voices for Say is now Public Beta

Wed, 09 Sep 2026 03:00:00 -0400

ElevenLabs voices are now available in Public Beta for <Say>, powered by the Flash v2 and Flash v2.5 models for fast, natural-sounding text-to-speech. Get started by specifying an ElevenLabs voice via the REST API or in a TwiML Bin.

Webhook Configuration API is now in Public Beta

Tue, 08 Sep 2026 02:00:00 -0400

Using the Webhook Configuration API, customers can configure how Twilio authenticates and delivers outbound webhooks, per URL. The API consists of two resources: Webhook Settings and Webhook Rules.

Webhook Settings hold the authentication and connection configuration. Customers can secure endpoints with OAuth 2.0. Twilio fetches an access token from the customer's authorization server using the client credentials flow and sends it as a Bearer token in the Authorization header of every webhook or with Shared Key signatures. Customers can also configure delivery behavior like timeouts and retries.

International Call Forwarding - Compliance Blocking for Spain & France

Fri, 04 Sep 2026 00:00:00 -0400

Critical fix: Java Helper Library 13.0.0: fixes crash on unknown fields in nested API responses

Wed, 02 Sep 2026 02:00:00 -0400

The Java Helper Library now handles unknown fields gracefully in nested response objects, but if customers are on an affected version, their integration is at risk until they upgrade.

Versions 10.0.0 through 12.1.1 parse nested response types (profile, configuration, webhook, and others) with strict deserialization. When an API response comes back with a field the SDK doesn't recognize, the request fails with ApiConnectionException: Unable to deserialize response: Unrecognized field. Because Twilio APIs can add new optional fields at any time, this is a latent break. Customers’ integrations work today and can start failing without warning the moment a new field ships.

In 13.0.0, the Java Helper Library ignores unknown fields in all response objects, matching how every other Twilio Helper Library already behaves.

What to do

Upgrade to Java Helper Library 13.0.0 or later as soon as possible. Version 13 does include breaking changes so follow the upgrade guide to migrate safely. Once customers are on 13.0.0, their integration handles new optional fields in API responses without hitting deserialization errors.

The Python, Node.js, C#, Ruby, PHP, and Go Helper Libraries are not affected. They already handle unknown response fields the same way.

Verify Custom Templates are now Generally Available

Wed, 02 Sep 2026 02:00:00 -0400

Verify Custom Templates give you the flexibility and security to use custom SMS/RCS and Voice message templates beyond standard defaults or pre-approved options.

To learn more about how to create a custom template for your business needs, check out our support guide.

Update to Twilio SendGrid Link Branding: Automatic SSL Certificate Provisioning

Thu, 27 Aug 2026 03:00:00 -0400

Twilio SendGrid has added automatic SSL certificate provisioning as a toggle within the standard link branding setup flow. When enabled, SendGrid provisions and hosts the SSL certificate needed to serve tracking and branded links over HTTPS, removing the need to purchase, install, and maintain a certificate through an external CDN or DNS provider.

Twilio SendGrid recommends activating this setting for all link branding domains. Gmail is rolling out warnings on non-HTTPS links by the end of October 2026, and tracking links without SSL will see reduced click-through as a result. Enabling automatic SSL requires adding two additional DNS records provided by SendGrid, alongside the CNAME records already used for link branding.

The Link Branding API now supports a new auto_ssl parameter when creating a branded link. Setting auto_ssl to true provisions the certificate automatically, returns the additional DNS records needed to complete setup, and reports certificate status through a new auto_ssl_available field once the certificate is issued and live. auto_ssl can only be set when a link is created and can't be changed afterward.

Verify tightens fraud prevention geo permissions for Italy and Argentina

Wed, 19 Aug 2026 14:30:00 -0400

Twilio has observed a sudden rise in SMS Pumping fraud (aka SMS Artificially Inflated Traffic) targeting messages to Italy (IT) and Argentina (AR). To protect customers from this activity, Twilio Verify is tightening its fraud prevention posture for these two countries, effective August 19, 2026.

Specifically, Twilio is updating the default Verify Geo Permissions setting for Italy and Argentina from "Allow all traffic" — the default state at account creation — to "Monitor all traffic for fraud." This change applies to all existing accounts where IT and/or AR remain in the default "Allow all traffic" state.

What this means for customers

If your account still has IT and/or AR set to the default "Allow all traffic" permission, it will be updated to "Monitor all traffic for fraud" starting August 19, 2026.
If you've already changed the geo permission for IT or AR away from the default “Allow all traffic” (to any other state), your configuration will not be modified by this update.
The protection provided by "Monitor all traffic for fraud" requires that you have Fraud Guard enabled.
No action is required for customers with Fraud Guard enabled. This update happens automatically for in-scope accounts. Customers that revert the status back to “Allow all traffic” risk SMS Pumping fraud and are responsible for payment to all traffic to IT and AR.
You can review or change your geo permissions at any time from the Verify Geo Permissions page in the Twilio Console.