Meta API Error 200 — Permission Error
Meta API error 200 means the app lacks permission for the requested operation. Learn which permissions are needed and how to request the correct scopes.
Meta API error 200 means the app lacks the required permission for the requested action. Check which permission is needed for the endpoint (e.g. ads_management, ads_read, business_management), ensure the app has been approved for that permission, and that the user granted it during Login.
What Causes Meta / Facebook Error 200?
Meta's permission system requires apps to request specific permissions during user login (via Facebook Login scopes) and many ad-related permissions require App Review approval by Meta. Error 200 fires when the access token doesn't include a required permission or when the permission was not granted by the user.
- 1App was not granted required permission during Facebook Login
- 2Permission requires App Review and has not been approved by Meta
- 3User denied a specific permission during the Login flow
- 4Permission was revoked by the user after initial grant
- 5Token generated before a new permission was added to the app
How to Fix Meta / Facebook Error 200
- 1Identify the required permission for your endpoint: check Meta's API reference for required scopes.
- 2Verify your app has App Review approval for that permission (Business permissions like ads_management require review).
- 3If the user hasn't granted the permission, re-run Login flow requesting the missing scope explicitly.
- 4Use the Token Debugger (developers.facebook.com/tools/debug) to inspect which scopes the current token has.
- 5Submit for App Review if the permission requires it — this can take 5–7 business days.
Official Meta / Facebook Documentation
https://developers.facebook.com/docs/permissions/reference
AdSkull Handles Meta / Facebook API Errors Automatically
Stop manually debugging API errors. AdSkull monitors your Meta / Facebook campaigns 24/7, detects authentication failures and permission issues, and surfaces clear actionable fixes — or handles them automatically when possible.
Other Meta / Facebook API Errors
Invalid OAuth Access Token
Meta API error 190 means your access token is invalid, expired, or has been revoked. Step-by-step guide to re-generating a valid Meta user or system access token.
Too Many API Calls
Meta API error 80004 means you have exceeded the rate limit. Learn how Meta rate limits work and how to implement proper throttling and backoff to fix this.
Invalid Parameter
Meta API error 100 means one or more parameters in your API request are invalid. Learn how to identify the invalid parameter and fix your request.
Custom Audience Terms Not Accepted
Meta API error 1870034 blocks audience creation when Custom Audience Terms have not been accepted. Learn the exact Business Manager fix before relaunching campaigns.
Targeting Category Deprecated
Meta API error 1487694 can appear when an ad set uses a deprecated targeting category. Learn how to replace removed interests and behaviors with Targeting Search.