ProviderTwilioIn effect

Twilio adds new error codes for 10DLC campaign rejections

Code that parses rejection reasons may need an update.

Published , updated

What changed
Twilio added new shared error codes for A2P 10DLC campaign and toll-free verification rejections. The codes name the rejection reason more exactly.
Who is affected
ISVs and platforms that register campaigns through the Twilio API.
When
Effective . Announced .
What to do
Check the code paths that read rejection error codes. Add the new codes to your handling and to your customer-facing messages.

On 15 September 2026 Twilio added new error codes for rejected 10DLC campaigns and toll-free verifications. The codes are shared between the two products and name the reason for the rejection more exactly.

This follows the more specific campaign rejection codes that Twilio started to return in March 2026. Code that maps error codes to messages for customers must know the new codes, or customers see a generic error.

Some rejections cannot be fixed by sending the campaign again. Twilio says that campaigns rejected for content violations or high risk (codes 30883 and 30885) must not be resubmitted.

Related

Catch 10DLC violations before a carrier does

Moderation API checks every message against the campaign it was registered under. Start with a free backtest on 30 days of your traffic.