Meta Tech Provider

WhatsApp error 133005: incorrect two-step verification PIN

Error 133005 means the two step verification PIN supplied during registration was incorrect. It is a six digit PIN set when the number was first registered, and repeated wrong guesses lock further attempts, so the recovery path matters more than the retry.

133005

Meta's code for an incorrect two-step verification PIN.

133008

The code returned once too many incorrect PIN guesses have been made.

Digits in a WhatsApp two-step verification PIN.

Where the PIN comes from

It is set the first time the number is registered for Cloud API messaging, and it is needed again on any later registration, including after migrating the number to a different account.

That gap is where the problem starts. A PIN set once at setup and not needed for a year is rarely written down, and the person who set it has often moved on. The error then appears at exactly the moment the number is being moved or re-registered, which is already a pressured moment.

If nobody knows it

There is a path, and it is slower than guessing but it actually works.

Stop guessing. Repeated failures return 133008 and lock attempts for a period.
Change the PIN in WhatsApp Manager under the number's two step verification settings; there is no API endpoint to disable it.
An admin can also set a new PIN through the API with a POST to the phone number ID, then re-register with it.
Once recovered, store the new PIN where the next person will find it.

Avoiding it next time

Treat the PIN as infrastructure rather than a personal detail. It belongs in the same place as the account credentials, owned by the business rather than by whoever happened to run the setup, and it should survive that person leaving.

The cost of not doing this is not the error itself, which is trivial. It is being unable to migrate or re-register a working number at the moment you need to.

Common mistakes

Guessing repeatedly. It triggers 133008 and a lockout.
Storing the PIN with one person rather than with the business.
Assuming it is never needed again after setup. Migration needs it.

Doing this with EasyCoexistence

EasyCoexistence connects numbers through Meta's own flow and keeps the resulting credentials available in the dashboard, so account level details are not stored in one person's memory.

Frequently asked questions

Where was this PIN set?

When the number was first registered for Cloud API messaging.

What if I do not know it?

Change it in WhatsApp Manager under the number's two step verification settings, or set a new one through the API.

What happens if I keep guessing?

Attempts lock and you get error 133008 instead.

When is the PIN needed?

At registration, and again on any re-registration or migration.

Keep reading

WhatsApp error 133008: too many PIN guessesError 133008 means too many incorrect two-step PIN attempts were made and the number is locked for a period. What to do while waiting.WhatsApp error 131045: phone number not registeredError 131045 means the number is not registered for messaging. What registration is, why it is separate from onboarding, and how Coexistence handles it.WhatsApp error 133006: phone number not verifiedError 133006 means the number must be verified before it can be registered. How verification differs from registration, and what it requires.WhatsApp Coexistence: the app and the API on one numberCoexistence runs the WhatsApp Business app and the Cloud API on the same number at once. What it changes, what it does not, and how a number gets connected.WhatsApp error 131050: the user has opted outError 131050 means the recipient chose not to receive messages from your business. Why it must be respected rather than worked around.WhatsApp Cloud API error codesEvery WhatsApp Cloud API error code in one table: what each one means, whether retrying helps, and the page that covers it in full.

Ready to get started?

Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.

Start Free Trial

Verified on 2026-10-12