The Muggle's Guide to the Facebook Engagement API (No Wand Required)

No need to be a wizard to get some Facebook metrics.

However, there is a part that actually needs the magic word.

If you're trying to collect Facebook engagement data in 2026, the hardest part is understanding which doors are actually open. And how. 

In this guide, you'll learn which engagement metrics are publicly available, where the official Facebook APIs stop, what changed after CrowdTangle, and when an alternative approach makes more sense than going through App Review.

The Short Version, Before You Get Sorted

If you only need the key takeaways, here's what matters.

• Facebook engagement data and Page Insights data are different things. Reactions, comments, and shares can be public, while impressions, reach, engagement rate, and audience demographics belong to Page Insights (closed territory for other eyes).
• It's a permissions gap, not an API version gap. The Facebook Graph API doesn't expose every metric simply because a newer version exists. Access depends on what data you're requesting and whether you own the Page.
• Page Insights work only for Pages you manage (and no tool changes that). Neither the official API nor Data365 API (or any other tool) can access impressions, reach, or engagement rate for Pages you don't manage. Those metrics remain private by design.
• Page Public Content Access requires App Review. Even public Page content isn't automatically available. Apps requesting access to other Pages must pass Meta's review process and meet its eligibility requirements.
• CrowdTangle is no longer available. Since August 2024, Meta has replaced it with the Meta Content Library, which is primarily available to qualified academic researchers.
• Some Page Insights metrics disappeared in 2026. On June 15, 2026, Meta deprecated another group of Page Insights metrics, making some historical integrations obsolete.
• If your goal is public engagement monitoring, there's another approach. Instead of building around App Review and permissions, services like Data365 provide structured access to public Facebook engagement data through a dedicated API.

Facebook Engagement API Basics: Before You Enter Hogwarts

Every Facebook Page exposes two fundamentally different categories of data, and mixing them up is probably the most common mistake anyone makes when looking for a Facebook engagement API.

• Engagement data is what happens in public, in front of everyone. It's the reactions under a post (Like, Love, Care (though Care reactions are folded into the Like count rather than tracked as their own bucket), Haha, Wow, Sad, and Angry): the comment count, the share count, and the likes count. If a post is public, these engagement metrics are public too. No login or registration required, no special standing, just eyes.
• Performance data tells a different story. Impressions (how many times a post was shown, whether or not anyone reacted), reach (how many unique accounts it reached), engagement rate (engagement divided by reach or impressions), and audience demographics, and other Page Insights metrics are generated inside Meta's own systems and are available only to people who manage that Page. A competitor can't see them. A researcher can't see them. And no third-party API, including Data365, can retrieve them unless the Page owner shares them manually.

Everything else in this guide follows from that distinction. Whether a Facebook metric is public or private determines whether you can access it at all, which API (if any) can provide it, and how much permission stands between you and the data.

Facebook Engagement API Limits: Spells, Rules, and Standards To Mind

Getting to engagement data isn't one door but several, each one with its own spell rulebook. Here's the list to get prepared.

Facebook Page Public Content Access: Alohomora Opens Not All Doors

Every developer looks for an Alohomora-like spell that opens every door.

Unfortunately, Facebook doesn't have one.

Many assume that if a Facebook Page is public, its content should automatically be available through the Graph API. That used to be closer to reality years ago. Today, public visibility and API access are two different things.

If you want to retrieve public posts, reactions, comments, or share counts from Pages you don't manage, you'll typically need Page Public Content Access. This permission was designed specifically for applications that analyze or monitor public Facebook content, making it one of the most requested features of the Facebook Graph API.

Getting there, however, involves much more than sending an API request. Yep, to obtain that permission means going through Meta's App Review process. 

During the review you'll need to explain exactly what data you want, why you need it, and how it benefits real users. In most cases, you'll also need Business Verification, which requires a registered business and a verified company domain (personal email addresses like @gmail.com aren't sufficient). Once approved, you'll authenticate requests using a system user access token.

Approval isn't automatic, and meeting the technical requirements doesn't guarantee access. Even if everything goes smoothly, this process rarely takes days. Depending on your use case and Meta's review timeline, it can easily stretch into several weeks.

And after all that?

You gain access to Facebook's public layer. That includes public posts, reactions (with a breakdown by reaction type), comments, share counts, Page information, and post metadata such as publication timestamps.

What you don't get is just as important.

Page Public Content Access has never been designed to expose impressions, reach, engagement rate, or any other Page Insights metrics. No level of approval opens that particular door. Those remain available only to people who manage the Page itself.

That's why many developers discover that the biggest challenge isn't writing the API request but getting permission to send it in the first place.

Meta Content Library Access: Some Sections Require Special Permissions

For eight years (2016-2024), the tool most researchers, journalists, and marketers actually used for cross-Page engagement monitoring wasn't the Graph API at all. It was CrowdTangle, a free dashboard Meta owned and ran. (More on what happened to it below.) 

When Meta retired it in 2024, many developers assumed another public monitoring tool would simply take its place.

Technically, one did.

Practically, most people never got through the door.

Its official replacement, Meta Content Library, works like the Restricted Section of the Hogwarts library: the material exists, but you need a signed note from a professor, or you need to be one yourself. The signed note here comes in the form of an academic or nonprofit affiliation, access is restricted to people doing research Meta classifies as scientific or in the public interest.

An agency running competitive analysis for a client, a marketer benchmarking industry engagement, or a local newsroom without a university affiliation — none of these qualify, no matter how legitimate or careful the actual use case is. The credential matters more than the purpose.

Facebook Page Insights API Limits: Strict Rules Nobody Can Ignore

Page Insights is the most complete engagement and performance dataset the Graph API offers, but only for Pages you already manage. To call it, your access token needs the pages_read_engagement permission, and whoever (or whatever system) sits behind that token needs the "analyze" task on that specific Page. There's no route from here to a Page you don't administer, approved app or not.

Even for your own Pages, the ground keeps shifting. 

On June 15, 2026, Meta deprecated another batch of Page Insights metrics across every API version simultaneously. Requests to those fields now return an invalid metric error, with no separate per-app warning. It's the same pattern as the metadata=1 debugging parameter, quietly removed from every Graph API version on May 19, 2026. 

Meta retires fields and shortcuts on its own schedule, and the only real defense is checking the changelog before you build anything that depends on a specific metric sticking around.

There's also a hard ceiling worth knowing before you architect anything: Page-scoped calls are rate-limited at 4,800 requests per engaged user, per 24-hour rolling window, calculated per Page. App-level calls are capped separately at roughly 200 calls per daily active user, per hour. A new integration with few users starts with almost no headroom on either count.

Facebook Engagement Metrics API: What Gringotts Won't Let You Withdraw

Gringotts is described as the safest place in the wizarding world — nobody breaks in, no exceptions. That's the right way to think about impressions and reach on a Page you don't own: it isn't a hard limit that a better tool or a bigger budget gets around. It simply isn't stored anywhere accessible to anyone but that Page's own admins.

Here's why that matters in practice. Two public posts can each receive 500 reactions, a similar number of comments, and nearly identical share counts. From the outside, they appear equally successful. In reality, one may have reached 5,000 people while the other reached 50,000. Without access to Page Insights, there's no way to see that difference.

Those metrics live on the private side of Meta's platform. 

No API, official or third-party, can extract impressions or reach for a Page it doesn't administer. Worth saying plainly, Data365 doesn't have a key to this vault either. 

That's not a limitation of any one product but just how Meta's data model works, full stop.

CrowdTangle Alternative in 2026: One More Closed Door

CrowdTangle worked like the Mirror of Erised by showing something different to whoever looked into it. 

A journalist used it to trace how a rumor spread across Pages. A marketer used it to see how a campaign's engagement stacked up against competitors'. A researcher used it to study platform-wide patterns. Same dashboard, different reflection, depending on what each person came looking for.

When Meta shut it down in August 2024, those workflows didn't disappear.

The tool did.

Unlike Harry, most CrowdTangle users never got an equivalent new home at all. That's the last gap on the official side of this guide and, as it happens, the clearest one a third-party API actually closes.

Data365 API to Get Facebook Engagement Data Without Complicated App Review (Choose Your House By Yourself)

Harry Potter never rejected Hogwarts. He simply refused to let someone else decide his path for him.

You face a similar choice.

You can build your workflow around Meta's official APIs, navigating App Review, Business Verification, permissions, and eligibility requirements. Or you can start with structured public engagement data that's already available through a different approach.

That's the idea behind Data365 API.

Instead of spending weeks navigating permissions, here's what you actually get:

• No App Review, no Business Verification, no waiting list. Sign up, get an API key, start pulling data the same day (not several weeks in).
• The same public layer Page Public Content Access is built for: reactions with a type breakdown, comments, shares, post and profile metadata, follower counts, page categories.
• Structured, unified JSON. The same response shapes whether you're pulling Facebook, Instagram, TikTok, Reddit, Threads, X (Twitter), or one of several other platforms, so you're not rewriting a parser for every source you add.
• Historical posts, not just what happens to post while you're watching. Pull a Page's public post history for a chosen date range, rather than only capturing activity from the moment your collector goes live.
• Language-agnostic by design. Plain HTTP requests, so Python, JavaScript, Go, or a no-code tool all work the same way.

One important limitation still applies.

Data365 simplifies access to Facebook's public engagement layer. It doesn't bypass any existing boundaries or expose metrics that aren't public in the first place.

Turns Out You Didn't Need Magic To Get Facebook Engagement Data in 2026

Turns out, you didn't need a spell or a wand – just the right tool.

The key is matching the solution to the data you actually need.

• If you're analyzing your own Facebook Page, Page Insights remains the only source for performance metrics like reach, impressions, and audience demographics.
• If you need public engagement data from competitor Pages and don't mind going through App Review, Page Public Content Access provides access to posts, reactions, comments, and shares.
• If you need that same public data across multiple Pages without waiting for approvals or qualifying as a researcher, Data365 offers a faster path.

The only constant is that Facebook draws a clear line between public engagement and private performance data. No API changes that boundary. The rest is simply a matter of choosing the workflow that fits your project, not chasing permissions you don't actually need.

Thus, just contact us and tell more about your project so we can provide the wand solution you actually need.