Twilio Changelog

For years, Twilio Voice JS SDK 1.x has helped customers power countless voice calling experiences. But as with any long-standing tool, there comes a time to pass the torch.

Twilio will officially sunset Voice JavaScript SDK version 1.x on September 10, 2025. To continue building [and delivering] seamless voice experiences, customers should migrate to version 2.x before this date. 

Why upgrade?

Voice JS SDK 2.x was built based on customer feedback and real-world cases in mind. Since its release it’s brought meaningful improvements, such as:

• Support for modern JavaScript Frameworks

• Ability to send messages to and receive messages from your backend (User Defined Messages)

• Improved connection handling with automatic recovery without dropping the call

As SDK 1.x begins to wind down, customers may start to experience service degradation or intermittent disruptions. After September 10, 2025, version 1.x will no longer be maintained or supported. 

Migrating early is the best way to ensure uninterrupted service. The Voice JS SDK migration guide makes it easy to get started, and SDK 2.x is the best way to ensure your voice experience stays reliable and up to date.

We’re grateful to the customers who have relied on SDK 1.x and we’re excited for what’s possible with version 2.x and beyond.

Meta Pricing Changes for WhatsApp Messages: Effective July 1, 2025

Starting July 1, 2025, Meta will shift from 24-hour conversation-based pricing to a new model that charges per template message delivered. Pricing will vary by template type (Marketing, Authentication, or Utility) and may also be subject to volume-based tiers in some regions. 

This update applies to all WhatsApp messages, including those sent through Twilio Verify.

Twilio will continue to pass through Meta’s updated charges without adding any additional fees. No action is required, but customers may notice billing changes starting July 1, 2025, based on message type and volume. 

We haven’t listed the Meta fees directly in this email because they vary by region and message type. For more information, check out Twilio’s Notice: Changes to WhatsApp’s Pricing (July 2025) Help Center article or Meta’s Pricing updates on the WhatsApp Business Platform docs page.

We can’t wait to see what you build!

–Team Twilio

At Twilio, we’re always working to make your messaging experience more reliable and transparent. That’s why we’re making some updates to how we handle Alphanumeric Sender IDs.

What’s Happening?

Starting on August 13, 2025, we’re introducing clearer error codes and new message status updates when an Alphanumeric Sender ID isn’t properly registered or authorized in a given country. These updates will help you quickly understand if something needs to be fixed and keep your messages flowing smoothly.

Here are the highlights:

• *New Error Codes

  • 30041: Sent when the Alphanumeric Sender ID isn’t registered or authorized for use.

  • 30042: Sent when the Alphanumeric Sender ID is explicitly blocked because it’s generic or not allowed to be used.

•  What Will Change in Your Logs?

  • Messages with unregistered Alpha Sender IDs will now appear as “Likely-SCAM” in the logs in Singapore and Ireland.

  • Error codes will be clearer and more actionable.

If your Alphanumeric Sender IDs are already registered and approved for your destinations, you’re all set—no action needed! If you see one of these new error codes, that’s your cue to double-check that your Alphanumeric Sender ID is properly set up for the country you’re sending to.

*Note: Error codes are subject to processing fees. For more information on charges on messaging errors, visit our Twilio Help Center article on error code fees.

For questions or help with registering your Alphanumeric Sender IDs visit:

• SMS Guidelines Page

• Twilio Help Center

We’ve extended the end-of-life (EOL) date for the legacy version of Flex Single Sign-On (SSO) from June 2025 to January 15, 2026. This extension comes directly in response to customer feedback and the momentum we’re seeing with migrations. Our goal is to give every team the time they need for a smooth, stress-free transition.

Here’s what customers need to do next: 

• Customers using legacy Flex SSO now have until January 15, 2026, to complete migration to the enhanced SSO.

• After this date, logins via the legacy flow will no longer be supported

Need a hand?

Here are some helpful resources to help customers migrate: 

• Enhanced and Legacy SSO Twilio documentation

• Flex SSO URL Migration Guide

We’re excited to announce that Flex UI 2.13.0 is now available. This release includes:

• The option to turn on a default Flex ringtone for incoming tasks and the ability to configure different sounds based on task channel using the new SoundManager API.

• Spell-check functionality in the email editor.

Throughout Flex UI, you'll find feature and UI enhancements, bug fixes, and more.

For complete details, see the Flex UI release notes for 2.13.0.

Ahoy!

​​On May 8, 2025, Twilio sent an advisory to some customers outlining an upcoming change to the Twilio Verify V1/Authy API endpoints. This change, initially planned for June 16, 2025, would stop accepting GET requests that include a request body. The goal is to enhance security and better protect against smuggling attacks.

To ensure a smooth transition and give customers more time to update their integrations, Twilio is extending the deadline for this change to January 15, 2026.

What customers need to do:

• Update any GET requests that include a request body to either remove the body or use the correct HTTP method (such as POST).

• If third-party integrations are involved, confirm with those providers to ensure they are aware of and preparing for this change.

Thank you for building with Twilio! 

–Team Twilio

Twilio has officially ended support for TLS 1.0 and TLS 1.1 protocols on Elastic SIP Trunking and Programmable Voice SIP interfaces.

Starting November 10, 2025, Twilio will no longer support Node.js v18 in Functions and Assets. This change aligns with the official Node.js community deprecation timeline.

What does this mean?

• Existing Functions and Assets using Node.js v18 will continue to run as long as they are not modified.

• Any new deployments or edits to Functions after November 10, 2025, must use Node.js v22.

• Deployments using Node.js v18 after this date will fail.

• New builds by Classic users will automatically default to Node.js v22. 

What action is required?

To ensure continued functionality, we recommend that you:

1. Test and re-deploy your Functions using Node.js v22 before November 10, 2025.

2. Verify that your dependencies are compatible with Node.js v22.

3. Explicitly set the Node.js runtime to v22 via one of the following methods:

   • In Twilio Console: Select v22 in the Dependencies tab list

   • Via Serverless Toolkit: Set the runtime parameter

   • During build creation: Use the runtime configuration setting

Need a hand?

Refer to our Node.js v22 migration guide for step-by-step instructions and tips to help ensure a smooth transition.