WhatsApp Cloud API Error 133xxx: The Registration Codes That Can Lock a Number for 72 Hours
A client is ready to go live. The number is verified, the display name is approved — and the registration call still fails with a four-digit code nobody explained. The 133xxx family is not one error. It is the entire registration and two-step-verification lifecycle, and one of its nine codes shares a single rate-limit bucket between two opposite actions.
What the 133xxx family actually covers
Registration lifecycle
Codes for a number that is not yet registered, mid-migration, or stuck after a failed deregistration attempt.
Two-step verification
PIN mismatch, PIN guessed too fast, and too-many-guesses lockouts — all separate codes with separate cooldowns.
Register/deregister rate limit
One shared 72-hour window that governs both actions on the same phone number, combined.
The trap most integrations hit: Meta's own registration documentation confirms that register and deregister calls draw from the same limit — 10 requests per business number in a rolling 72-hour window, combined. Debugging by deregistering and re-registering the same number a few times while troubleshooting a PIN or connectivity issue can burn through that shared quota fast, and the response is error 133016, which blocks the number from registering or deregistering for the next 72 hours.
The nine registration & two-step-verification codes
| Code | Meaning | What it signals |
|---|---|---|
| 133000 | Incomplete deregistration | A previous deregister attempt failed midway — the number needs deregistering again before it can register. |
| 133004 | Server temporarily unavailable | Platform-side outage, not a configuration issue. |
| 133005 | Two-step verification PIN mismatch | The 6-digit PIN sent doesn’t match what’s set on the number. |
| 133006 | Phone number re-verification needed | Ownership verification must be redone before registering. |
| 133008 | Too many PIN guesses | Repeated incorrect PIN attempts trigger a separate cooldown from 133016. |
| 133009 | PIN guessed too fast | Retries submitted faster than Meta’s throttling allows. |
| 133010 | Phone number not registered | The number was never registered on the platform in the first place. |
| 133015 | Recently deleted, wait before retry | A short-lived block after a number deletion, separate from the 72-hour window. |
| 133016 | Register/deregister rate limit exceeded | The shared 72-hour, 10-request combined ceiling described above. |
Where WhatsApp Cloud API setups actually get stuck
1. Ownership and eligibility aren’t fully settled first
Registration only succeeds after the number is added and ownership-verified inside WhatsApp Manager — skipping ahead produces 133006 or 133010.
2. The two-step verification PIN gets treated as an afterthought
A wrong or reused PIN, or repeated guesses under time pressure, triggers 133005, 133008, or 133009 — each with its own cooldown, not a single retry.
3. Troubleshooting attempts burn the shared rate-limit window
Deregistering and re-registering to “reset” a stuck number counts against the same 10-per-72-hour bucket as normal registration, so repeated attempts lock the number out entirely.
4. A failed deregistration leaves the number in limbo
133000 means a previous deregister call didn’t finish cleanly — the fix requires another deregister call, which itself counts against the shared limit.
5. Migrated or recently deleted numbers hit timing windows
133015 and the On-Premises-to-Cloud migration path each carry their own waiting periods that aren’t documented anywhere near the main error table.
For a SaaS platform onboarding client numbers through Tech Provider access (see our Embedded Signup & Tech Provider guide), a single mishandled registration retry loop can lock several client numbers out for three days at once — and a locked registration status compounds with the account’s messaging quality rating if support tickets pile up during the wait. I handle WhatsApp Cloud API number registration, two-step verification setup, and Tech Provider onboarding end to end as part of WhatsApp API approval and setup support — so the registration sequence is done right the first time, without triggering a self-inflicted 72-hour lockout.
Sourced from Meta’s official WhatsApp Cloud API documentation (Error Codes and Register a Business Phone Number pages, both fetched August 2026). Rate-limit and cooldown figures are quoted as published; no approval timelines or success figures are claimed beyond what Meta documents.