Unsupported post request. Object with ID '{object_id}' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api (error code 100, subcode 33)
In short
The API call targets an object ID that does not exist, that the access token is not allowed to load, or that does not accept this kind of request. Check the ID and the endpoint, then the access of the token’s user or system user.
By Mathieu Malige, co-founder of Apogee
· Checked on 8 October 2026
Exact message
| English | French | |
|---|---|---|
| Message (Graph API response) | Unsupported post request. Object with ID '{object_id}' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api | not captured yet |
| Short version (Meta’s Marketing API error reference) | Unsupported post request. | Requête POST non compatible. |
Where it shows up: in the response of Meta’s Marketing API or Graph API (developers, tools and integrations); Meta’s error reference documents the short version for code 100, subcode 33.
Why it happens
- The message lists three causes: the object does not exist, it cannot be loaded because of missing permissions, or it does not support the operation.
- A documented permission case. Meta’s error reference says code 100, subcode 33 may occur if your access token is not added as a system user with appropriate permissions to the ad account that owns a Custom Audience.
- Code 100 is the “Invalid parameter” code in that same reference.
How to fix it
- Check the ID in the request: it must be the right object, of the right type for this endpoint.
- Check that the token’s user (or system user) has access to that object, for example a role on the ad account.
- For Custom Audiences, Meta’s reference asks you to verify the ad account in Meta Business Suite and that all system users appear under it as Admin: in Business Settings, click the ad account, select Add people, search for the system user and add it as an admin, then retry the call.
- Check in Meta’s API reference that the endpoint accepts a POST for that object.
What worked for other advertisers
Developers who got this message with the WhatsApp Cloud API fixed it by generating a new access token in the Graph API Explorer with three permissions: whatsapp_business_management, whatsapp_business_messaging and business_management. Under the video that shows it, 7 people say it worked and about 15 were still stuck; one wrote “we officially crown you a LEGEND 👑 You just saved us hours”. The takeaway: the token must carry the permissions of the object you call.
Source: YouTube video on this error (WhatsApp Cloud API) and its comments
How to avoid it next time
- Store object IDs per ad account and check them when a user switches accounts.
- Give system users the role they need on each ad account before using them.
Frequently asked questions
Does the object really not exist?
Not necessarily. The same message also covers an object the token cannot load because of missing permissions, or one that does not support the operation.
Is this an Ads Manager error?
No. It is returned by the Graph API to apps and tools.
What is subcode 33?
Meta’s error reference lists it under code 100 (invalid parameter) as an unsupported post request, with the case of an access token not added as a system user with appropriate permissions to the ad account that owns a Custom Audience.
Related errors
Launch your creatives in 47 seconds
Bulk upload on Meta Ads, TikTok Ads and Snapchat Ads, with your naming convention detected and Advantage+ off by default. 15 free creatives, no credit card.