Product changelog and announcements

You can now search for Studio flows by friendly name when selecting a flow from a menu. Search results are limited to the most recent 1,000 Studio flows within a flow menu.

The Studio Flows page now supports searching using a friendly name within the current page of flows. The default page size has been increased to 1,000 flows.

 

Security standards are always evolving, and we want to ensure your Twilio applications are using the strongest protection available.

To keep your applications secure, starting February 5, 2026, the Twilio REST API endpoints will only support the cipher suites listed below and support for any other cipher suites will end. 

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.

We've introduced two new granular roles in the Twilio Console: Account API Access Admin and Account API Access Viewer. These roles give access to manage API keys, Auth Tokens, OAuth Apps, Credentials and Connect Apps.

Unlike existing general roles, these roles can be assigned at the organization, account, or subaccount level, giving you greater flexibility and least-privilege access. View the complete list of roles here.

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.

Twilio Interconnect has added a new Interconnect Exchange location in São Paulo, Brazil.

Restricted API Keys is now Generally Available (GA). You can now enforce the principle of least privilege by assigning specific permissions to individual keys, ensuring they only access exactly what is needed.

By scoping keys to specific endpoints or resources, you minimize security risks and limit the potential impact of leaked credentials. You can create and manage Restricted API Keys in the Twilio Console or programmatically via APIs.

We’re preparing to say goodbye to classic Journeys in Q2 2027 as we focus on bringing you even more possibilities with the new Journeys experience. Starting June 25, 2026, you won’t be able to create or edit classic Journeys, but existing campaigns will keep running until end-of-life in Q2 2027.

The new Journeys is all about giving you access to more powerful tools to make reaching your audience even more effective. Here’s just a sample of what you can expect:

• React to customer moments in real time: Event-Triggered Journeys let you respond instantly to actions like cart abandonment, new signups, or onboarding milestones. You'll create timely, relevant experiences that drive results.

• Personalize with richer context: Pull in detailed data from your data warehouse, including loyalty status, purchase history, and cart contents, to make every message feel tailored to each customer's unique journey.

• Build with an intuitive, powerful builder: We've completely redesigned the interface to make mapping, analyzing, and optimizing your campaigns more straightforward and efficient.

Updates to the Email Activity API rate limits, moving to 6 requests per minute to maintain throughput and reliable performance.

Personalized Recommendations are now generally available in Twilio Messaging Insights, turning your messaging data into clear, prioritized actions to improve deliverability and engagement. Powered by your Health Score for Messaging and traffic patterns, recommendations surface the highest-impact optimization opportunities and highlight relevant Twilio products to drive better performance.