Skip to content
truescrape
Free key

How Do You Read Public Facebook Page Posts?

The official Graph API path is gated behind App Review and business verification, CrowdTangle is gone, and its replacement is researchers-only. Here is what each route actually requires, and what a public, logged-out read can get.

9 min read · 16 Oct 2026

Reading a Facebook Page's own posts sounds like it should be the easiest thing the Graph API does, and for a Page you manage it is. Reading Pages you don't manage is where every official route runs into a gate: the Graph API needs a formal review and business verification, the tool researchers used for a decade was shut down, and its replacement is limited to vetted academics. For a normal developer, the realistic path is the public, logged-out Page — which the law treats more favorably than most people expect, and the terms still tell you not to.

Here is each route and exactly what it costs you.

The Graph API, for Pages you manage

If you administer a Page, the Graph API gives you its posts directly. You use a Page access token for a Page you own, request the /feed or /posts edge, and you get the posts with their engagement. This is the intended, fully supported path, and nothing below applies to it. The friction only starts when the Page is not yours.

The Graph API, for Pages you don't manage

To read posts and engagement on Pages you don't administer, Meta requires a specific feature, Page Public Content Access, which lets an app "read public data for Pages" and "analyze and/or display posts and engagement on Pages." It is not something you can just switch on. Meta's documentation states that it "requires successful completion of the App Review process before your app can access live data," and that it "is only available with business verification."

So the official answer to "read any public Page via the API" is: submit your app for review, pass business verification, and get the feature approved. That is a real process with real rejection, aimed at established products, not a quick integration.

This gate is not new. After Cambridge Analytica, Meta announced on April 4, 2018 that "all future access to the Pages API will need to be approved by Facebook." Open Pages-API access ended that day; everything since has been review-gated.

The tool everyone used is gone

For years the practical answer to "monitor public Pages" was CrowdTangle, Meta's own public-content tool. Meta shut CrowdTangle down on August 14, 2024. In its place Meta offers the Meta Content Library, but access is narrow: it is restricted to vetted researchers whose organization operates "as a not-for-profit entity" and holds "scientific or public interest research" purposes, and applications are independently reviewed. A product company monitoring Pages for a commercial reason does not qualify.

So the two "official, for other people's Pages" routes are: pass Graph API App Review plus business verification, or be an approved academic researcher. Neither fits most builders.

What a public, logged-out read can get — and the law around it

A public Facebook Page renders its recent posts to anyone, signed in or not. That is the surface left for everyone who isn't approved for the Graph feature or the Content Library. Two things are worth being precise about.

First, the law here moved in favor of public, logged-out reads. In Meta Platforms v. Bright Data (N.D. Cal., January 23, 2024), the court granted Bright Data summary judgment on Meta's breach-of-contract claim, reasoning that a logged-off scraper "stands in the same shoes as a visitor to whom the Terms cannot apply as a matter of basic contract law" — because Facebook's terms bind account holders' use, and a logged-out collector is not using an account. Meta later dropped the case. Important nuance: this was a contract ruling turning on being logged out, not a blanket "all scraping is legal" — a separate tortious-interference theory remained in play, and the holding is specific to public, logged-off collection.

Second, Facebook's robots.txt states that "collection of data on Facebook through automated means is prohibited unless you have express written permission from Facebook." Robots.txt is not a law, but it is Meta's stated position, and it is why the only defensible version of this is reading genuinely public content while logged out, not touching anything that needs an account, and staying off personal profiles. Reddit's public data sits in a similar place — reachable without the paid API, but with its own gates and gaps.

What a public Page actually exposes, logged out

Logged out, Facebook server-renders only the head of a Page's feed — the newest one to three posts — and loads the rest behind an authenticated scroll. So a logged-out read gets the most recent posts (text, reaction/comment/share counts, timestamps), not the Page's full history. That is a real limit, not a bug: the history is simply not served to a signed-out visitor in one request.

TrueScrape reads that public surface. The /v1/facebook/ad-library/page-ads and organic Page endpoints read what Facebook serves logged out; /v1/facebook/page-posts returns a Page's recent public posts newest-first, three per page, and hands back a cursor so you can page forward through them. No account, no login, no personal profiles.

curl "https://api.truescrape.com/v1/facebook/page-posts?url=https://www.facebook.com/SomePublicPage" \
  -H "x-api-key: YOUR_KEY"

The honest summary: for a Page you own, use the Graph API. For Pages you don't, the official routes are gated behind review, verification, or researcher status, CrowdTangle is gone, and what's left for everyone else is the public, logged-out Page — defensible to read as public data, limited to what Facebook actually serves a signed-out visitor, and best kept strictly to that.

Sources

Referenced in this post

Everything described here runs on the same API. You are never charged for a failed request, an empty result, or a cache hit.

Get a free keyAll posts