Product changelog and announcements

Customers can now use the Consent Management API to programmatically re-opt-in users on US and Canada Toll-Free numbers.

Previously, opt-outs on US/CA Toll free numbers were strictly enforced at the network level, meaning an opt out block could only be lifted if the user texted an opt-in keyword like "START". Now, if a user provides valid re-opt-in consent outside of a messaging channel (e.g., via a web form, email, or in-app preference center), you can log their updated consent directly through the Consent Management API. Twilio will automatically pass this signal to downstream networks to clear the opt-out block and resume messaging.

Key Highlights:

• Programmatic Re-Opt-In: Seamlessly restore message deliverability for users who re-consent via external channels.

• Fewer Failed Sends: Eliminate 21610 (Unsubscribed Recipient) and 30004 (Message Blocked) error codes for users who have re-consented to receive messages.

• Centralized Compliance: Keep your Twilio messaging traffic perfectly synced with your CRM and internal omnichannel engagement and consent workflows.

For more information, see our Consent Management API docs.

On September 9, 2026, Twilio will rotate the end-user TLS certificate for all REST API endpoints. Only the end-user certificate and certificate serial number will be renewed; root and intermediate certificates will remain the same.

This is a routine update that won’t impact most customers unless they’re pinning certificates or are managing them manually. Customers using the Twilio Helper Libraries don’t need to take any action since the change will be handled automatically. 

Twilio recommends against certificate pinning because it creates potential security risks, can cause downtimes for services, and a higher probability of failed API requests.

How to test your connection

The new certificate will be available for testing at https://tls-test.twilio.com starting August 12, 2026. If the request succeeds with a 200 OK, no further action is required.

Need a hand?

These resources have more detail:

• Monitoring Updates to Twilio REST API Security Settings

• Security best practices

Dedicated IPs are now available for Twilio Email, enabling streamlined control over email deliverability directly within the Twilio console. This functionality simplifies sending reputation management at scale.

To ensure deliverability from day one, newly provisioned dedicated IPs automatically enter a 41-day warm-up schedule, complete with shared pool overflow protection to smooth out volume spikes. Organizations can also segment traffic by grouping IPs into custom pools, assigning specific IPs directly to sub-accounts, and configuring flexible fallback options to maintain continuous email flow.

To learn more about how to manage your email reputation and IP warmup, see the Twilio Docs.

On September 15, 2026, Twilio will add new error codes for Toll-Free Verification and A2P 10DLC campaign registration rejections. 

The Twilio Voice JavaScript SDK now includes noise cancellation reference components, giving you a production-ready starting point for either open-source RNNoise or commercially-licensed Krisp.

On September 15, 2026, Twilio is introducing a new regional IP address for Event Streams webhook traffic in US East (us-east-1). This is part of a move from a single shared IP range to dedicated regional addresses, bringing Event Streams in line with how the rest of the Twilio platform routes traffic.

This change only affects customers who validate incoming Event Streams webhook traffic by source IP address. If a setup doesn’t check the source IP, no action is needed.

Effective August 3, 2026, Twilio SendGrid has removed the Send to Coworker action from the Domain Authentication setup flow due to low usage. This simplification prioritizes only the most valuable paths for users to complete their domain authentication and get started with email.

Directing DNS records through automated email is no longer the optimal method for technical handoffs. DNS configurations are highly sensitive to formatting, and transferring this data via email can increase the risk of errors during the setup process. This change ensures that critical security records are managed through more intentional and reliable methods.

For users of the Send to Coworker action, Twilio SendGrid recommends reaching out directly to your IT or infrastructure teams via internal communication channels, such as Slack, Microsoft Teams, or internal ticketing systems. Sending DNS record update requests through internal communication channels ensures recipients trust the request. Utilizing these established workflows also delivers the necessary context and data in a format that aligns with an organization’s standard practices for updating DNS records.

Conversations (classic) now supports the whatsapp/card and whatsapp/flows content types, letting you send WhatsApp Card templates and WhatsApp Flow templates directly through the Conversations API. Cards let you pair a message with tappable action buttons and optional media, while Flows let you launch an interactive, multi-step WhatsApp Flow from a single templated message — both previously only available via Programmable Messaging. Build these content types with the Content Template Builder and reference them by SID when sending a message in a Conversation.

Restricted API Keys now support granular, resource-level permissions for Conversations (classic), covering actions like listing conversations, sending messages, managing participants, and configuring webhooks. This lets you scope a key to only the operations your integration needs — for example, granting read access to conversations while blocking any ability to delete users or roles — reducing the blast radius if a key is ever compromised. Configure these permissions when creating a Restricted API Key in the Twilio Console. 

We are thrilled to announce that US Branded Calling is now Generally Available for all customers. This feature helps you create a more trusted and recognizable voice experience by showing branded elements like your logo and call reason when you reach out to customers. Branded Calling is available on T-Mobile and Verizon.