WhatsApp error 33: Parameter value is not valid
Last verified against Meta for Developers - Cloud API error codes
The business phone number has been deleted.What error 33 means
Code 33 on the Cloud API means the phone number ID in your request path points at a business phone number that no longer exists. The Graph API's generic title for this code is "Parameter value is not valid", but Meta's WhatsApp documentation is more specific: the business phone number has been deleted. The platform is not rejecting your message content; it cannot find the sender you named.
This usually follows an account event rather than a code change. Someone deleted the number from WhatsApp Manager, migrated it to a different WABA, or tore down a test WABA whose phone number ID was still hard-coded in a config file. The ID is a long numeric string that looks nothing like the phone number itself, which is why stale IDs survive unnoticed.
Your token, templates, and recipients are all fine. The request is simply addressed to a sender that is gone.
Why it happens
- The business phone number was deleted from the WhatsApp Business Account in WhatsApp Manager.
- The number was migrated to another WABA, which issues a new phone number ID.
- A test WABA was removed and the environment still references its phone number ID.
- Configuration for the wrong environment was deployed, carrying an ID from a decommissioned account.
- The phone number ID was mistyped or truncated when copied into configuration.
How to fix WhatsApp error 33
- 1Call GET /{waba-id}/phone_numbers with your token and list the IDs that currently exist.
- 2Compare the ID in your failing request against that list; if it is absent, the number is gone.
- 3Update configuration with the correct current phone number ID and redeploy.
- 4If the number was migrated, re-register it on the new WABA and subscribe your app to that WABA's webhooks.
- 5Re-send the failed messages once a live sender ID is in place.
How to stop it recurring
Resolve phone number IDs at startup by listing the WABA's numbers and matching on display_phone_number, rather than hard-coding IDs. Emit an alert on code 33 because it signals an account-level change, and keep WhatsApp Manager deletions behind a change-management step so production IDs are not removed without notice. A number that exists but was never activated raises 133010 instead; number lifecycle problems are covered end to end in the registration troubleshooting guide.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
Error 33 - quick answers
What does WhatsApp error 33 mean?
Code 33 on the Cloud API means the phone number ID in your request path points at a business phone number that no longer exists. The Graph API's generic title for this code is "Parameter value is not valid", but Meta's WhatsApp documentation is more specific: the business phone number has been deleted. The platform is not rejecting your message content; it cannot find the sender you named.
How do I fix WhatsApp error 33?
1. Call GET /{waba-id}/phone_numbers with your token and list the IDs that currently exist. 2. Compare the ID in your failing request against that list; if it is absent, the number is gone. 3. Update configuration with the correct current phone number ID and redeploy. 4. If the number was migrated, re-register it on the new WABA and subscribe your app to that WABA's webhooks. 5. Re-send the failed messages once a live sender ID is in place.
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.