Twilio error 30007 means a carrier accepted your message and then blocked it before it reached the handset. Twilio labels it "Carrier violation" or "Message filtered", and the cause is almost always content, sender reputation or registration, not a bug in your code.
If you just saw it in a delivery status callback, don't resend the same text. The same body from the same number will usually be filtered again, and you'll pay for another attempt. Work through the checklist below first.
What error 30007 actually tells you
Carriers run spam filters on application-to-person traffic. When one of those filters blocks a message, the messaging provider receives a failure from the carrier and passes it back as 30007. You get a status of undelivered or failed, and the code appears on the message record.
The part that frustrates people is how little the code says. Carriers don't publish their filter rules, and they don't tell you which rule fired. Twilio's docs describe 30007 as a carrier violation, and the usual fix is to figure out which of a few known triggers applies to you.
Two things are worth knowing up front:
- A filtered message is a carrier decision, so the provider can't override it.
- Filtering is per message and per sender. One text can be filtered while the next, with different wording, goes through.
The usual causes
Here are the causes we see named most often in carrier and provider documentation, roughly in the order worth checking.
| Cause | What it looks like | First thing to check |
|---|---|---|
| Unregistered or mismatched traffic | Many 30007s from one number after a volume jump | Is the number on an approved campaign? |
| Spammy content | Only certain templates fail | Look at wording, caps, urgency, "free" and "winner" style phrases |
| Public URL shorteners | Texts with a short link fail, plain ones pass | Swap to your own branded domain |
| Bad sender reputation | Everything from one number slowly degrades | Complaints, opt-out rate, send bursts |
| Use case mismatch | Marketing sent on a campaign registered for notifications | Compare the sample messages you registered with what you send |
| Prohibited content | Lending, gambling, cannabis, adult | Carrier content rules for that category |
Our post on carrier filtering and public URL shorteners covers the link case in detail, and use case mismatch throttling covers the registration side.
A checklist to fix it
Go in this order. Each step is cheap, and the earlier ones catch the most common problems.
- Confirm the sender is registered. For US traffic from a 10-digit local number, the number has to sit on an approved A2P 10DLC campaign. If it isn't, fix that before anything else. See what 30034 means for the unregistered case.
- Read the exact body that failed. Pull a few filtered messages and a few delivered ones and compare. Look for shortened links, all caps, repeated punctuation, and phrases that read like a giveaway.
- Replace public shorteners. Links on shared shortener domains are a well-known trigger. Use a domain you control.
- Check the first-message pattern. A first text with a link and a hard call to action is more likely to be filtered than a plain one that names the sender and says why they're hearing from you.
- Match the content to the registered use case. If the campaign says appointment reminders, don't send promotions on it.
- Look at send patterns. A sudden burst from a number that's been quiet reads like spam. Ramp volume up over days, not minutes.
- Check opt-out and complaint signals. A rising STOP rate hurts reputation. Make sure opt-outs are honored on every send.
- Test a plain version. Send a clean, short, link-free copy of the message to a handful of your own test handsets on different carriers. If it passes, add elements back one at a time.
What not to do
Don't loop retries on a 30007. It won't change the outcome, and it makes your sender pattern look worse. Don't rotate through new numbers to dodge the filter either. Carriers watch for exactly that behavior, and it can turn a content problem into a reputation problem on every number you own.
If your platform texts on behalf of many customers, build the failure into your product. Show the end user that the message was filtered and why it likely happened, and don't show a vague "failed". Our post on delivery failure triage for support teams shows one way to sort these.
How this shows up on Ready
On Ready, each customer sub-account has its own numbers and its own carrier registration, so a filtering problem stays with the sender that caused it. Registration status is readable through GET /v1/registration, which is the first call to make when you see filtering on a number: it tells you whether the account is registered at all, and what state its submission is in.
Ready also refuses some sends before they reach a carrier. Opt-outs and numbers on your Ban list are refused up front and not charged, so they never turn into carrier failures of any kind. Content is a different matter. Ready can't see inside a carrier's filter, so wording and link problems still need the checklist above. The AI message writer has a spam check that can flag risky wording before you send, which is a second pair of eyes and not a guarantee.
When you resend a corrected message, use an idempotency key so a retry never sends twice:
POST /v1/messages
X-API-Key: <key>
Idempotency-Key: 7f3c9a52-1d4e-4b8a-9c0e-2a6d5b1e8f40
{"to": "+12125550199", "body": "Hi, this is Example Dental. Your cleaning is confirmed for Tuesday at 3 PM. Reply STOP to opt out.", "consent_attested": true} Error responses and codes are documented at https://docs.tryready.com/api/errors, and the registration endpoints are at https://docs.tryready.com/api/registration.
Where to read more
This post is about one code. If you want the whole range of Twilio-style codes and how to bucket them, start with SMS error codes explained and SMS API error codes and troubleshooting.
The short version
Error 30007 is a carrier filter, not a code bug. Check registration first, then wording, then links, then send pattern, and test a plain copy on a few handsets. Don't retry blindly, and don't hop numbers. Once the cause is clear, fix it at the source, and your delivery should recover as the sender's reputation does.