Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 200-299: API permission

Codes from 200 to 299 are Meta's family of API permission errors. Whatever the exact number, the call was refused because the token or the app doesn't have permission for it.

200-299
Code
API permission
Meta's name
Authorisation
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

The app or token lacks permission for this call, or it was removed. Check granted permissions, restore what's missing and call again.

What WhatsApp error 200-299 means

Meta documents the 200–299 range as: permission is either not granted or has been removed, with the same advice as for codes 3 and 10: use the access token debugger to verify that the app has the permissions the endpoint requires.

Why error 200-299 happens

Authorisation errors come from the token or the app's permissions. Usually one of these:

  • The token was generated without a permission the endpoint needs.
  • An admin removed a permission, or the app's access to the WhatsApp Business Account.
  • The system user behind the token lost its role on the account.
  • A permission is pending app review and isn't active yet.

How to fix error 200-299

Work through these in order; the first one that turns up a problem is usually the fix.

  • Read the exact code and message, then check the token's permissions in the access token debugger.
  • Confirm the app still has access to the right WhatsApp Business Account.
  • Check the system user's role and assigned assets in business settings.
  • Grant what's missing, generate a fresh token and retry the call.

Should you retry after 200-299?

Retrying with the same token fails until the permission is restored. Retry with a token that carries it.

How error 200-299 shows up in InfiQ

If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 200-299, a message beginning "(#200-299)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up. With InfiQ you send with an InfiQ API key; the Meta access token behind it belongs to InfiQ's connection to your WhatsApp Business Account. If this code reaches you, that connection needs attention: contact InfiQ support with the InfiQ_traceid rather than generating tokens yourself.

Send it through InfiQ

Frequently asked questions

Why does Meta use a range of codes for permissions?+
The Graph API groups permission errors in the 200–299 range. For WhatsApp the fix is the same across the range: check what the token is allowed to do and restore the missing permission.
Do I need a new token after fixing permissions?+
Usually yes. A token carries the permissions that were granted when it was generated, so after adding one, generate a new token and update it wherever it's stored.
Can a permission error appear suddenly?+
Yes, if someone changes roles, removes an app during a clean-up, or moves the account to another business portfolio. Check recent changes in business settings.

Connect once, send without token juggling

Send with an InfiQ API key while InfiQ manages the connection to your WhatsApp Business Account.