Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 10: Permission denied

Error code 10 is a permission refusal. Meta lists the usual token-permission cause, and two WhatsApp-specific ones: Flows set-up, and calling an API your account isn't eligible for.

10
Code
Permission denied
Meta's name
Authorisation
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

The permission for this call isn't granted, was removed, or your account isn't eligible for the API. Check the token's permissions, the Flows allowlist if you were setting a public key, and the API's eligibility rules.

What WhatsApp error 10 means

Meta documents code 10 as: permission is either not granted or has been removed. For WhatsApp Flows with an endpoint, it adds that the phone number used to set your business public key must be allowlisted; and it notes that you get this code when you aren't eligible for the endpoints you're calling.

Why error 10 happens

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

  • The token is missing a WhatsApp permission, or an admin removed it.
  • Setting the business public key for Flows from a phone number that isn't allowlisted.
  • Calling an API whose eligibility requirements your account doesn't meet yet.
  • The app's access to the WhatsApp Business Account was removed in business settings.

How to fix error 10

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

  • Check the token's permissions with the access token debugger.
  • If the error came while setting a Flows public key, confirm the number is allowlisted for it.
  • Read the eligibility requirements of the API you're calling and check your account meets them.
  • Restore the app's access to the account if it was removed, then call again.

Should you retry after 10?

Retrying without fixing permissions or eligibility fails the same way. Fix the cause, then retry.

How error 10 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 10, the "(#10)" message and error_data.details) alongside InfiQ's own 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 do I get error 10 when setting up a WhatsApp Flow?+
Meta notes that for Flows with an endpoint, the phone number used to set your business public key must be allowlisted. If it isn't, setting the key is refused with code 10.
Can error 10 mean my account isn't eligible?+
Yes. Meta says you receive code 10 when you aren't eligible to access the endpoints you're calling, so check the API's eligibility requirements as well as the token.
How is error 10 different from error 190?+
190 means the token itself is expired or invalid. With 10 the token can be perfectly valid; it just isn't allowed to do this particular thing.

Connect once, send without token juggling

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