Get a Single Comment by ID
View all Facebook Public Data API endpoints →Pass a known public comment_id to request one comment directly. This documented endpoint has no sampled response; text, author, creation time and exact result shape must be checked before use. It is distinct from the nested-reply route and does not promise a reply collection. Refresh only comments relevant to a permitted review purpose; a missing or inaccessible record must be treated as unavailable, not conclusively deleted.
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/comment-by-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/comment-by-id?key=<API_KEY>&comment_id=<comment_id>'
Query Result
Use Cases
- Open a saved comment reference from an analyst review queue.
- Refresh an annotated public comment record during an authorized research audit.
- Compare a direct comment lookup with a discussion-list record after verifying identifier compatibility.
- Track unavailable comment references separately from confirmed content changes in a client dataset.
Frequently asked questions
How can I avoid collecting an entire discussion again for one comment?
Save and validate the comment_id, then request it through the single-comment endpoint. The returned fields still need validation.
Does this endpoint return all replies beneath the comment?
There is no such promise. It targets a single comment; expanding replies uses a separate endpoint and context workflow.
Does an unreadable comment mean that it was deleted or moderated?
Unavailability alone does not establish that conclusion. Visibility or a temporary read condition may be responsible.