Log inStart Free Trial
easyCoexistence Official APIs

Facebook Page access token: how long it lasts and what invalidates it

A long-lived Facebook Page access token has no expiration date. An app gets one by trading a person's sign-in for a long-lived user token, which lasts about 60 days, and reading /me/accounts; the person needs full control of the Page or task access. Meta still invalidates the token under certain conditions, such as that person losing their role on the Page.

easyCoexistence takes a long-lived Page token for each Page you connect, keeps it encrypted, checks the Page every 6 hours and emails you when Meta stops accepting it.

No expiry

Long-lived Page access tokens, generated from a long-lived user token, have no expiration date.

About 60 days

How long a long-lived user access token generally lasts; short-lived tokens last about one to two hours.

492

Error subcode for a Page token whose person no longer has an appropriate role on the Page.

90 days

After this long without the app using a permission, the person has to grant it again.

PROFILE_PLUS_FULL_CONTROL

One of the Page tasks Meta's API can assign, beside CREATE_CONTENT, MODERATE, MESSAGING and ANALYZE.

Does a Facebook Page access token expire?

It depends on the user token it came from. Meta's default user and Page tokens are short-lived and expire within hours, and a long-lived user token generally lasts about 60 days. A Page token generated from a long-lived user token has no expiration date: Meta says it only expires or is invalidated under certain conditions. Meta also warns not to rely on token lifetimes, which may change without warning.

How do you get a long-lived Page access token?

In three calls after the person signs in with Facebook Login for Business. The app exchanges the returned code for a short-lived user token, then trades that for a long-lived one at GET /oauth/access_token with grant_type=fb_exchange_token and the app secret, a call Meta says to make from a server. GET /me/accounts with the long-lived user token then returns each Page the person allowed, with its ID, the person's tasks and a Page token.

1Sign-inFacebook Login for Business returns a code
2User tokenThe code becomes a short-lived user token
3Long-livedfb_exchange_token trades it for about 60 days
4Page token/me/accounts returns one per Page, with no expiry

Who can connect a Page and get its token?

Someone who owns the Page or can perform tasks on it. In Facebook's Page settings and Meta Business Suite that means full control, or narrower task access such as Content or Messages, and Meta's Pages API overview adds that a person with Admin access can perform all tasks. Page tokens are unique to each Page, person and app, so two people connecting the same Page hold different tokens. The names in Facebook's interface map to API tasks this way:

Full controlPROFILE_PLUS_FULL_CONTROL
ContentPROFILE_PLUS_CREATE_CONTENT: publish as the Page
MessagesPROFILE_PLUS_MESSAGING: send messages as the Page
Community activityPROFILE_PLUS_MODERATE: reply to and delete comments
InsightsPROFILE_PLUS_ANALYZE: view the Page's Insights
AdsPROFILE_PLUS_ADVERTISE: create ads

Which task does each action need?

Meta checks, for each call, whether the person behind the token holds a task that permits the action, so connect from an account whose access covers the work:

  • Text, link and photo posts: CREATE_CONTENT.
  • Video posts: admin-equivalent tasks, according to Meta's Video API overview.
  • Comment IDs and replies as the Page: MODERATE.
  • Messenger replies and private replies: MESSAGING.
  • Insights: ANALYZE.
  • Feed webhooks: CREATE_CONTENT, MANAGE or MODERATE; the messages field: MESSAGING.

What invalidates a Page access token?

Meta reports a token it no longer accepts with error code 190, or 102 for a session, and an authentication subcode that says why. A person can also invalidate an app's user tokens by removing it under Business Integrations in Facebook's settings, and a permission the app has not used for 90 days has to be granted again. The subcodes Meta lists:

  • 458: the person has not logged into the app.
  • 459 or 464: the person must log in at facebook.com to fix an issue with their account.
  • 460: the person's password changed.
  • 463 or 467: the token expired, was revoked or is otherwise invalid.
  • 492: the person behind a Page token no longer has an appropriate role on the Page.

What does easyCoexistence do to keep a Page connected?

It takes each Page's token from a long-lived user token at sign-in, so there is no expiry to renew on a schedule, and stores it encrypted. Every 6 hours it checks each connected Page with a light Graph call. When Meta refuses the token with error 190 or 102, at that check or in any tool call, the Page is marked as needing reconnection, its owner gets an email and a partner platform receives channel.disconnected. Signing in again from an account that runs the Page restores it.

Can you use the Page token yourself?

Not the token itself. get_social_credentials returns the Page ID and the Graph API base on graph.facebook.com, but never the Page token (Meta's terms); the token does not expire while the Page stays connected, though Meta can still invalidate it. The MCP tools make the calls as the Page without exposing the token; the token and webhook subscriptions stay with easyCoexistence.

Common mistakes

  • Requesting the long-lived token from a browser. The exchange carries the app secret, so Meta says to make that call from a server, never client-side.
  • Trying to extend an expired token. Meta will not turn an expired token into a long-lived one; the person has to go through the login again.
  • Connecting through someone about to leave the business. The Page token rests on their access and stops working when they lose their role, so connect from an account that will stay.
  • Storing tokens in a fixed-length column. Meta changes token length over time and advises a variable-length type with no set maximum.
Doing this with EasyCoexistence

Your AI works through it with the MCP tools, which add the token for you, and get_social_credentials gives your own code the Page ID and API base. 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

Do Facebook permissions expire if the app stops using them?

Yes. After 90 days without the app using a permission, the person has to grant it again.

Can an expired Facebook token be made long-lived?

No. Meta will not turn an expired token into a long-lived one, so the person has to go through the login again before a new long-lived Page token can be read.

What does error 190 mean for a Facebook Page?

That Meta no longer accepts the token. The subcode says why, such as 460 after a password change or 492 when the person lost their role on the Page.

Does easyCoexistence refresh Facebook Page tokens?

No, because there is nothing to refresh on a schedule: the Page tokens it holds have no expiration date. It checks each Page every 6 hours instead and emails you if one needs reconnecting.

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