Changelog

WhatsApp Card & Flows Support in Conversations (classic)

Fri, 31 Jul 2026 03:00:00 -0400

Conversations (classic) now supports the whatsapp/card and whatsapp/flows content types, letting you send WhatsApp Card templates and WhatsApp Flow templates directly through the Conversations API. Cards let you pair a message with tappable action buttons and optional media, while Flows let you launch an interactive, multi-step WhatsApp Flow from a single templated message — both previously only available via Programmable Messaging. Build these content types with the Content Template Builder and reference them by SID when sending a message in a Conversation.

Restricted API Keys, Conversations (classic) permissions

Fri, 31 Jul 2026 03:00:00 -0400

Restricted API Keys now support granular, resource-level permissions for Conversations (classic), covering actions like listing conversations, sending messages, managing participants, and configuring webhooks. This lets you scope a key to only the operations your integration needs — for example, granting read access to conversations while blocking any ability to delete users or roles — reducing the blast radius if a key is ever compromised. Configure these permissions when creating a Restricted API Key in the Twilio Console.

US Enhanced Branded Calling is now Generally Available

Thu, 30 Jul 2026 14:30:00 -0400

We are thrilled to announce that US Enhanced Branded Calling is now Generally Available for all customers. This feature helps you create a more trusted and recognizable voice experience by showing branded elements like your logo and call reason when you reach out to customers. Enhanced Branded Calling is available on T-Mobile and Verizon.

Functions and Assets API date_created and date_updated timestamps will be corrected on September 1, 2026

Thu, 30 Jul 2026 02:00:00 -0400

On September 1, 2026, date_created and date_updated on Functions and Assets resources will be updated to return accurate UTC timestamps.

Currently, these fields return values shifted forward by the Pacific Standard Time time zone offset (+7 hours) despite the Z suffix indicating UTC. This is a presentation-layer bug introduced in 2023; the underlying data is correct.

The correction applies retroactively. Any request made on or after September 1 will return corrected UTC values, including for resources created before that date.

What do you need to do?

Customers whose integrations depend on date_created or date_updated for sorting, filtering, display, time-range comparisons, or audit logic should review their implementation before September 1 to confirm it handles the corrected values.

This resource will help:

Functions and Asset API documentation

Real-time WhatsApp Template Approval and Category Updates via Event Streams

Mon, 27 Jul 2026 03:00:00 -0400

Twilio Event Streams now supports real-time notifications for WhatsApp message template status and category updates.

Previously, tracking changes to WhatsApp content template approvals or re-classifications required periodic polling via the Content API or Senders API. With this release, you can subscribe to template lifecycle events through Event Streams and automatically trigger downstream workflows whenever Meta approves, rejects, or updates the category of a template.

What’s New

You can now subscribe to the event type com.twilio.messaging.template.approval.updated in your Event Streams sink configurations (Webhooks, Amazon Kinesis, Segment, etc.).

This event fires for two main template update types:

status_update: Triggers when a template’s approval status changes (e.g., moving from pending to approved or rejected).
category_update: Triggers when Meta updates or re-categorizes a template (e.g., changing between UTILITY, MARKETING, or AUTHENTICATION).

Event Payload Overview

When a status or category update occurs, Event Streams delivers a payload containing both the current state and the previous state of the template.

Getting Started

Go to the Event Streams section in the Twilio Console.
Create or edit an active Subscription.
Add the com.twilio.messaging.template.approval.updated event type under the Messaging category.
For detailed field specifications and integration guides, review the Twilio Event Streams for WhatsApp documentation and the Template Approval Event Schema.

Error code 30915 now flags invalid Sole Proprietor classification for both A2P 10DLC and Toll-Free Verification

Fri, 17 Jul 2026 00:00:00 -0400

Error code 30915 now applies consistently to A2P 10DLC campaign registration and Toll-Free Verification. When a Sole Proprietor registration is submitted with a business but the available information shows it is actually a registered legal entity (for example, an LLC or corporation) error code 30915 will be returned.

What changed

30915 is now non-program specific; the same code and guidance apply whether you register via A2P 10DLC or submit for Toll-Free Verification.
In addition to a corporate identifier in the business or brand name (LLC, Inc., Corp.), 30915 can now be triggered when your website or public records indicate a registered corporation, or when tax documents or business registration documents reflect a legal structure that does not match a sole proprietorship.

What you should do if you receive 30915

Update the submission to the correct business type. If your business is an LLC, corporation, partnership, or any other entity with an EIN or Canadian Business Number, register it as a Standard or Low-Volume Standard Brand (A2P 10DLC), or select the correct business type for Toll-Free Verification, not the Sole Proprietor flow.
Provide valid business registration documentation that matches your legal business entity.
Keep your details consistent. Make sure your business name, website, and supporting documentation align across the submission.

Learn more:

Lookup Line Status Public Beta is now available!

Tue, 14 Jul 2026 01:00:00 -0400

As of July 14, 2026 the Lookup Line Status Public Beta is now available!

Lookup’s Line Status package allows you to get the status information of a mobile phone number. Line Status provides statuses that lets you know if the mobile number is active, inactive, unreachable, reachable or unknown. Validate phone numbers in your contact database to improve the efficiency of your campaigns.

Additional Documentation on this feature can be found here

RCS error code for unconfirmed delivery is changing from 30036 to 30046

Thu, 09 Jul 2026 03:00:00 -0400

Starting August 10, 2026, the error code returned when an RCS message cannot be delivered to an unreachable end-user device will change from 30036 to 30046.

Error code 30046 (Message delivery not confirmed) gives developers a more accurate signal when an RCS message cannot reach an end-user device. Previously, 30036 (Validity Period Expired) was returned for these failures, pointing to queue and throughput settings as likely causes and making it easy to investigate in the wrong direction.

With 30046, the failure is correctly attributed to device-side conditions like the recipient's device being switched off, out of coverage, having no internet connection, or being unable to accept the message. This code will also serve as the standard for device-unreachable conditions across RCS and future OTT channels.

Conference list endpoint rollout extended

Wed, 08 Jul 2026 02:00:00 -0400

Based on customer feedback, we are pushing out the change to the Conference list endpoint split to only return in-progress conferences until September 30, 2026.

Node.js v24 is now available for Twilio Functions

Wed, 08 Jul 2026 00:00:00 -0400

Twilio Functions now supports Node.js v24 as a build runtime. You can target it by selecting Node.js v24 from the runtime dropdown in the Console Dependencies tab, or by specifying runtime: node24 in your Serverless Toolkit configuration.

Node.js v24 requires @twilio/runtime-handler version 2.1.2 or later. If your service specifies a version between 1.2.0 and 2.1.2, Twilio will automatically upgrade it to 2.1.2 when you deploy to node24 — no action required. If your service specifies a version below 1.2.0, your build will fail with an error asking you to upgrade manually before deploying to node24.

Functions currently deployed on earlier runtimes are unaffected. Node.js v22 remains the current default.

To upgrade your runtime or learn more about supported versions, see the Node.js version upgrade guide and the Migrating Functions from callback to async/await documentation.

WhatsApp Usernames is now supported on the Twilio Platform & Messaging APIs for WhatsApp

Tue, 07 Jul 2026 02:00:00 -0400

WhatsApp Usernames is now supported on the Twilio Platform and Messaging APIs for WhatsApp. WhatsApp now allows users to adopt usernames. A username can optionally mask a user's personal phone number and allows them to interact with businesses through Business Scoped User IDs (BSUID). Twilio exposes this identifier in message webhooks and in Event Streams event data. Meta is releasing this functionality in multiple waves, starting on July 7, with additional countries to follow at later dates. Please check our documentation for the latest rollout schedule.

Branded Calling for Non-US Regions is Now in Public Beta

Tue, 07 Jul 2026 00:00:00 -0400

We are thrilled to announce that Branded Calling has officially entered Public Beta for our customers in Canada, Germany, and the United Kingdom.

Email Notifications for A2P 10DLC Campaign Registrations

Tue, 07 Jul 2026 00:00:00 -0400

Email notifications for A2P 10DLC campaign registrations to give you greater visibility into your onboarding pipeline are now live.
Automated email updates at four critical stages of the campaign lifecycle:

Initial Registration: Confirmation that your campaign submission has been received and is entering review.
Approval: Notification that your campaign is live and ready to route traffic.
Rejection: Immediate alert if a campaign fails carrier or ecosystem validation, allowing you to address issues quickly.
Resubmission: Confirmation when a corrected campaign has been successfully submitted for re-review.

Where are these emails sent?

Standard Direct Customers: Notifications are sent directly to the address provided in your Brand registration or the specific A2P bundle email field (which can be viewed and updated anytime within the Console).
ISV Customers & Subaccounts: To protect the end-customer experience, if a campaign belongs to a subaccount under an ISV, the notification will automatically route to the Parent ISV account’s Primary Customer Profile (PCP) email instead of the subaccount.

OAuth 2.0 client credentials for Organization API access is now GA

Fri, 03 Jul 2026 14:30:00 -0400

Organization APIs can now be accessed using OAuth 2.0 client credentials (grant type per RFC 6749, section 4.4). Alongside GA, we're also launching the Role Assignments and Roles public APIs.

This release enables:

Microsoft Entra ID SCIM integration: Follow our integration guide to set it up.
Programmatic user management: Manage users via standard SCIM APIs.
Programmatic role management: Assign any role type to users via the new Role Assignments and Roles APIs.

Upcoming changes to Twilio Interconnect SIP Signaling IP Addresses

Thu, 02 Jul 2026 00:00:00 -0400

In the second half of 2027, Twilio will update the SIP signaling IP addresses used for Programmable Voice SIP and Elastic SIP Trunking over Interconnect in all regions. The Interconnect signaling IPs, for both inbound and outbound SIP signaling over private connections, will move to the 159.26.160.0/20 range as part of infrastructure improvements for greater flexibility, reliability, and scalability.

Customers using these products over Interconnect will need to update their network firewalls to allowlist the new IP addresses before the cutover date. Depending on the specific Twilio solution in use, IP address configurations within that solution may also need to be updated.

SIP FQDNs/hostnames, TLS certificates, public internet SIP signaling IPs, and Media IP address ranges aren’t affected by this migration.

Voice Insights Call Summary: Removal of conference_participant field

Wed, 01 Jul 2026 03:00:00 -0400

The conference_participant field in the Voice Insights Call Summary is being removed from the REST API and Event Streams August 1, 2026. This field pre-dated Conference Insights and had limited accuracy due to the complexity of conference call flows. It is currently only populated for calls eligible to participate in a Twilio conference; all others return attributes: null. After removal, all calls will uniformly return attributes: null. Use the Conference Insights API or Conference Insights Event Streams for conference data going forward.

Updates to optimize RCS delivery and fallback

Wed, 01 Jul 2026 03:00:00 -0400

Twilio recently made improvements to our platform to increase RCS delivery and improve fallback consistency.

The time for a recipient’s device to confirm delivery before an RCS message’s status is updated to "undelivered" or a fallback SMS / MMS is sent, no longer depends on how long a message is queued within Twilio. Consequently, when messages queue within Twilio (as expected when sending large marketing campaigns) Twilio’s native fallback-to-SMS feature now ensures messages to RCS-capable devices are always attempted to be delivered on RCS, and no longer will fall back prematurely.

In addition, to optimize our platform by balancing successful RCS delivery with timely message resolution (whether that results in a native SMS / MMS fallback or a timely "undelivered" status), the amount of time given to devices to confirm delivery has been updated. As a result, you may notice messages falling back to SMS / MMS or an RCS message’s status updating to undelivered faster or slower than before.

No code changes are needed to take advantage of these optimizations. However, you may guide this behavior by ensuring you are using the "ValidityPeriod" parameter. Though the "ValidityPeriod" parameter continues to only apply to messages queued within Twilio’s platform, it is used to inform Twilio of how time-sensitive the message is and when a faster fallback or failure signal is needed. For time-sensitive messages, like OTPs or appointment reminders, it’s recommended to use a shorter value than the 10-hour default, like 30 seconds or 15 minutes. For customers sending RCS without Twilio's native fallback feature, these optimizations also ensure the message’s status moves to "undelivered" when it is no longer likely to be delivered, rather than waiting hours (or days) for it to inevitably expire.

Consent Management API is now Generally Available and HIPAA Eligible

Tue, 30 Jun 2026 14:30:00 -0400

Consent Management API is now Generally Available allowing you to programmatically sync, store, update, and manage user consent preferences globally across RCS, SMS, and MMS channels.

As of June 30, 2026, Consent Management APIs can now support healthcare use cases that may 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 Services. Learn more about how to build on Twilio for HIPAA compliance.

Learn more about this feature and how to enable it in our documentation.

Compliance Toolkit for Messaging is now HIPAA Eligible

Tue, 30 Jun 2026 14:30:00 -0400

As of June 30, 2026, Compliance Toolkit can now support healthcare use cases that may 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 Services. Learn more about how to build on Twilio for HIPAA compliance.

Learn more about this feature and how to enable it in our documentation.

Twilio Voice React Native SDK Conversation Relay Reference Component

Tue, 30 Jun 2026 00:00:00 -0400

Twilio Conversation Relay handles the real-time complexity of voice AI interactions - transcription, turn-taking, interruption handling, speech generation - so that your app logic stays focused on the conversation itself. We've published a reference component for the Twilio Voice React Native SDK to show how that works end-to-end on mobile.

Compliance Embeddable for US A2P 10DLC is now available in Private Beta

Mon, 29 Jun 2026 02:00:00 -0400

Twilio is launching the Private Beta for Compliance Embeddable for US A2P 10DLC.

The Compliance Embeddable is a white-label, self-service solution that integrates seamlessly into an Independent Software Vendor’s (ISV) application portal. With the Compliance Embeddable, end customers can independently complete both brand and campaign registrations while Twilio handles the underlying regulatory infrastructure behind the scenes.

Featuring fully customizable styling and data pre-filling, the Compliance Embeddable simplifies end-user registration, reduces internal development overhead, and streamlines onboarding workflows.

Enhanced Role-Based Access Control (RBAC) is a GA product in the new Twilio Console

Thu, 25 Jun 2026 14:30:00 -0400

With Enhanced RBAC we have introduced more granular roles called built-in roles, which provide access to specific Twilio products including Messaging, Studio, Phone Numbers etc. You can find the complete list of new roles here.

These roles can be assigned at the organization, account or subaccount level, unlike the general roles which can only be assigned at the account level.

Elastic SIP Trunking - Immutable Call Forwarding with CallToken (Public Beta)

Tue, 23 Jun 2026 00:00:00 -0400

Twilio is announcing its public beta availability of Call Forwarding with Caller ID preservation. Twilio Elastic SIP Trunking customers who would like to preserve & retain the caller ID from the incoming trunking origination call in their outgoing trunking termination (forwarded) call for context about their customers can now use this feature. Twilio Programmable Voice already has support for this functionality via CallTokens.

Sending Typing Indicators on RCS, WA, and AMB in V3 Typing Indicator API

Sun, 14 Jun 2026 18:00:00 -0400

New Unified Typing Indicator API experience:

You can now send typing indicators across RCS, WhatsApp (WA), and Apple Messages for Business (AMB) using a streamlined consistent integration with JSON payloads.

Smart Channel Behaviors:

RCS: Displays a typing indicator for up to 20 seconds (or until the message delivers) to reduce perceived wait times.
WhatsApp: Automatically marks the referenced message as read and displays the indicator for up to 25 seconds (or until delivery) using the required messageId.
Apple Messages for Business (Private Beta): Support for Typing indicators is available! Please note that AMB access is currently restricted as it is in private beta. How to use typing indicators on AMB is available in our beta documentation.

💡 Need more time? For longer workflows, you can send additional typing indicator requests to extend the duration before the default timeouts hit.

See our public documentation here:

Studio and TaskRouter are now available in Private Beta in IE1

Thu, 11 Jun 2026 00:00:00 -0400

Studio and TaskRouter are now available in Private Beta in Twilio's Ireland (IE1) region. With this release, your application's Studio and TaskRouter data is processed and stored in IE1, providing EU data residency and control over where your contact center routing and workflow automation data lives.

You can learn more on Studio and TaskRouter as well as other Regional products on our Regional product and feature availability page. To request Private Beta access, contact your account team.

Conference list endpoint will default to in-progress conferences only on July 13, 2026

Wed, 10 Jun 2026 02:00:00 -0400

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

If you're querying for in-progress conferences (the most common use case), no action is needed.

Currently, calling this endpoint without a Status filter returns all conferences regardless of status (init, in-progress, and completed). This change is part of an infrastructure upgrade that separates in-progress and completed conference data into distinct systems, improving reliability and performance for real-time conference operations.

Data Residency for SMS (EU) is now Generally Available (GA)

Tue, 09 Jun 2026 19:00:00 -0400

The Programmable Messaging API is now generally available for SMS in Twilio’s Ireland (IE1) region. When using this feature, SMS message personal data is stored and processed in the EU up to the point it reaches Twilio’s connections with telecommunications providers.

With this release, the Ireland (IE1) region supports the following messaging features:

Programmable Messaging API: Send outbound SMS messages using phone numbers and alphanumeric sender IDs.
Inbound SMS: Receive inbound SMS messages via webhooks configured at the phone number or messaging service level.
Messaging Services: Manage IE1 sender pools from the Twilio console or via the API. Take advantage of Sticky Sender, Country Code Geomatch, Advanced Opt-Out, and service webhooks in IE1.
Messaging Logs and Insights: Analyze and troubleshoot IE1 SMS traffic in the Twilio Console.
Phone Numbers: Configure phone numbers for use in IE1 using the Twilio Console or the API.

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

Upcoming cipher suite list update for all Twilio REST API endpoints on November 18, 2026

Tue, 26 May 2026 00:00:00 -0400

Security standards are always evolving, and we want to ensure your Twilio applications are using the strongest protection available.

We're extending the deadline for these changes and customers now have until November 18, 2026, to update their setups with the ciphers listed below. We’ll continue accepting legacy cipher traffic during that window so customer applications keep running without interruption.

T-Mobile A2P 10DLC Daily Limit Warning Error Codes 30025, 30026, and 30027 Being Decommissioned

Tue, 12 May 2026 02:00:00 -0400

Starting May 21, 2026, T-Mobile A2P 10DLC daily message cap warning error codes 30025 (50% threshold), 30026 (70% threshold), and 30027 (100% of the daily limit) are being retired. These error codes will no longer fire in API error logs or webhooks, and the associated proactive warning emails will stop.

Error code 30023, which triggers when traffic hits 100% of the T-Mobile daily cap, is not affected by this change.

What do customers need to do?

Customers who have webhooks or monitoring configured for error codes 30025, 30026, or 30027 should plan to remove those integrations before May 21.

Customers who relied on these error codes or warning notifications to monitor daily usage can track T-Mobile message volume through Twilio Messaging Insights. Error code 30023 will continue to fire when traffic hits 100% of the T-Mobile daily cap, so customers can use that as a trigger for monitoring and alerting.

Need a hand?

These resources will help:

Apple Messages for Business Private Beta with Twilio

Thu, 07 May 2026 03:00:00 -0400

We are excited to announce that Apple Messages for Business (AMB) is now available in Private Beta on the Twilio platform. This release allows businesses to connect with their customers directly within the native Messages app on iPhone, iPad, and Apple Watch, providing a secure, branded, and highly interactive communication channel.

With Apple Messages for Business, you can go beyond plain text to deliver rich, end-to-end customer journeys with features like:

Native Entry Points: Meet customers where they already are—integrated natively into Apple Maps, Safari, Siri, and iOS Search.
Rich Interactive Features: Utilize List Pickers for product selection, Time Pickers for scheduling, and Rich Links for high-fidelity website previews.
Secure Commerce: Enable seamless, one-touch payments using Apple Pay, authenticated via FaceID or TouchID.
Branded Experience: Build trust with a verified sender logo and end-to-end encrypted messaging.

To learn more and request access to the beta, visit Twilio's Apple Messages for Business product page.