Product changelog and announcements

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.

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

1. Go to the Event Streams section in the Twilio Console.

2. Create or edit an active Subscription.

3. Add the com.twilio.messaging.template.approval.updated event type under the Messaging category.

4. For detailed field specifications and integration guides, review the Twilio Event Streams for WhatsApp documentation and the Template Approval Event Schema.

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.

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:

• RCS
• WA

Starting in June 2026, WhatsApp will start rolling out usernames, an optional feature that allows users to hide their phone numbers when messaging or calling businesses. When a user adopts a username, their phone number may no longer appear in webhook payloads. Instead, a Business Scoped User ID (BSUID) will be provided in the to and from field, as well as the new ExternalUserId field.

Template editing is live for all Content API users today. You can now update existing templates (text, variables, rich content) directly via the API without needing to recreate or version manually. Editing a template does not change its Content Sid.

Why it matters

• Faster copy tweaks and fixes
• Consistent messaging template changes across channels
• Retain the same Content Sid when sending templates

How it works
Use PUT /v1/Content/{ContentSid} to update any existing template.

To learn more about editing your Content Templates, see our docs page here.

With zero code changes, start sending WhatsApp Marketing Message API messages to increase marketing deliverability. Meta has seen up to 9% greater marketing template deliverability with this new API, and Twilio is making it available to all customers with zero code changes required. Simply sign the terms-of-service (TOS) and your traffic will immediately start using the Marketing Message API.

All you need to do is sign Meta's Marketing Messages API terms of service. To navigate to the Meta terms of service, start in the Twilio Console under WhatsApp Senders. Click on the WhatsApp Business Account ID hyperlink. Go to the Alerts section where you can find the Marketing Messages API notifications. From there, accept the terms of service.

To accept the terms of service, you must be an admin of the Business Account. If you cannot see the terms of service in Alerts, please ask an account admin to accept the TOS.

To learn more, see our documentation on marketing templates here. 

The Senders API - WhatsApp, is now generally available, providing customers with an automated and scalable way to register, verify, and manage WhatsApp senders (phone numbers) directly through Twilio’s API.

This release allows both Direct Customers and Independent Software Vendors (ISVs) under the Tech Provider Program to automate sender onboarding. With the Senders API, customers can programmatically create, update, verify, fetch, and delete WhatsApp senders — enabling faster setup, improved accuracy, and reduced operational overhead.

The Senders API is especially beneficial for ISVs managing large portfolios of client accounts, helping streamline registration and configuration across subaccounts while maintaining compliance and consistency.

By eliminating manual workflows, customers can scale WhatsApp adoption more efficiently and accelerate time to market. To learn more about the Senders API - WhatsApp and how to integrate it, see our documentation here.

WhatsApp typing indicators are now supported on Twilio. Create typing indicators to signal to WhatsApp users that a response is being prepared. This improves user experience by reducing perceived wait times. Use typing indicators for responses that might take longer than a few seconds to generate.

To learn more about typing indicators on WhatsApp and how to send them, see our docs here.

Twilio customers can now directly define flows through WhatsApp and send them with Twilio. This enables customers to use the full capabilities offered by WhatsApp. It now also supports flows powered with endpoints. Endpoints let you pass data directly between your services and Meta to provide a personalized and dynamic experience to your customers.

Twilio now supports sending messages containing flows in session without template approval in addition to as an approved template with WhatsApp/flows. 

To learn more about how to send WhatsApp/flows see our docs here.