Product changelog and announcements

Twilio Communications APIs now support OAuth 2.0. Upgrading to OAuth 2.0 makes your applications more secure than using traditional API keys or Auth tokens. Here is why:

• Short-lived tokens: OAuth 2.0 generates short-lived access tokens instead of static, long-lasting credentials.
• Scoped access: Each token only works with the specific APIs it was issued for, so a compromised token doesn't expose everything.

Starting June 30, 2026, PrivacyPolicyUrl and TermsAndConditionsUrl will be required fields when registering a new A2P 10DLC campaign via the Twilio Messaging REST API. Campaign creation requests that don’t include both fields will be rejected during campaign review.

Branded Calling Insights for Canada, the United Kingdom, and Germany are now live in the US1 region.

V2 of Verify Message Status events is now available. This version adds a "tags" parameter to the event stream. By including key-value pairs in your Start New Verification request, you can now pass custom metadata through to your stream for better tracking. Check out the Message Status Stream guide to get started.

New customers subscribing to the Verification Event stream will no longer provide updates on the delivery_status for each send_code_attempt and its value will be set to a static status of SENT. The error_code attribute will also be removed from each attempt. To obtain updates on message delivery status, new subscribers should now use the new Message Status Event Stream.

Verify Event's Verification stream has a new version 3 that includes a new "tags" parameter in each attempt. This set of custom tags will appear in the event stream when you include a key value pair in the tags parameter of the Start New Verification request. To learn more, please visit our Verification Status Stream guide.

We’re excited to announce that Twilio’s integration with Salesforce Service Cloud Voice is GA and listed on the AppExchange.

This release comes with the following enhancements:

• External Call Transfers: Agents can now transfer calls to external phone numbers.
• Supervisor Barge & Listen: Supervisors can now monitor live calls and “barge in” to assist agents during critical customer interactions.
• Toggle Real-Time Transcription: Administrators can enable or disable real-time transcription based on specific privacy requirements or workflow preferences.

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

Voice Insights Trust & Engagement Insights and its companion Reports API are now Generally Available. This combined release provides a comprehensive solution for managing outbound calling health and campaign ROI.

Trust & Engagement Insights offers a specialized Twilio Console dashboard to detect behaviors triggering spam labeling, identify blocked calls, and optimize dialing windows with a best-time-to-call heatmap. Users can quantify campaign effectiveness through a visual engagement funnel and measure the ROI of trust investments like Branded Calls.

The Reports API serves as a zero-infrastructure companion, allowing you to programmatically retrieve these same aggregated metrics—per account or per phone number—with a single call. By outsourcing data processing to Twilio, you can accelerate decision-making and reduce operational costs by up to 90%.

Key Benefits:

• Holistic Health: Monitor Trust & Engagement scores to proactively mitigate spam labeling and blocks.

• Performance Optimization: Use heatmaps and human-answer rates to refine dialing strategies.

• Programmatic Access: Use the Reports API to build custom dashboards or integrate metrics into your own internal tools.

• ROI Attribution: Compare branded vs. unbranded call performance to justify trust product investments.

These features are available exclusively as part of Voice Insights Advanced Features.

Learn more in our Trust & Engagement Insights and the Reports API documentation.

Twilio SCIM API is now Generally Available (GA). You can now automate user provisioning and deprovisioning directly from your Identity Provider (IdP), keeping Twilio access in sync as your team grows and changes.

Connect your IdP to Twilio using the SCIM 2.0 standard by creating an OAuth application in the Twilio Admin Center. Use the access token to manage users via the SCIM API endpoints—create new Twilio users, update user details, and deactivate access automatically.

• Create a new OAuth application using the authorization code grant type with the required SCIM scopes.

• Use the access token to manage users via the SCIM API endpoints—create Twilio users, update user details, and deactivate access automatically

• Okta is supported out of the box; Azure AD and Google Workspace require custom setup.

To learn more about the SCIM API, please check our docs.

We are excited to announce that Flex instances can now be added to any existing Twilio account or subaccount. Key features include:

• Reuse existing resources: You can now add Flex to any existing (non-Flex) Twilio account. This allows you to leverage existing phone numbers and Studio flows without the need for time-consuming resource migrations.
• Subaccount support: Flex instances can now be deployed within Twilio subaccounts. This is ideal for managing distinct Flex environments for:
  • Regional or departmental deployments: Separate instances for different countries or regions or departments like sales or support.
  • SDLC environments: Clear separation between Dev, Staging and Production.
  • Tenant isolation: ISVs can provide strict data and configuration isolation for end-customers within a multi-tenant architecture.