WhatsApp error 200: No access token provided
Last verified against Meta for Developers - Cloud API error codes
No access token was provided.What error 200 means
Code 200 on its own (as opposed to the wider 200-299 permission range) is what certain GET endpoints return when the request carries no access token at all. Meta's reference names whatsapp_business_profile as an example, and notes that the response message reads Provide valid app ID, which sends many developers hunting for an app ID problem that does not exist. The real problem is that the Authorization header or access_token query parameter never reached Graph.
Meta also points out that other endpoints answer the same missing-token situation differently, returning 190 or 104 instead, so the code you see depends on which endpoint you called. Separately, the registration guide documents that calling /deregister without the whatsapp_business_messaging permission also returns code 200.
This is not an expired token. An expired token produces 190; a missing one produces this.
What it looks like
GET https://graph.facebook.com/v23.0/<PHONE_NUMBER_ID>/whatsapp_business_profile
(no Authorization header)
{
"error": {
"message": "Provide valid app ID",
"type": "OAuthException",
"code": 200,
"fbtrace_id": "AbC1dEf2GhI3jKl"
}
}Why it happens
- The Authorization header was dropped by a proxy, redirect, or HTTP client that strips headers on redirect.
- An environment variable holding the token was empty in this deployment, so the code sent
Bearerwith nothing after it. - A GET call was built by string concatenation and the
access_tokenparameter was never appended. - Calling
/deregisterwith a token that lackswhatsapp_business_messaging.
How to fix WhatsApp error 200
- 1Log the outgoing request (headers redacted to the first few characters) and confirm an Authorization header is present.
- 2Check that the token variable is populated at runtime in the failing environment, not just locally.
- 3Paste the token into Meta's access token debugger to confirm it is valid and carries the permissions the endpoint needs.
- 4For deregistration, use a token with
whatsapp_business_messaginggranted on the WABA. - 5Repeat the GET; once a valid token is attached the call should either succeed or return a more specific code.
How to stop it recurring
Fail fast at startup if the token variable is empty, and wrap every Graph call in one client that always attaches the header rather than building URLs by hand. Disable automatic redirect following for Graph requests, or confirm your client preserves headers across it, so a missing credential surfaces in tests instead of production.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
Error 200 - quick answers
What does WhatsApp error 200 mean?
Code 200 on its own (as opposed to the wider 200-299 permission range ) is what certain GET endpoints return when the request carries no access token at all. Meta's reference names whatsapp_business_profile as an example, and notes that the response message reads Provide valid app ID , which sends many developers hunting for an app ID problem that does not exist.
How do I fix WhatsApp error 200?
1. Log the outgoing request (headers redacted to the first few characters) and confirm an Authorization header is present. 2. Check that the token variable is populated at runtime in the failing environment, not just locally. 3. Paste the token into Meta's access token debugger to confirm it is valid and carries the permissions the endpoint needs. 4. For deregistration, use a token with whatsapp_business_messaging granted on the WABA. 5. Repeat the GET; once a valid token…
Stop debugging WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.