Twilio adds new error codes for 10DLC campaign rejections
Code that parses rejection reasons may need an update.
ProviderTwilioIn effect
Twilio rejection codes now name the exact 10DLC campaign problem
A rejected campaign tells you what to fix.
Published , updated
- What changed
- Twilio returns more specific error codes when a 10DLC campaign is rejected or needs edits. Each code names one compliance issue. The old codes still work. The new codes show in API responses, Event Streams and the Console.
- Who is affected
- Twilio customers and ISVs that register 10DLC campaigns.
- When
- Effective . Announced .
- What to do
- Update the code that maps rejection codes to messages for your customers, so each code shows the fix.
When a 10DLC campaign is rejected, the reason decides what to fix: the campaign description, the sample messages, the opt-in flow or the website. Twilio's older rejection codes were broad, so the reason was not always clear.
From 23 March 2026, Twilio returns more specific codes. Each one names one compliance problem. They appear in API responses, in Event Streams and on the campaign page in the Console. The old codes still work.
An ISV can now show its customers the exact fix instead of a general "rejected" message.
Related
Twilio sends emails when a 10DLC campaign is approved or rejected
ISVs get the emails for all their subaccounts.
Twilio rejects campaigns without privacy policy and terms URLs
API registrations without both URLs fail review.
