---
title: "Meta API error 190: Invalid OAuth 2.0 Access Token"
description: "Meta error 190 means the login a tool uses for your Facebook account has expired or been revoked. Reconnect the tool to fix it. Causes by subcode."
---

> For AI agents: the full docs index is at [https://useproxy.dev/docs/llms.txt](https://useproxy.dev/docs/llms.txt). Append `.md` to any docs URL for Markdown.

Not serious, and your ad account is fine. Error 190 means the saved login (the access token) that a tool uses to act on your Facebook account has expired or been cancelled. Reconnect the tool to Facebook and it will get a new one. Developers report that Meta sometimes cancels these logins early "for security reasons", even when no password was changed, and that the user logging in again is what restores access, as in [this Meta developer forum thread](https://developers.facebook.com/community/threads/849474743510785).

Sources: Meta's developer docs, Meta's developer forum and one data tool's help page, checked November 2026.

## Try this, in order

1. In the tool showing the error (a shop platform, scheduler or reporting app), find its Facebook or Meta connection and click reconnect. Log in and approve the permissions. Data tools give the same fix for this error, for example [Fivetran's "Re-authorize connection" steps](https://fivetran.com/docs/connectors/applications/facebook-ads/troubleshooting/access-token-expired).
2. Changed your Facebook password lately? That cancels saved logins. Reconnecting fixes it.
3. Log in at facebook.com in a normal browser. If Facebook asks you to confirm something or complete a security check, finish it, then reconnect the tool.
4. Reconnect as the person who actually has access to the ad account and the Page.

## If that did not work

- **It comes back every couple of months.** Ordinary logins last about 60 days. Ask the tool's support or your developer to use a system user token, which Meta says does not expire based on time.
- **It comes back within hours.** The tool is using a short-lived login, which lasts about one to two hours. Your developer needs to exchange it for a long-lived one.
- **The message mentions a Page.** The person who connected the tool no longer has a suitable role on the Page. Reconnect as a Page admin.
- **You removed the tool from your Facebook settings.** Connect it again from the tool.

## When to stop and contact Meta

Rarely needed. Contact the tool's support first: the login belongs to their app. Go to Meta through the [Business Help Center](https://www.facebook.com/business/help) only if facebook.com itself will not let you log in or complete its security check.

## The detail

Meta's [Marketing API error reference](https://developers.facebook.com/docs/marketing-api/error-reference/) lists code 190 as "Invalid OAuth 2.0 Access Token." The [Graph API error handling guide](https://developers.facebook.com/docs/graph-api/guides/error-handling/) names it "Access token has expired" with the advice "Get a new access token", and breaks it down by subcode:

| Subcode | Name | Meta's advice |
| --- | --- | --- |
| 458 | App Not Installed | "The User has not logged into your app. Reauthenticate the User." |
| 459 | User Checkpointed | "The User needs to log in at https://www.facebook.com or https://m.facebook.com to correct an issue." |
| 460 | Password Changed | The person must log in to the app again |
| 463 | Expired | "Login status or access token has expired, been revoked, or is otherwise invalid." |
| 464 | Unconfirmed User | Same as 459 |
| 467 | Invalid Access Token | "Access token has expired, been revoked, or is otherwise invalid." |
| 492 | Invalid Session | "User associated with the Page access token does not have an appropriate role on the Page." |

Token lifetimes are from Meta's [access token guide](https://developers.facebook.com/docs/facebook-login/guides/access-tokens/), which warns: "Do not depend on these lifetimes remaining the same".

Look-alikes:

- **Error 102** is the same problem under an older name: get a new token.
- **Error 200 or 10** means the login works but lacks permission. See [error 200](https://useproxy.dev/docs/troubleshooting/meta-error-200-permission-error).

## Related

- [Meta Marketing API error 200: Permission error](https://useproxy.dev/docs/troubleshooting/meta-error-200-permission-error)
- [Meta Marketing API error 100: Invalid parameter](https://useproxy.dev/docs/troubleshooting/meta-error-100-invalid-parameter)
- [All troubleshooting pages](https://useproxy.dev/docs/troubleshooting)

While the connection is fixed, you can still see what competitors are running. [Proxy](https://useproxy.dev/welcome) reads the public ad libraries from your AI assistant, with no Meta token to manage. It does not manage ad accounts.
