Skip to content

Error #10 is the message most developers see when they first try to read Facebook Page data. It says the endpoint needs the “pages_read_engagement” permission or the “Page Public Content Access” feature. In February, a developer on Meta’s own community forum reported this error even though their app was live and already had the permission approved. By late October, others were still reporting the same problem on the newest version of the API, with no clear answer from Meta.

So if Facebook’s API feels confusing, you are not imagining it. The good news is that most people need less access than they think, and several official routes need no App Review at all. This guide explains what changed in Meta’s rules, how to pick the right route for your situation, why scraping usually costs more than it saves, and how to pass App Review when you really need it.

What changed in Meta’s rules

Meta releases a new Graph API version about twice a year, and each one changes something. Version 25.0 arrived on 18 February and version 26.0 on 29 July. Each version works for about two years before it expires, so code written for an old version keeps running for a while and then suddenly stops. Version 23.0, for example, expires on 8 October 2027.

Website owners felt a bigger change on 10 February, when Meta switched off the Facebook Like button and Comment button for external websites. Sites that still had them lost those features, and many WordPress themes and plugins were left with empty boxes.

Access to other people’s Pages has stayed strict. According to Meta’s developer documentation, the Page Public Content Access feature, which lets an app read public posts and comments on Pages it does not manage, needs both App Review and business verification. Until it is approved, an app can only read Pages whose admins also have a role on the app. CrowdTangle, the free monitoring tool many marketers and journalists used, was shut down in 2024. Its replacement, the Meta Content Library, is open only to not-for-profit academic and research institutions, and its approval process alone takes around four to six weeks.

Start with one question, whose Page is it?

The right route depends almost completely on who owns the Page you want data from. Most “Facebook API alternative” searches come from people in one of four situations, and each one has a different answer.

It is your own Page, or a client’s Page you manage. This is the easiest case. You do not need Page Public Content Access, because you are reading a Page you have a role on. With the Pages API, a Page access token from someone who manages the Page can read its posts and much of its data. Permissions at Standard Access level work without App Review for people who have a role on your app, so if only you and your team use the tool, add those people as app admins or developers. If you do not want to write code at all, the official Facebook Pages connections in tools such as Zapier and Make let you log in and send new posts, leads or messages to a spreadsheet, CRM or email.

You want to show your own Facebook posts on your website. Meta’s February changes removed the Like and Comment buttons, but did not include the Page Plugin, so the official embed still exists. It does load Meta’s scripts and cookies on your site, which slows pages and may need cookie consent. A cleaner option is to fetch your own posts on your server through the Pages API, store them, and show them as normal HTML on your site. That is faster, works without tracking, and keeps working if Meta changes the embed again.

You want to track competitors or other brands. For their ads, the official Meta Ad Library is free and shows the active ads of any Page, with no developer account needed. For their regular posts and engagement, you either apply for Page Public Content Access with a clear business case, or use a social listening tool that already holds approved access. Many marketing teams find the second option faster and cheaper than building their own app.

You are doing research for a university or not-for-profit. Apply for the Meta Content Library. It is free, but your institution must qualify, and applications are checked first by an independent data centre and then by Meta.

Why scraping is the expensive option

When the official routes feel slow, scraping tools look tempting. Several vendors now advertise ways to collect public Facebook data without the Graph API. Before you go that way, it helps to count the real costs.

Meta’s terms do not allow collecting data by automated means without permission, and Meta actively blocks this kind of traffic. Accounts and business assets connected to scraping can be restricted, which is a serious risk if you also run ads from the same business account. Scrapers also break whenever Facebook changes its layout, so someone has to fix them again and again. And public comments still contain personal data, so storing them can bring privacy duties under laws such as GDPR. We are not lawyers, and rules differ by country, but for most businesses the official routes are cheaper once maintenance and risk are counted.

Getting through App Review the first time

If you do need Advanced Access or Page Public Content Access, a well-prepared submission saves weeks. Meta reviewers check that your request matches what your app actually does. Rejections usually happen because something is missing or unclear, not because the use case is forbidden. These steps make approval much more likely.

  • Complete business verification before you submit, because some features cannot be approved without it
  • Request only the permissions your app uses today, and explain each one in one or two plain sentences
  • Record a screencast that shows the full flow, from logging in to the exact screen where the data appears
  • Give reviewers a working test account and step-by-step instructions to reach the feature
  • Make sure your privacy policy is public, mentions Facebook data and explains how users can ask for deletion
  • Match your description to Meta’s allowed use for the feature, such as analysing or displaying Page posts and engagement

Even with approval, test engagement counts carefully. The forum thread from the start of this article shows that likes, reactions and comment counts can still fail with error #10, so build your app to handle missing fields without breaking.

Connecting a website or system to Meta’s APIs is the kind of job we do every week. Our custom development team builds API integrations that keep working through version changes, our automation service connects Facebook leads and messages to your CRM, and our social media team can handle the reporting for you. If you only need Facebook data to measure results, our analytics setup brings it together with your website numbers.

Frequently asked questions

Can I get Facebook Page data without App Review?

Yes, for Pages you manage. Permissions at Standard Access level work without App Review for people who have a role on your app. Reading public data from Pages you do not manage needs the Page Public Content Access feature, which requires App Review and business verification.

Is the Facebook Page Plugin still available?

Meta’s February changes switched off the Like and Comment buttons for external websites but did not include the Page Plugin. It still loads Meta’s scripts and cookies, so many sites now show their posts through the Pages API instead.

What replaced CrowdTangle?

Meta replaced CrowdTangle with the Meta Content Library, which is only open to not-for-profit academic and research institutions. Businesses usually use social listening tools with approved access, or the free Meta Ad Library for competitors’ ads.

Is it legal to scrape public Facebook Pages?

It depends on your country and on what data you collect, and we cannot give legal advice. What is clear is that Meta’s terms do not allow automated collection without permission, and that scraping can put your Facebook accounts and ad accounts at risk.