Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 200: No access token provided

Error code 200 on its own, often with the message "Provide valid app ID", means the request arrived without an access token. The wording is misleading: the app ID is fine, the token is missing.

200
Code
No access token provided
Meta's name
Authorisation
Type
On the API response
Where you see it
After fixing the cause
Retry

Quick answer

The request had no access token. Make sure every call sends a valid token, typically in the Authorization header.

What WhatsApp error 200 means

Meta documents 200 as: no access token was provided, with the message "Provide valid app ID". It occurs on certain read endpoints, such as the WhatsApp business profile, when no token is included, while other endpoints may return 190 or 104 instead. Meta stresses this is distinct from 190, an expired or invalid token.

Why error 200 happens

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

  • The Authorization header was dropped by a proxy, a redirect or a client library.
  • An environment variable holding the token was empty in that environment.
  • A typo in the header name, or Bearer without a token after it.
  • A request built for a public endpoint was reused for a protected one.

How to fix error 200

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

  • Log the outgoing headers of the failing call, with the token redacted, to confirm whether it's there.
  • Check the environment variable or secret that supplies the token in that environment.
  • Send the token as Authorization: Bearer followed by the token, without extra spaces or quotes.
  • Avoid redirects on API calls; some clients strip the Authorization header when following one.

Should you retry after 200?

Retry once the token is actually being sent. The same request will keep failing.

How error 200 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 200, the "(#200)" 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 does the error say "Provide valid app ID"?+
That's the message Meta returns on some read endpoints, such as the business profile, when no token is included. The real problem is the missing token, not the app ID.
Is error 200 the same as the 200–299 permission range?+
Meta lists both. Code 200 here means no token was provided; the 200–299 range covers permissions that weren't granted or were removed. Check whether a token was sent at all before looking at permissions.
Can error 200 appear on message sends?+
Meta describes it on certain read endpoints. Other endpoints may report a missing token as 190 or 104, so treat all three as signs the request's credentials need checking.