Twilio Release Notes

Starting May 21, 2026

T-Mobile A2P 10DLC daily message cap warning error codes 30025 (50% threshold), 30026 (70% threshold), and 30027 (100% of the daily limit) are being retired. These error codes will no longer fire in API error logs or webhooks, and the associated proactive warning emails will stop.
Error code 30023, which triggers when traffic hits 100% of the T-Mobile daily cap, is not affected by this change.

What do customers need to do?

Customers who have webhooks or monitoring configured for error codes 30025, 30026, or 30027 should plan to remove those integrations before May 21.
Customers who relied on these error codes or warning notifications to monitor daily usage can track T-Mobile message volume through Twilio Messaging Insights. Error code 30023 will continue to fire when traffic hits 100% of the T-Mobile daily cap, so customers can use that as a trigger for monitoring and alerting.

Need a hand?

These resources will help:

• Error code 30023
• T-Mobile Daily Message Limits
• Twilio Messaging Insights
• Traffic Optimization Engine

We are excited to announce that Apple Messages for Business (AMB) is now available in Private Beta on the Twilio platform. This release allows businesses to connect with their customers directly within the native Messages app on iPhone, iPad, and Apple Watch, providing a secure, branded, and highly interactive communication channel.

With Apple Messages for Business, you can go beyond plain text to deliver rich, end-to-end customer journeys with features like:

• Native Entry Points: Meet customers where they already are—integrated natively into Apple Maps, Safari, Siri, and iOS Search.
• Rich Interactive Features: Utilize List Pickers for product selection, Time Pickers for scheduling, and Rich Links for high-fidelity website previews.
• Secure Commerce: Enable seamless, one-touch payments using Apple Pay, authenticated via FaceID or TouchID.
• Branded Experience: Build trust with a verified sender logo and end-to-end encrypted messaging.

To learn more and request access to the beta, visit Twilio's Apple Messages for Business product page.

Simplify sending and build faster with a single shared API that is compatible with Android, iOS and web browsers

• Automatically expire stale tokens instead of managing expiration webhooks and token state
• Send up to 10,000 notifications with a single API request and personalize those notifications for each recipient using Liquid
• Schedule notifications for a later time
• This API also features shared primitives that make it easy to extend your use case across SMS/MMS, RCS and Email using the Bulk Messaging API and Twilio Email.
• Request access to the private beta to try it today!
• Note that this API is expected to replace Twilio Notify. If you are a Twilio Notify customer, please indicate it in your request for faster access so you can start planning your migration.

The Bulk Messaging API is now in Public Beta, enabling product and engineering teams to message at scale. Key features and benefits include:

• Send up to 10,000 messages with a single API request over SMS/MMS and RCS, eliminating the need for custom queuing, rate limiting, and retry logic
• Personalize message text, images, rich content, and tags for each recipient using Liquid
• Schedule bulk sends for a later time
• Send RCS rich content without templates, or continue using your existing Content Templates

This API also offers full JSON support, consistent versioning schemes, and shared primitives that work across Twilio Email and Push Notifications, enabling you to expand to multiple channels with fewer lines of code.

By providing multi-recipient sends, per-request controls and a durable API design, the Bulk Messaging API reduces implementation complexity and can accelerate time-to-scale for teams of all sizes. Check out our tutorial to get started now.

You can now use the Programmable Messaging API to send and receive SMS in Twilio's Ireland (IE1) region. When using the feature, messages are stored and processed in Twilio's Ireland (IE1) region up to the point they reach Twilio’s connections with telecommunications providers.

This release adds API support in IE1 for:

• Sending SMS messages with phone numbers and alphanumeric sender IDs.
• Receiving inbound SMS messages with webhooks.
• Messaging Services, including webhooks, sticky sender, and country code geomatch.

To learn more and get started, see the Public Beta API docs.

The TCPA Known Litigators Check is now available within Compliance Toolkit to help safeguard your messaging by identifying and blocking messages to phone numbers believed to be associated with individuals or entities with a history of filing TCPA-related legal actions.

This safeguard intelligently filters non-essential communications, such as marketing/promotional messages to phone numbers associated with known litigators, while allowing essential traffic, like transactional alerts, otp, and customer support messages, to reach the recipient.

When a message is blocked by this feature, Twilio will return Error Code 30640.

Learn more about this feature and how to enable it in our documentation.

Consent Management API is now available globally in Public Beta, allowing you to programmatically sync, store, update, and manage end-user consent preferences across RCS, SMS, and MMS channels. This API acts as a centralized source of truth for managing consent preferences, enabling you to seamlessly integrate consent data from external systems like CRMs or web forms directly into Twilio.

Note that consent states updated via this API for a given Messaging Service are automatically enforced across all three unified channels (RCS/SMS/MMS) to ensure compliance, without requiring any code changes.

Learn more about this feature and how to enable it in our documentation.

You can now specify the SMS or MMS sender Twilio uses when an RCS message fails to deliver using the new "FallbackFrom" parameter in your /Messages API request. The FallbackFrom sender must be in the same account SID, but does not need to be in your Messaging Service's sender pool.

This can be useful if you need fallback messages to come from a specific number, instead of relying on Twilio's automatic selection. You can also use this to send from one RCS sender representing your brand, with different fallback numbers per department, store, or representative.

For more information, please see our docs.

The Country Code Geomatch feature within Messaging Services now supports RCS in a public beta. If you have distinct RCS senders approved per country, you can add each of them to the sender pool of a single Messaging Service. When you send from that Messaging Service, Twilio will select the RCS sender that matches the country of your recipient’s phone number.

Previously, each Messaging Service supported only one RCS sender, which meant customers sending to recipients in multiple countries had to maintain separate Messaging Services and build their own routing logic. RCS Geomatch removes that requirement.

For more information, see the Messaging Services’ docs.