Log inStart Free Trial
easyCoexistence Official APIs

Facebook error 190: access token invalid or expired

Facebook error 190 means the access token is no longer valid. Meta's message reads Invalid OAuth 2.0 Access Token, or starts Error validating access token, followed by the reason, such as Session has expired. Its fix is to get a new token, which for a Page usually means someone with a role on the Page signing in again. A subcode, when present, says why.

easyCoexistence calls each connected Page with its own Page token and checks the Page every 6 hours.

190

The Graph API code for an expired access token; Meta's recommended action is to get a new one.

460

Subcode sent when a person logged out or changed their password: The session is invalid because the user logged out.

492

Subcode for a Page token whose user does not have an appropriate role on the Page.

No expiry

Long-lived Page access tokens have no expiration date; they expire or are invalidated only under certain conditions.

No notice

Facebook does not notify an app when one of its access tokens has become invalid.

What does error 190 mean on a Facebook Page?

Meta no longer accepts the access token in the request. Its Graph API error guide lists 190 as an expired access token, with one fix: get a new access token. Meta's references for Page photos and videos describe the code as Invalid OAuth 2.0 Access Token, and its guide to sending Messenger messages says to generate a new Page access token.

What do the subcodes mean?

When a subcode comes with the error, Meta's table of authentication subcodes says why the token was refused, and its token debugging guide shows the message that goes with some of them:

  • 463, Expired: the token has expired. The message reads Error validating access token: Session has expired on, followed by the date.
  • 467, Invalid Access Token: the token has expired, been revoked or is otherwise invalid.
  • 460, Password Changed: Error validating access token: The session is invalid because the user logged out. The person logged out or changed their password, and logs in again.
  • 458, App Not Installed: Error validating access token: User {user-id} has not authorized application {app-id}. The person has to be authenticated again.
  • 459, User Checkpointed, and 464, Unconfirmed User: the person has to log in at facebook.com to correct an issue.
  • 492, Invalid Session: the person behind the Page token does not have an appropriate role on the Page.

Do Facebook Page tokens expire?

Not on a schedule, when they come from a long-lived user token. Meta's guide to long-lived tokens says such a user token generally lasts about 60 days, while long-lived Page access tokens do not have an expiration date and expire or are invalidated only under certain conditions. Meta's token debugging guide adds that tokens may be invalidated before their expected expiry because of security-related events.

How do you fix it?

Get a new token, which for a Page comes from a fresh sign-in. Meta issues a Page token only to a person with a role on the Page, so if the person who connected it has left or lost that role, someone who still manages the Page signs in instead. With subcode 459 or 464, the person first logs in at facebook.com and resolves what Facebook asks, then signs in again.

How do you catch it before a call fails?

Check the token on a schedule. Facebook does not tell an app when a token stops working, so a regular request with the Page token, such as reading the Page's id and name, finds a 190 before a post or a Messenger reply depends on it. Meta's debug_token endpoint also returns whether a token is valid, when it expires and the permissions it holds.

A quick check of a Page token
curl "https://graph.facebook.com/<PAGE_ID>?fields=id,name&access_token=<PAGE_ACCESS_TOKEN>"

# Valid: the Page comes back
{"id": "<PAGE_ID>", "name": "<PAGE_NAME>"}

# Rejected: code 190, with a subcode when Meta gives one
{"error": {"type": "OAuthException", "code": 190, "error_subcode": 460, "message": "..."}}

Common mistakes

  • Retrying the call. A rejected token stays rejected, and only a new token from a fresh sign-in clears the error.
  • Assuming a Page token lasts forever. It has no expiry date, but Meta still invalidates tokens under certain conditions, and error 190 is how that shows.
  • Connecting the Page again with an account that has no role on it. Meta gives Page tokens only to people with a role on the Page.
  • Keeping your own copy of the Page token. After a fresh sign-in, the stored copy is still the rejected one, so fetch the current token instead.
Doing this with EasyCoexistence

When Meta answers 190, during a check or any other call, the connection is marked for reconnecting at once and you get an email, and the tools tell your AI the Page needs connecting again. Signing in from the dashboard brings the same connection back with a new token. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.

easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.

Frequently asked questions

What does Error validating access token mean?

It is the start of Meta's message for error 190: the token in the request is no longer valid. The rest of the message gives the reason, such as an expired session or a logout.

Does changing my Facebook password break the Page token?

Yes. A logout or password change invalidates it, with subcode 460, and someone with a role on the Page has to sign in again.

What does subcode 492 mean?

The person whose sign-in produced the Page token does not have an appropriate role on the Page. Someone who manages the Page has to connect it again.

Can a Page token be refreshed after error 190?

No. Meta's fix is a new access token, and for a Page that comes from someone with a role on the Page signing in again.

Keep reading

Connect your first channel in two minutes.

No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.

  • 3 days free
  • Cancel any time
  • Official APIs only
  • Monitored 24/7

Verified on