Product changelog and announcements

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. 

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.

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.

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.

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.

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

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

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

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

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.