Skip to main content
jeremieseguillon
New Participant
February 9, 2026
Question

pages_read_engagement permission present in token scopes but API returns error

We are experiencing an issue where the pages_read_engagement permission is correctly granted (Advanced Access) and confirmed present in our Page Access Token scopes, yet all engagement-related endpoints return error #10.

App info:

  • App Mode: Live
  • Graph API version tested: v24.0 and v21.0 (same result)

Token verification via /debug_token:

{ "data": { "app_id": "....", "type": "PAGE", "is_valid": true, "scopes": [ "pages_show_list", "business_management", "instagram_basic", "instagram_manage_insights", "instagram_content_publish", "pages_read_engagement", "pages_manage_posts", "public_profile" ] } }

As shown above, pages_read_engagement is explicitly listed in the token scopes.

Calls that FAIL (error #10):

GET /{page_id}/posts?fields=id,likes.summary(true) GET /{post_id}/likes?summary=true GET /{post_id}/comments?summary=true

Error response:

{ "error": { "message": "(#10) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature.", "type": "OAuthException", "code": 10 } }

Calls that SUCCEED with the same token:

GET /{page_id}/posts?fields=id,message,created_time → ✅ OK GET /{page_id}?fields=followers_count,fan_count → ✅ OK GET /{page_id}/posts?fields=id,shares → ✅ OK

Steps to reproduce:

  1. Create a Page Access Token via Facebook Login for Business with config_id that includes pages_read_engagement
  2. Verify pages_read_engagement is in token scopes via /debug_token
  3. Call GET /{page_id}/posts?fields=id,likes.summary(true) with this token
  4. Observe error #10 despite the permission being present

Expected behavior: The call should succeed since pages_read_engagement is in the token scopes and granted in Advanced Access.

Actual behavior: Error #10 stating the endpoint requires pages_read_engagement — the very permission that is already granted.

Additional context:

  • The token is obtained via Facebook Login for Business (using config_id, not explicit scopes)
  • Instagram endpoints using the same token work correctly (instagram_manage_insights which depends on pages_read_engagement)
  • We have requested pages_read_user_content twice and it was rejected both times
  • The issue is reproducible across API versions (v21.0 and v24.0)

    2 replies

    cpdev
    New Participant
    February 10, 2026

    I am having the same issue. Engagement related endpoints are returning

    {"error": {"message": "(#10) This endpoint requires the 'pages_read_engagement' permission or the 'Page Public Content Access' feature. Refer to https://developers.facebook.com/docs/apps/review/login-permissions#manage-pages and https://developers.facebook.com/docs/apps/review/feature#reference-PAGES_ACCESS for details.","type": "OAuthException","code": 10}}

    I checked the scopes as well. I have pages_read_engagement. I have the app in live mode as well. And I have advanced access for pages_read_engagement meta as well.

    Were you able to figure this out jeremie.seguillon​ 

      

    DavidSchreiber1649493
    New Participant
    May 6, 2026

    Hi jeremie.seguillon​ , cp_dev​ — exact same problem here. My app is Live, pages_read_engagement is in Advanced Access, token has the permission verified via /debug_token. Yet engagement endpoints on client Pages return Error #10:

    GET /{page-id}/posts?fields=id,message,reactions.summary(true),comments.summary(true) GET /{post-id}/reactions?summary=total_count GET /{post-id}/likes?summary=true

    All fail with the standard "(#10) requires pages_read_engagement permission or Page Public Content Access feature" error.

    My best guess: pages_read_user_content is what's actually needed. Even though the docs and the error message both say pages_read_engagement is enough for reaction and comment counts on Page posts, my testing suggests otherwise.

    And here's the paradox I hit:

    I only need the counts of reactions and comments on Page posts — not the actual content. I demonstrated this clearly in my screencast: I'm just displaying numbers ("12 reactions, 3 comments") in my dashboard, never showing comment text or user identities.

    When I requested pages_read_user_content, the App Review team rejected me because my app doesn't display the actual comment content — they wanted to see comment text rendered in the UI, which is exactly what I don't need.

    So it seems like:

    • pages_read_engagement alone → Error #10, can't get counts
    • pages_read_user_content → required for counts (apparently?), but rejected because I don't display content
      Terms & ConditionsAccessibility statement