Facebook Pages API guide for 2026: from your app to your first post
The Facebook Pages API path in 2026 runs from a Meta app with the Manage everything on your Page use case, through Facebook Login for Business, to a Page access token read from /me/accounts and a first POST to /{page-id}/feed on Graph API v26.0. Comments, Messenger replies, webhooks and insights then run on the same Page token, each with its own permission.
easyCoexistence's Meta app holds the Page permissions, so one Facebook sign-in connects a Page, and Claude, ChatGPT or your own platform publishes, schedules, replies to comments and DMs, receives the Page's events and reads its insights through Meta's official API, with each connection checked every 6 hours and an email when it needs reconnecting.
The latest Graph API version, released July 29, 2026; v25.0 stays available until July 29, 2028.
The Page task Meta's Get Started guide asks for to publish a first post, on a published or unpublished Page.
Largest app icon Meta accepts when an app is published: 512 x 512 to 1024 x 1024 pixels, in JPEG, GIF or PNG.
How long Meta keeps Page Insights data for an unpublished Page; a public Page's is kept for 2 years.
What are the steps from a Meta app to a first post?
Five, in a fixed order, because each one needs the one before it: the app holds the permissions, the sign-in grants them, the grant produces the Page token, and the token signs the calls. Comments, Messenger, webhooks and insights come after the first post and reuse that same token. The sections below take the steps in order, then the work that follows them.
How do you create the Meta app?
In the App Dashboard: create an app, choose the Manage everything on your Page use case, then customize it to add the optional permissions you need. Ready to test marks each use case as tested, which App Review requires, and Graph API Explorer runs test queries with tokens and code samples. An app that will work on other businesses' Pages is set up as a Tech Provider under Become a Tech Provider, which adds data questions, App Review and a verified business portfolio. The full setup is on the Graph API access page.
Where does Facebook Login for Business fit?
It is how someone who runs the Page grants the app access, and Meta names it the preferred login for Tech Providers building on its business tools. Its settings take a Redirect URI, a Deauthorize Callback URL and a Data Deletion Request URL; a configuration then names the token type, the assets and the permissions, and its config_id goes in the login dialog where scope would otherwise sit. After the person approves, Facebook returns a code that your server exchanges for a user token.
Which permissions and access level does a Page app need?
One pages_ permission per kind of work, each granted at login: pages_manage_posts to publish, pages_read_engagement and pages_read_user_content to read, pages_manage_engagement to reply to comments, pages_messaging for Messenger, pages_manage_metadata for webhooks and read_insights for metrics, with pages_show_list beneath them. Standard Access covers people with a role on the app; Pages run by anyone else need Advanced Access, through App Review and Business Verification. Access Verification is no longer one of the steps, since Meta retired it for Tech Provider apps in October 2026. Each permission's dependencies are on the permissions page.
How does the app get the Page token?
From GET /me/accounts, called with a long-lived user token. The Page token follows the user token it came from: read with the short-lived token of a fresh sign-in, it expires within hours, while read with a long-lived user token, obtained on the server with fb_exchange_token, it has no expiration date. Each entry in the response gives the Page's ID and name, the person's tasks on it and that Page's own token, unique to that Page, person and app. The tokens page covers what can still end one.
How do you publish a first post?
With POST /{page-id}/feed, a message and the Page token of someone who can perform the CREATE_CONTENT task. Meta answers with the new post's ID, written {page-id}_{post-id}, and the post appears in the voice of the Page. A link field makes it a link post, and published set to false with scheduled_publish_time holds it for later. Meta's own Get Started example sends the fields as JSON:
curl -X POST "https://graph.facebook.com/v26.0/{page-id}/feed" \
-H "Content-Type: application/json" \
-d '{
"message": "Our first post through the API",
"access_token": "{page-access-token}"
}'
# {"id": "{page-id}_{post-id}"}How does the Page reply to comments?
It reads them with GET /{page-post-id}/comments and replies as the Page with POST /{comment-id}/comments and a message. The token has to come from someone who can perform the MODERATE task, or Meta leaves the comment IDs out, and replying also needs pages_manage_engagement. filter=stream returns comments at all levels in time order. A comment can also receive one private reply in Messenger, sent within 7 days of it, and is_hidden on the comment hides it or shows it again.
How does Messenger fit in?
Through the same Page token and POST /{page-id}/messages, once a person has written: their message opens a 24-hour window for replies with messaging_type RESPONSE, addressed to the Page-scoped ID that came with the webhook. The token must come from someone who can perform the MESSAGING task and carry pages_messaging. After the window, only a message tag such as HUMAN_AGENT can reach the person, and since April 27, 2026 three older tags return error 100, as the message tags page explains.
How do webhooks reach your server?
Through three pieces: an HTTPS endpoint that answers Meta's hub.challenge check, the Webhooks product in the App Dashboard set to the Page object with fields such as feed and messages, and POST /{page-id}/subscribed_apps with each Page's token, which installs the app on that Page. Meta sends nothing for a Page that has not installed the app or has turned off the App platform in its App Settings. Each event arrives signed in X-Hub-Signature-256, which your endpoint checks with the app secret.
How do you read Page insights?
With GET /{page-id}/insights, a comma-separated list of metrics and a period of day, week or days_28, using a token from someone who can perform the ANALYZE task, with read_insights and pages_read_engagement granted. Metrics that work in late 2026 include page_media_view, page_total_media_view_unique, page_post_engagements and page_follows, and one request covers at most 90 days through since and until. A public Page's data goes back 2 years.
Which limits shape the design?
A handful, set by Meta and documented with each API, and they decide how an integration queues its work:
- Pages API calls with a Page token: 4,800 per engaged user of the Page in a rolling 24 hours.
- Messenger Send API: 300 calls per second per Page for text, links, reactions and stickers, 10 for audio or video.
- Conversations API: 2 calls per second per Page.
- Scheduled posts with Meta's own
scheduled_publish_time: between 10 minutes and 30 days after the request; easyCoexistence's queue takes 1 minute to 90 days instead. - Reels: 30 published through the API in a 24-hour moving period, enforced on /{page-id}/
video_reels. - Private replies: one per comment, within 7 days of it.
What is the shorter path through easyCoexistence?
The same API with the setup already done. easyCoexistence's Meta app holds the permissions, so the person who runs the Page signs in with Facebook once, and Claude, ChatGPT or your own platform starts at the first post. Each step above maps to something that already runs:
Common mistakes
- Pinning a Graph API version near its end. v20.0 was removed on September 24, 2026 and v21.0 goes on January 21, 2027, after which its calls run on the next version up; move to v26.0 on purpose.
- Testing only with accounts that have a role on the app. In development they can grant any permission, so a flow that works for the team can fail for a customer until Advanced Access is approved.
- Requesting permissions the app will not use. Each one needs a successful call in the 30 days before App Review, and one left unused for 90 days can expire and has to be granted again.
- Passing a bare post ID. Page posts come back as {page-id}_{post-id}, and comments, edits and insights on the post take that whole value.
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
Can I build and test on an unpublished Page?
Yes. Meta's Get Started guide works on a published or unpublished Page where you can perform CREATE_CONTENT, so a hidden test Page is enough; Meta keeps an unpublished Page's insights for only 5 days.
Which Graph API version should a new Page integration use?
v26.0, the newest since July 29, 2026. Meta keeps each version working for at least two years, so pin the version in each URL and move up deliberately rather than by default.
Can one Meta app serve other businesses' Pages?
Yes, as a Tech Provider app: its permissions need Advanced Access through App Review, and the business behind the app must complete Business Verification before it reaches data other businesses own.
How much does easyCoexistence cost for a Facebook Page?
Each Page is one connection, billed at US$ 9 to US$ 0.75 per connection per month as your total grows, and the first 3 days are free, with no Meta app of your own to maintain.
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