Read Public Post Comments
View all Facebook Public Data API endpoints →Provide the required post_id and an optional cursor from the same discussion. The documented discussion workflow refers to a comment-collection identifier supplied with post data, so preserve comments_id when present and validate which identifier this route accepts before bulk traversal; do not assume every post ID form is interchangeable. No response for this endpoint was sampled, so comment text, author, timestamps and result shape are not asserted here. A top_comments preview from Page posts is not a full comment collection. Respect the privacy of individuals and use bounded, permission-aware samples.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/facebook-scraper/comments API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/comments?key=<API_KEY>&post_id=<post_id>'
Query Result
Use Cases
- Collect a bounded set of public customer questions under a selected product announcement.
- Expand beyond top_comments previews before drawing conclusions about a discussion.
- Validate comments_id versus post_id handling in a small client compatibility test.
- Prepare human-led feedback annotation without republishing commenters' personal information.
Frequently asked questions
Should the comment request use post_id or comments_id?
The parameter is named post_id, but the workflow refers to a comment-collection key. Preserve comments_id from the post data and validate the identifier actually accepted before expanding collection.
Does top_comments in Page posts already contain all comments?
No. It is only a preview and cannot establish the full discussion content or total comment count.
Does a comment cursor let me read the entire discussion?
This is not guaranteed. Set a page limit, handle repeated cursors and retain public-visibility and coverage limitations.