Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 0: AuthException

Error code 0 is Meta's authentication failure: the call reached Meta, but Meta couldn't confirm who was making it. Nothing else about the request matters until the credentials are sorted out.

0
Code
AuthException
Meta's name
Authorisation
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

Meta couldn't authenticate the app user behind the call. The access token has usually expired, been invalidated, or lost its rights; get a valid token and try again.

What WhatsApp error 0 means

Meta documents code 0 as: we were unable to authenticate the app user. It explains that this typically means the access token has expired, been invalidated, or the user changed a setting that blocks all apps from accessing their data, and that the fix is to get a new access token.

Why error 0 happens

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

  • A short-lived user access token was used in production and expired after a few hours.
  • The token was invalidated when the user who created it changed their password or logged out of sessions.
  • The user who granted access removed the app or turned off app access for their account.
  • A token was copied with extra characters or truncated in a configuration file.

How to fix error 0

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

  • Check the token with Meta's access token debugger to see whether it's valid and when it expires.
  • For servers, use a system user token rather than a personal user token, so it doesn't depend on one person's login.
  • Replace the token everywhere it's stored, including secrets managers and environment variables.
  • Test with a simple read call before resuming sends.

Should you retry after 0?

Retrying with the same token fails every time. Retry only after the token has been replaced or access restored.

How error 0 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 0, the "(#0)" 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

What is the difference between error 0 and error 190?+
Both point to the access token. Meta uses 190 specifically for an expired or invalid token, while 0 is the broader authentication failure that can also come from the user removing app access. In both cases, a valid token fixes it.
Why did error 0 start without any code change?+
Tokens can stop working because of things outside your code: a token reaching its expiry, an admin changing their password, or someone removing app access during a security review. Check what changed in the business around the time the errors began.
Can error 0 affect only some calls?+
If different parts of your system use different tokens, yes. A service still using an old personal token fails while others work, which is a good reason to keep tokens in one managed place.

Connect once, send without token juggling

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