Twilio error 30034 means you sent a text to a US recipient from a 10-digit local number that isn't tied to an approved A2P 10DLC campaign, and the carriers blocked it. The fix is to register the brand and campaign, attach the number to that campaign, and wait for approval before sending again.
Since carriers began enforcing registration, unregistered application-to-person traffic over standard US long codes gets blocked. 30034 is how that block shows up in your logs.
What the code is telling you
A2P 10DLC is the registration system US carriers use for business texting over local numbers. A brand (your business identity) is registered, then a campaign (what you send and why), and the numbers are linked to the campaign. A number that isn't linked to an approved campaign is treated as unregistered, and its messages to US numbers fail.
The error isn't about a single message. It's about the sender. Every text from that number will fail the same way until the registration is in place, so retries are pointless.
Common reasons you're seeing it
| Reason | Detail |
|---|---|
| The number was never registered | Bought a local number and started sending |
| Registration is still in review | Submitted, but not approved yet |
| Registration was rejected | The campaign needs corrections and a resubmit |
| Number not attached to the campaign | The campaign is approved but the number wasn't linked |
| Wrong sender type | Using a local number where toll-free or another route fits better |
A checklist to fix it
- Find the sender. Look at the
Fromnumber on the failed messages. Confirm every failure comes from the same unregistered number or numbers. - Check registration status. See whether the brand and campaign exist and what state they're in: approved, pending or rejected.
- Register the brand. You'll need the business's legal name, EIN, address, website and contact details. They must match what's on file with the tax authority.
- Register the campaign. Pick the right use case, write an honest description, add sample messages that look like real ones, and explain how people opt in. Weak consent language is a top reason for rejection. Consent language that passes registration shows what reviewers look for.
- Attach the numbers. Link every sending number to the approved campaign.
- Wait for approval, then test. Send a short test to your own handset before you restart production traffic.
- If it's rejected, read the reason. Fix what the reviewer named and resubmit. See decoding a 10DLC rejection.
If you want the background on why this exists and who has to register, read is 10DLC required and what the registration process involves for Twilio senders.
What about a sole proprietor?
Registration paths differ by provider and by business type. A business with a tax ID registers as a standard brand. Sole proprietor registration exists on some providers with tighter limits. If you're not sure which applies, read sole proprietor and low volume registration before you file.
Why retrying doesn't help
Some teams answer a blocked send by buying another number and trying again. That fails for the same reason: the new number isn't registered either, and you've added cost and confusion. The block follows the registration state, not the individual message or number. Fix the registration once, and every number attached to the approved campaign can send.
Toll-free is a different route
Toll-free numbers don't use 10DLC. They have their own verification process. If you'd rather not register a local number, a toll-free number is an option, with its own approval step. Toll-free number texting and SMS verification explains it.
How this shows up on Ready
On Ready, each customer gets a sub-account with its own numbers and its own carrier registration, so one customer's registration state never decides another's. Brand and campaign registration is handled in the app as a single Registration step, and most approvals take 2 to 7 days. Ready registers businesses that have an EIN. A sole proprietor without one can't register there.
For platforms that onboard customers in code, registration is available through the API:
GET /v1/registrationreturns the registration status.POST /v1/registration/brand,POST /v1/registration/campaignandPOST /v1/registration/confirmsubmit it.
So when a sender is blocked for being unregistered, the first call is GET /v1/registration to see whether the account has been approved, is still in review, or needs changes. The request shapes and fields are in the docs at https://docs.tryready.com/api/registration, and the app walkthrough is at https://docs.tryready.com/guides/registration. Error handling is at https://docs.tryready.com/api/errors.
Our post on the 10DLC registration API covers building this into an onboarding flow.
Stopping it from coming back
For a multi-tenant product, the lasting fix is a gate in your own flow. Don't let a new customer's number send until their registration shows approved. That turns a carrier error that confuses customers into a clear "registration pending" state they understand. Launching SMS without managing carrier registration describes how to keep that out of your support queue.
The short version
Error 30034 means the sending number isn't on an approved A2P 10DLC campaign. Register the brand, register the campaign, attach the numbers, wait for approval and test. Don't retry in the meantime. For the broader set of codes, see SMS error codes explained and SMS API error codes and troubleshooting.