WhatsApp error 133005: Two step verification PIN Mismatch
Last verified against Meta for Developers - Cloud API error codes
Two-step verification PIN incorrect.What error 133005 means
Code 133005 means the six-digit two-step verification PIN you supplied in a register call does not match the PIN set on the phone number. Every Cloud API phone number must be registered with a PIN, and once set, the same PIN is required for future registrations and migrations. If a different team member set the PIN, if it was changed in WhatsApp Manager, or if the number came from the WhatsApp Business app with a PIN the developer never knew, the register call fails with 133005.
This is safe to see once or twice, but be careful: repeated wrong guesses lead to 133008 (too many guesses), guesses in rapid succession lead to 133009, and a pattern of failures can contribute to an account lock (131031). Meta's documentation describes a reset path: disable two-step verification, then send a POST to the phone number endpoint with the new PIN.
Your token, number, and app are all fine; only the secret is wrong.
Why it happens
- The PIN stored in your configuration is from a different number or environment.
- Someone changed the PIN in WhatsApp Manager after automation was set up.
- The number was migrated from the WhatsApp Business app and still carries the PIN set there.
- A placeholder PIN such as 000000 left in a deployment.
- Leading zeros stripped by a numeric type in configuration, turning 012345 into 12345.
How to fix WhatsApp error 133005
- 1Confirm the PIN with the person or team who set it, and store it as a string to preserve leading zeros.
- 2If unknown, disable two-step verification for the number in WhatsApp Manager (or via the API) and then set a new PIN with a POST to /{phone-number-id} including pin.
- 3Retry the register call with the correct PIN, spacing attempts out.
- 4Verify status is CONNECTED afterwards.
- 5Record the new PIN in your secrets manager.
How to stop it recurring
Treat the two-step PIN as a secret owned by the same system that owns the token: store it in a secrets manager as a string, document who can change it, and never rotate it without updating automation. Rate-limit registration attempts in your own code so a wrong PIN cannot escalate into 133008 or an account lock. The PIN reset sequence is part of the registration troubleshooting guide; the guess-limit and velocity blocks it can escalate into are 133008 and 133009.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
- 133008: Too Many two step verification PIN GuessesToo many two-step verification PIN guesses for this phone number.
- 133009: Two step verification PIN Guessed Too FastTwo-step verification PIN was entered too quickly.
- 131031: Account has been lockedThe WhatsApp Business Account associated with the app has been restricted or…
- 133010: Phone number Not RegisteredPhone number not registered on the WhatsApp Business Platform.
Error 133005 - quick answers
What does WhatsApp error 133005 mean?
Code 133005 means the six-digit two-step verification PIN you supplied in a register call does not match the PIN set on the phone number. Every Cloud API phone number must be registered with a PIN, and once set, the same PIN is required for future registrations and migrations.
How do I fix WhatsApp error 133005?
1. Confirm the PIN with the person or team who set it, and store it as a string to preserve leading zeros. 2. If unknown, disable two-step verification for the number in WhatsApp Manager (or via the API) and then set a new PIN with a POST to /{phone-number-id} including pin. 3. Retry the register call with the correct PIN, spacing attempts out. 4. Verify status is CONNECTED afterwards. 5. Record the new PIN in your secrets manager.
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.