Product changelog and announcements

Security and reliability go hand in hand, and we want to make sure your applications keep running smoothly while we work in the background to keep things safe.

That’s why on April 8, 2026, the end-user certificate for all Twilio REST API endpoints will be rotated.

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 June 3, 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. 

Verify Events now supports message status events in real time, providing information on the message status of verifications. Available message status events include DELIVERED, UNDELIVERED, SENT, READ and FAILED statuses.

Twilio Programmable Messaging now supports RCS messaging to Canadian phone numbers.

You can now request RCS Sender approval on available Canadian carriers.

To start sending branded RCS messages using Twilio Programmable Messaging, go to the Twilio Console to create, test and submit an RCS Sender.

Note that while all brands can submit RCS Senders for carrier approval, Twilio cannot provide an SLA or guarantee Sender approval by carriers.

For more information, see our RCS documentation.

We’re introducing a refreshed, easier-to-use Studio canvas in public beta. This update offers a snappier building experience and an updated design with zero impact on your existing flow logic.

What’s new

• High-performance interactions: The new canvas is built for speed, delivering smooth panning, zooming, and dragging especially for workflows with hundreds of widgets.

• Modernized look and feel: We've overhauled the visual interface to align with modern Twilio UX standards, featuring updated node styling, improved spacing, and cleaner typography.

• Safe, side-by-side testing: Explore the new UI with total confidence. This update maintains full feature parity with the classic canvas, ensuring your widgets and flow logic work exactly as they did before.

How to opt in

Ready to try it out? You’ll find a banner at the top of your Studio page with an option to Try Studio’s new canvas. Turning on this option enables the new canvas experience just for you, without affecting the view for the rest of your team. If you need to switch back at any time, turn off the new canvas option at the top of the page to return to the classic canvas.

Feedback

We want to hear from you! Please help us shape the future of Studio by sharing your thoughts about the updated Studio canvas.

RCS Business Messaging now has a redesigned end-to-end compliance registration flow. The new console experience collects all Google and U.S. carrier requirements in one guided session, shows country-level pricing, gives customers visibility into the status of their submission, and accelerates approvals through automated carrier and verification integrations.

Starting June 11, 2026, Node.js v20 support in Twilio Functions will end. Any new Functions that you create or deploy after that date will default to Node.js v22. Existing Functions will keep running on Node.js v20, and will only move to v22 when you choose to redeploy them. 

Starting May 1, 2026, Twilio’s public Certificate Authority will no longer include the Client Authentication Extended Key Usage (EKU) extension in the security certificates they issue.

We’re pleased to announce that Flex UI 2.16.0 is now available. This release includes a number of bug fixes.

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

To support compliance and improve campaign approval rates, Twilio is introducing new fields during U.S. A2P 10DLC Campaign registration.

What’s Changing?

When registering a Campaign, you must now provide:

• Privacy Policy URL – A valid, publicly accessible link to your privacy policy
• Terms & Conditions URL – A valid, publicly accessible link to your service terms.

These are now dedicated fields in the registration flow.

Console Updates

In the Twilio Console, you’ll see new fields in the Campaign registration form where you can enter your Privacy Policy and Terms & Conditions URLs directly.

API Updates
For programmatic registrations, these fields are now supported:

• Setup: Values can be passed during the Campaign create request. Providing the specific request header during the Campaign create call will return these fields in the API response.
• Recommendation: While the API currently allows flexibility, we highly recommend including these links in all new registration requests to avoid potential vetting failures.

Why This Matters
Previously, this information was required and  requested within the Message Flow description.
Providing dedicated, direct links ensures your Campaigns get approved faster and reduce the risk of rejection.

To learn more about U.S. A2P 10DLC registration, please review our documentation and Support article on Campaign approval requirements.