Meta API Error 190 — 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.
Meta API error 190 means the access token is invalid or expired. Causes: short-lived token expired (2 hours), user changed password, user revoked app access, or permissions were removed. Fix: use long-lived tokens or system user tokens for server-to-server calls, or prompt the user to re-authenticate via Meta Login.
What Causes Meta / Facebook Error 190?
Meta has several token types with different lifespans: User Access Tokens (short-lived: 2 hours; long-lived: 60 days), Page Access Tokens, and System User Access Tokens (never expire unless revoked). Error 190 fires when the token used is no longer valid. For production ad integrations, System User Access Tokens are strongly preferred as they don't expire on password changes.
- 1Short-lived user access token expired (valid for only 2 hours)
- 2Long-lived user access token expired (valid for 60 days)
- 3User changed their Facebook password, invalidating all user tokens
- 4User manually revoked app access in Facebook settings
- 5Token was generated for a different app_id
- 6User's account was disabled by Meta
How to Fix Meta / Facebook Error 190
- 1For user-facing apps: prompt the user to re-authenticate via Facebook Login and exchange for a new token.
- 2For server-to-server apps: switch to System User Access Tokens which do not expire on password changes. Create via Business Manager > System Users.
- 3Exchange short-lived tokens for long-lived tokens immediately after user login using the token exchange endpoint.
- 4Implement token health checks: before each API call, verify the token is valid or refresh proactively.
- 5Store token expiry time and set up alerts 7 days before expiry for long-lived tokens.
Official Meta / Facebook Documentation
https://developers.facebook.com/docs/facebook-login/access-tokens/debugging-and-error-handling
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
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.
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.