Error 133010 is the plainest message in the WhatsApp Cloud API. Meta documents it as "Phone number Not Registered," describing it as a phone number not registered on the WhatsApp Business Platform, with an HTTP status of 400 and a recommended action of registering the phone number before trying again (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-20).
There is no ambiguity about the cause. The confusion is elsewhere: a number can be visible in your Meta dashboard, attached to your WhatsApp Business Account, and still not be registered in the sense this error means. Adding a number and registering it are two different operations, and the dashboard does not make that obvious.
This guide covers that distinction, the registration sequence, and what to have in hand before you start so it takes twenty minutes rather than three days. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
Added Versus Registered
This is the distinction that makes an unambiguous error confusing.
Added to the WABA means the number exists as an asset on your WhatsApp Business Account. You can see it in Meta Business Manager, it has a phone number ID, and it appears in API listings.
Registered means the number has completed verification and holds a valid credential binding it to your account for sending. Only a registered number can send messages.
A number in the first state but not the second returns 133010 on every send while looking entirely healthy in the dashboard. That is what sends teams looking at their code, their token, and their templates before checking registration state.
The states that produce it:
State | How you got here |
|---|---|
Added but never registered | Onboarding stopped after adding the number |
Registration abandoned | The flow was started and never completed, usually at the verification code step |
Deregistered | An explicit deregistration, or a provider migration that removed the binding |
Registered elsewhere | The number is registered to a different WABA than your credentials |
What To Have Ready Before You Start
Registration is short when you have these four things and a multi-day outage when you do not. Gather them first.
1. The two-step verification PIN for the number. This is the item that causes the delay. It was set once during original onboarding — often by an agency or a colleague who has since left — and frequently never documented. Check your secret manager, onboarding runbook, and any provider handover documentation now.
If it is genuinely unavailable, you do not need the old one. Disable two-step verification using a token with whatsapp_business_management permission, then set a new PIN. What you must not do is guess: wrong attempts trip the lockout in error 133008, which adds a mandatory cooldown, and attempting during that cooldown restarts it. The full reset path is in error 133005.
2. Access to receive a code on that number. Verification is by SMS or voice call to the number itself. Someone needs the handset, or a diversion that reaches a person who can read out a code. For a landline or a number owned by another department, arrange this before you begin.
3. Credentials with management permission. Registration needs whatsapp_business_management. If the call fails on permissions rather than registration, you are looking at error 3 or error 10 first.
4. Confirmation of which WABA owns the number. If the number is registered to a different account than the one you authenticate as, registration is not the problem — account mapping is. Businesses running multiple numbers on one WhatsApp Business Account, or several WABAs across brands, should keep an explicit map of display number, phone number ID, and owning account per environment.
The Registration Sequence
- Confirm all four prerequisites above.
- Request registration for the phone number ID, supplying the two-step verification PIN.
- Complete verification with the code delivered by SMS or voice call.
- Write the PIN to your secret manager with a named owner and the numbers it covers, if it is not already there.
- Send a test message to confirm the number can actually send, rather than assuming.
If step 2 returns a PIN mismatch, stop and read error 133005 rather than trying again. If it returns a certificate error, see error 131045, which is the same territory approached from a different angle — Meta documents that one as "Incorrect certificate" with HTTP 500 while this one is a clean 400, but both resolve through registration.
Three Gates, Not One
The reason 133010 so often appears during a launch week is that registration is only one of three independent checks, and teams tend to discover them one at a time.
Gate | Error if not cleared | Lead time |
|---|---|---|
Phone number registered | 133010 | Short, if you have the PIN and code access |
Display name approved | Usually hours, no published maximum | |
Billing configured | Depends on your finance team | |
App has advanced access | App review — the longest of the four |
Clearing one does not clear the others, and they surface sequentially: you register the number, then discover the display name is pending, then discover billing has no payment method. Each looks like a fresh problem.
The fix is to treat all four as a single onboarding checklist worked in parallel weeks before launch, rather than as errors encountered on the day. Our guide to setting up the WhatsApp Business API covers the full sequence, and creating a WhatsApp Business account covers the profile work that supports it.
For teams changing providers, all four gates are re-checked, which is why a migration deserves the same preparation as an initial launch. See switching WhatsApp API provider.
Frequently Asked Questions
What does WhatsApp error 133010 mean?
The phone number is not registered on the WhatsApp Business Platform, so it cannot send messages. Meta documents it as "Phone number Not Registered" with HTTP status 400 and a recommended action of registering the number before trying again.
My number appears in the dashboard. Why does it say not registered?
Because adding a number to your WhatsApp Business Account and registering it for sending are two different operations. An added number has a phone number ID and is visible in Business Manager, but only a registered number holds the credential that permits sending. A number in the first state but not the second returns 133010 while looking healthy.
What do I need to register a WhatsApp phone number?
Four things: the two-step verification PIN for that number, the ability to receive an SMS or voice call on the number itself, credentials carrying whatsapp_business_management permission, and confirmation that the number belongs to the WhatsApp Business Account you are authenticating against. Missing the PIN is what turns this from a short task into a multi-day one.
What if nobody knows the two-step verification PIN?
You do not need the old PIN. Disable two-step verification using a token with management permission, set a new PIN, and store it before enabling verification again. Do not guess at the old one — wrong attempts trip the lockout in error 133008, and attempting during the resulting cooldown restarts it.
What is the difference between error 133010 and 131045?
They describe the same underlying problem from different angles and resolve the same way. Meta documents 133010 as "Phone number Not Registered" with HTTP 400, and 131045 as "Incorrect certificate" with HTTP 500 — one says the number is not registered at all, the other that the credential binding it to your account is wrong or stale. Work the registration sequence for either.
Prepare, Then Register
Error 133010 has no interesting diagnosis. The number is not registered, and Meta says so plainly. What determines whether it costs twenty minutes or three days is entirely preparation: whether someone can produce the two-step verification PIN, and whether anyone can receive a verification code on the number.
Both are organisational rather than technical, and both are worth fixing permanently. Store the PIN as a production credential with a named owner and a map of which numbers it covers. Keep a record of who can access each business number for verification. Then work registration, display name approval, billing, and app access as one parallel checklist during onboarding — not as four surprises during launch week.
Want the go-live gates cleared before they become blockers? Helo.ai is a Meta Partner and Google RCS Anchor Partner of the Year, managing number registration, verification, display name approval, and billing setup for enterprise WhatsApp programmes. Talk to an expert.
Next: error 133005 if the PIN is the blocker, or error 131037 if display name approval is still outstanding.
