
Pages API guide
Facebook Page API: Page Access Tokens, Permissions and a Simpler Way to Connect Pages
Page access tokens, Page tasks, pages_* permissions and App Review in 2026, and how a SaaS app can connect the Pages its users manage.
GET
graph.facebook.com/me/accounts?fields=id,name,tasks,access_token Northwind Bakery
Page · full control
access_token: {PAGE_ACCESS_TOKEN_1}
CREATE_CONTENTMODERATEMESSAGINGANALYZEADVERTISEMANAGE
Harbor Yoga
Page · partial access
access_token: {PAGE_ACCESS_TOKEN_2}
ANALYZEMESSAGING
Requires
pages_show_list
Facebook Login for Business
App Review for customer Pages
TOKEN
One Page token per Page, admin and app
Table of Contents
Short answer
The Facebook Page API (Meta calls it the Facebook Pages API) is a set of Graph API endpoints to manage a Facebook Page: publish and read posts, moderate comments, read insights and handle Page conversations. Every call needs a Page access token, obtained from a person who can perform tasks on the Page. For your own Pages, managed by people with a role on your app, no App Review is needed; serving your customers' Pages takes an app that passed App Review.
For a SaaS serving many customers, there is a second model: users connect Facebook accounts through Unipile and their Pages come with the connection.
With Unipile
Your users' Pages, without a Page token to manage
Connect. Your user links their Facebook account through Hosted Auth and their Pages come with it. No Meta app, no App Review.
List the Pages. Call
GET /v2/{ACCOUNT_ID}/inboxeswith yourX-API-KEY: each Page is an inboxPAGE_<page_id>_INBOX.Act as the Page. Reply with
POST /v2/{ACCOUNT_ID}/chats/{CHAT_ID}/messages/send, or publish as the Page withpost_as.
Definition
What Is the Facebook Page API?
It is the part of the Graph API built around the Page node: endpoints that read and change a Page, its posts, comments and metrics. Messaging runs on the Messenger Platform and ads on the Marketing API, with the same Page access token.
Despite the name, the Graph API is not GraphQL. It is a versioned HTTP API at graph.facebook.com, organized in nodes, edges and fields. For the wider picture (Login, Messenger, versions, rate limits), see how the Facebook APIs fit together.
Page detailsRead and update Page details and settings
GET / POST /{page-id}pages_manage_metadata · MANAGEPostsPublish, read, edit and delete posts as the Page
POST /{page-id}/feedpages_manage_posts · CREATE_CONTENTCommentsRead, answer and delete comments on Page posts (comments API guide)
GET / POST /{post-id}/commentspages_read_user_content, pages_manage_engagement · MODERATEInsightsPage and post metrics
GET /{page-id}/insightsread_insights, pages_read_engagement · ANALYZEConversationsThe Page inbox, through the Messenger Platform
GET /{page-id}/conversationspages_messaging · MESSAGINGWebhooksReal time events on the Page feed and inbox, once your app is installed on the Page through its subscribed_apps edge
POST /{page-id}/subscribed_appspages_manage_metadata, pages_show_listFacebook Pages API rate limits
Calls made with a Page access token fall under Meta's Business Use Case limits, counted per Page: 4,800 calls times the number of engaged users over 24 hours, engaged users being people who interacted with the Page in that window. Each response carries an X-Business-Use-Case-Usage header with your current usage. Limits for the other Facebook APIs are in our Facebook API guide.
Sources: Meta's Pages API overview, Manage a Page, Page Insights, Webhooks for Pages, Posts, Comments, Page conversations, subscribed_apps, rate limiting and permissions reference. Last verified: November 17, 2026.
Access token
How to Get a Facebook Page Access Token
There is no Facebook Page API key. A Page admin logs in to your Meta app with Facebook Login for Business, which gives you a user access token. Then GET /me/accounts returns every Page they manage, with their tasks and a Page access token for each.
1
Create a Meta app
On Meta for Developers, with the "Manage everything on your Page" use case.
App ID + App Secret2
Add Facebook Login for Business
Request pages_show_list and what your features need.
3
Get a user access token
Short lived; exchange it server side (fb_exchange_token) for a long lived one.
4
Call /me/accounts
Each Page returns its ID, tasks and token.
GET /me/accountsMeta: "Page access tokens are unique to each Page, admin, and app combination." Ten customer Pages, ten tokens to store and watch.
The exchange call and the /me/accounts request are ready to copy in the "Meta token exchange" tab of the code block below. User, app and system user tokens are covered in our guide to the Facebook API access token.
Get a Page access token in the Graph API Explorer
To test on a Page you manage, without writing code:
- Pick your app in the app menu of the Graph API Explorer, and add
pages_show_listplus the permissions you want to test. - Open the "User or Page" menu, choose your Page and generate the token: the Explorer asks you to grant the permissions.
- Copy the token shown at the top of the tool. It is short lived: exchange it as in step 3 for a Page token that does not expire.
How long does a Facebook Page access token last?
It depends on the user token you start from. A Page token obtained with a short lived user token lasts about one hour. Exchange the user token for a long lived one first, call /me/accounts again, and Meta says the Page token you get has no expiration date, though it can still be invalidated.
Short lived user tokenAbout one to two hours
Long lived user tokenAbout 60 days
Page token from a short lived user token"Valid for 1 hour"
Page token from a long lived user token"Do not have an expiration date", but can be invalidated
Sources: Meta's Access Tokens, Long-Lived Access Tokens and Get a Page Access Token; Graph API Explorer steps from its guide. Meta adds: "Do not depend on these lifetimes remaining the same." Last verified: November 17, 2026.
Can a Facebook Page access token never expire?
Yes. A long lived Page access token, obtained by calling /me/accounts with a long lived user token, has no expiration date. In Meta's words, long lived Page access tokens "only expire or are invalidated under certain conditions." That is the "permanent" Page token most guides refer to. It is not eternal, though: the events below still invalidate it, so store it, watch for errors and plan a reconnect flow. For Pages owned by your own business, a system user token is the other option.
What breaks a Page token in production
- The admin loses their role on the Page. Meta only issues Page tokens to people with a role on the Page; get a new token from another admin.
- The admin logs out of your app, changes their password or removes your app. They must log in again.
- Your app loses a permission. Access then stops for every customer at once.
Meta reports these cases as error 190. Its subcodes and how to check a token with debug_token are detailed in our Facebook API access token guide; for a Page token, the fix is always the same: ask the admin to reconnect.
Permissions
Page Tasks and Permissions: Who Can Do What
A call succeeds only if the person behind the token can perform the matching task on the Page, and your app holds the matching permission, with Advanced Access for people outside your app.
The 8 Page tasks
Tasks are what a person may do on a Page. /me/accounts lists them per Page; an admin can perform all of them.
ADVERTISECreate ads and unpublished Page posts
ANALYZEView the Page's insights and which admin published a post or comment
CREATE_CONTENTPublish content as the Page
MANAGEAssign and manage Page tasks; also needed to update Page details and settings
MANAGE_LEADSView and manage leads
MESSAGINGSend messages as the Page
MODERATERespond to and delete comments on Page posts
VIEW_MONETIZATION_INSIGHTSView monetization insights
The pages_* permissions you will request
Permissions are what your app may do. A Meta app built on the "Manage everything on your Page" use case starts with pages_show_list, business_management and public_profile. Add only what a feature uses: each permission is reviewed separately.
pages_show_listList the Pages a person manages: the Page picker after login
pages_read_engagementRead Page content, metadata, followers and insights
pages_manage_postsCreate, edit and delete Page posts
pages_manage_engagementCreate, edit and delete comments posted on the Page
pages_read_user_contentRead posts and comments by visitors on the Page, delete their comments
read_insightsRead Page insights, together with
pages_read_engagementpages_messagingManage and access Page conversations in Messenger
pages_manage_metadataSubscribe to Page webhooks and update Page settings
Reading Pages you do not manage is a different case: it takes the Page Public Content Access feature, limited by Meta to analyzing or displaying posts and engagement on Pages, with its own App Review and Business Verification.
Sources: Meta's Pages API overview (tasks), Manage a Page (MANAGE for settings), Page Insights permissions reference (descriptions, summarized) and Page Public Content Access. Last verified: November 17, 2026.
App Review
App Review: Why It Works on Your Page but Not on Your Customers' Pages
Your app starts with Standard Access, and Meta states that "permissions with Standard Access can only be requested from app users who have a role on the requesting app." Your prototype works on your Page and fails when a customer logs in. Serving their Pages takes Advanced Access, granted per permission through App Review.
1Standard Access
Your team only
Only people with a role on the app can grant permissions.
2Review
App Review
One request per permission, and a verified business.
3Advanced Access
Live for customers
Any Page admin can grant the approved permissions.
What a multi-customer SaaS has to run
Once live, every customer Page is its own small integration: an admin login, a stored token, that admin's tasks, a health check and a reconnect flow. Nothing in the Facebook Page API tracks them for you across tenants. Meta's submission guide asks for:
- A screen recording per permission, showing the user granting it and the feature using it: "Any requested permission or feature missing a screen recording will not be approved."
- A description per permission, as specific as possible.
- Access for reviewers: a public app or instructions to reach the feature.
- Only the permissions your app needs.
Meta also requires Business Verification: "Business Verification is required to get Advanced Access."
Sources: Meta's access levels, App Review submission walkthrough and Pages API overview ("All Page-related Permissions and Features require approval through the App Review process"). Last verified: November 17, 2026.
Messaging
Facebook Page Messaging: Where the Pages API Hands Off to Messenger
Page conversations are not part of the Pages API itself. They run on the Messenger Platform, with the same Page access token, the pages_messaging permission and the MESSAGING task.
People are identified by a Page-scoped ID (PSID), they write first, and the Page can answer for 24 hours after their last message. How a SaaS app reads and answers those conversations is covered on our Facebook Messenger API page. For conversations in a personal profile, see the Facebook Messenger API for personal accounts; for what Meta bills, see Facebook Messenger API pricing.
With Unipile
Another Model: Connect the Pages Your Users Manage
With Unipile, your user connects their Facebook account once, through Hosted Auth. The Pages they administer are activated on the same account_id, by default. No Meta app, no App Review, no Page token on your side.
One connection
Anna LeePersonal inbox
Northwind BakeryPage inbox
Harbor YogaPage inbox
Northwind Bakery 2Harbor YogaPersonal
Leo MartinIs the shop open on Sunday?Page
Sara KimPhoto of a cake orderPage
Omar HaddadYou: Ready at noonPage
Connection status
Personal inboxConnected
Northwind BakeryConnected
Harbor YogaNeeds attention
A problem on one Page does not affect the personal inbox or the other Pages.
GET
api.unipile.com/v2/{ACCOUNT_ID}/inboxes
200 OK
A connected Page can
- Read the messages of the Page, each Page appearing as an inbox
PAGE_<page_id>_INBOX - Reply in the Page's conversations
- Publish posts as the Page, with the
post_asparameter (Facebook post API) - Read the Page's posts
It cannot
- Start a new conversation: the person writes first
- Delete its messages (
501 api/not_implemented) - Post Stories
- Use Facebook Groups
Each Page reports its own state under metadata.products_connection_status (key page_<page_id>). The same connection carries the admin's personal messages, and the same API covers LinkedIn, WhatsApp, Instagram, Telegram, email and calendars.
The same job in code
List the Pages, then answer a Page conversation. The "Meta Graph API" tab uses a Page token, the "Meta token exchange" tab shows how to get a Page token that does not expire, and the "Unipile" tab uses the connected account.
# 1. List the Pages a person manages, with tasks and Page tokens
curl "https://graph.facebook.com/me/accounts?fields=id,name,tasks,access_token&access_token={USER_ACCESS_TOKEN}"
# Response (abridged)
{ "data": [ {
"id": "{PAGE_ID}",
"name": "Northwind Bakery",
"tasks": ["CREATE_CONTENT", "MODERATE", "MESSAGING", "ANALYZE"],
"access_token": "{PAGE_ACCESS_TOKEN}"
} ] }
# 2. Store one token per Page, then call Page endpoints with it
curl "https://graph.facebook.com/{PAGE_ID}/conversations?platform=messenger&access_token={PAGE_ACCESS_TOKEN}"
# 1. Server side: exchange the short lived user token for a long lived one
curl "https://graph.facebook.com/oauth/access_token?grant_type=fb_exchange_token&client_id={APP_ID}&client_secret={APP_SECRET}&fb_exchange_token={SHORT_LIVED_USER_TOKEN}"
# Response
{ "access_token": "{LONG_LIVED_USER_TOKEN}", "token_type": "bearer", "expires_in": 5183944 }
# 2. Call /me/accounts with the long lived user token:
# the Page tokens it returns have no expiration date
curl "https://graph.facebook.com/me/accounts?fields=id,name,tasks,access_token&access_token={LONG_LIVED_USER_TOKEN}"
# 1. List the inboxes of the connected account: one per managed Page,
# with the ID PAGE_{PAGE_ID}_INBOX
curl --request GET \
--url "https://api.unipile.com/v2/{ACCOUNT_ID}/inboxes" \
--header "X-API-KEY: {YOUR_API_KEY}"
# 2. List the chats of one Page inbox
curl --request GET \
--url "https://api.unipile.com/v2/{ACCOUNT_ID}/inboxes/PAGE_{PAGE_ID}_INBOX/chats" \
--header "X-API-KEY: {YOUR_API_KEY}"
# 3. Reply in a Page chat (chat ID PAGE_{PAGE_ID}_{THREAD_KEY})
curl --request POST \
--url "https://api.unipile.com/v2/{ACCOUNT_ID}/chats/{CHAT_ID}/messages/send" \
--header "X-API-KEY: {YOUR_API_KEY}" \
--header "content-type: application/json" \
--data '{ "text": "Yes, we open at 9am on Sunday." }'
200 OK · one Page access token per Page, admin and app
200 OK · expires_in is in seconds: about 60 days for the user token
200 OK · one account_id for the personal inbox and every Page
Meta calls checked against Long-Lived Access Tokens on November 17, 2026. Activation, inbox IDs and post_as are detailed in the Facebook Pages documentation.
Compliance
Each user connects their own account
Unipile is an independent company, not an official Meta app and not a Meta Partner. It connects on behalf of each authenticated user, and every user remains bound by Meta's terms. Use it for customer conversations on Pages your users manage.
Decision
Pages API or Connected Account: Which One Fits Your Product?
Meta's Pages API fits a team managing its own Pages, or needing insights and ads. A connected account fits a SaaS whose users bring their own Pages.
| Question | Meta Pages API | Unipile connected account |
|---|---|---|
| Who connects the Page | A Page admin, through Facebook Login for Business in your Meta app | Your user, through Hosted Auth |
| Meta app and App Review | Required, plus Advanced Access and Business Verification | Not needed on your side |
| Tokens to manage | One Page token per Page, admin and app | None: an account_id and your API key |
| Page messages | Messenger Platform, pages_messaging, 24 hour window | Read and reply; a Page cannot start a conversation |
| Publish as the Page | pages_manage_posts | post_as on the posts endpoint |
| Admin's personal account | Not available for messaging | Same connection: personal chats, posts and profile |
| Status per Page | You check each token yourself | page_<page_id> in products_connection_status |
Who connects the Page
Meta Pages APIA Page admin, through Facebook Login for Business in your Meta app
UnipileYour user, through Hosted Auth
Meta app and App Review
Meta Pages APIRequired, plus Advanced Access and Business Verification
UnipileNot needed on your side
Tokens to manage
Meta Pages APIOne Page token per Page, admin and app
UnipileNone: an
account_id and your API keyPage messages
Meta Pages APIMessenger Platform,
pages_messaging, 24 hour windowUnipileRead and reply; a Page cannot start a conversation
Publish as the Page
Meta Pages API
pages_manage_postsUnipile
post_as on the posts endpointAdmin's personal account
Meta Pages APINot available for messaging
UnipileSame connection: personal chats, posts and profile
Status per Page
Meta Pages APIYou check each token yourself
Unipile
page_<page_id> in products_connection_statusStill choosing between Login, Messenger, Marketing API and Pages? Our decision grid shows which Facebook API you need for each kind of product.
Connect Pages without a token pipeline
Let each user link their Facebook account once, and work with their Page inboxes and posts through the same API as their LinkedIn, WhatsApp and email accounts. 7-day free trial, no credit card.
EU Regulated
Digital Markets Act (DMA)
Each user connects their own account, with no profile storage. Unipile is not a Meta Partner. Learn more
All Facebook API endpoints in one place
Pages are one part of the picture. See every Facebook endpoint available with Unipile (messages, posts, comments, profiles, webhooks), or read the complete Facebook API guide.
Facebook Page API FAQ
Quick answers on the Facebook Page access token, its lifetime, App Review and permissions.
Log a Page admin in to your Meta app with Facebook Login for Business, requesting pages_show_list. Exchange the user token for a long lived one on your server with grant_type=fb_exchange_token, then call GET /me/accounts: each Page comes back with its own access_token and the tasks the admin can perform.
It depends on the user token behind it. Per Meta, a Page token obtained with a short lived user token is valid for 1 hour. Get it from a long lived user token (about 60 days) and the Page token has no expiration date, though a logout, a password change or an app removal still invalidates it.
Yes. Call /me/accounts with a long lived user token and the Page tokens returned have no expiration date. They are not permanent in every case: if the admin loses their Page role, changes their password or removes your app, the token stops working and the admin has to reconnect.
Your app only has Standard Access, so only people with a role on the app can grant it permissions. To serve customer Pages, each permission needs Advanced Access, granted through App Review with a screen recording per permission, and Meta requires Business Verification for it.
Almost every integration starts with pages_show_list. Then add only what you use: pages_read_engagement to read content and metadata, pages_manage_posts to publish, pages_manage_engagement for comments, pages_messaging for conversations, pages_manage_metadata for webhooks and settings, and read_insights for metrics.
No. Unipile is an independent company, not a Meta Partner, and Meta does not endorse, sponsor or approve it. Connecting Pages through Unipile does not make your product a Meta app either. Facebook and Messenger are trademarks of Meta Platforms, Inc.
No. Instead of a Meta app collecting Page access tokens, your users connect their Facebook account once through Unipile's hosted authentication, and the Pages they administer come with that connection. There is no App Review, Advanced Access or Business Verification to complete on your side.
It is built in the spirit of the Digital Markets Act: each Page admin connects their own account, Unipile acts on their behalf for the Pages they already manage, and it does not store user profiles. Details are on our Digital Markets Act page.
Yes. A Page connected through Unipile is still governed by Meta's Terms of Service and Page policies. Keep to legitimate uses such as answering customers in the Page inbox, publishing the Page's own content or syncing conversations to a CRM; spam and unauthorized automation can get the account or the Page restricted.
Still have questions? Our team is here to help.
Talk to an expert
