Product changelog and announcements

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.

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

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.

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.

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.

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.

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 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.

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.

Sign up for the Private Beta to get started.

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.