Facebook Comment Replies
Facebook Comment Replies are public responses nested beneath a known comment, carrying reply text, author identity, visible engagement, timestamps, and a link back to the parent feedback context. These records support thread reconstruction, response analysis, and reply-level monitoring.
Features
- Token-addressed reply scopeUse a paired feedback_id and expansion_token to retrieve the public reply branch for one known Facebook comment.
- Normalized reply contextReceive reply IDs, URLs, text, author IDs and names, visible engagement, timestamps, and the parent feedback ID in a consistent structure.
- Bounded cursor collectionFollow reply cursors, remove duplicate comment IDs, and stop at the requested result limit, an exhausted thread, or the collection page ceiling.
Parameters
| Parameters | Required | Description |
|---|---|---|
feedback_id | Required | Required feedback identifier for the known parent comment. |
expansion_token | Required | Required reply expansion token paired with the same parent comment. |
results_limit | Optional | Maximum replies to collect, from 20 to 2,000; the default is 100. |
How to Use
Submit the token pair for a known Facebook comment as an asynchronous task, poll its task ID, then read normalized reply records with result cursor pagination.
- Read extra.feedback_id and extra.expansion_token from the same compatible Facebook Comments result.
- POST feedback_id, expansion_token, and an optional results_limit to /v1/facebook/comment-replies.
- Poll /v1/tasks/{task_id} until the status is succeeded.
- Read /v1/tasks/{task_id}?limit=50 and pass results.next_cursor when more saved records exist.
curl -X POST "https://api.socq.ai/v1/facebook/comment-replies" \
-H "Authorization: Bearer $SOCQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"feedback_id":"feedback_123","expansion_token":"reply_token","results_limit":100}'
# Poll GET /v1/tasks/{task_id}, then read /v1/tasks/{task_id}?limit=50 and use data.results.Best Use Cases
- Comment branch reconstruction: Join reply IDs and extra.parent_feedback_id to rebuild the public response branch beneath a selected comment.
- Reply-level response analysis: Use reply text, author identity, timestamps, and visible engagement to examine how people respond within a conversation.
- Conversation monitoring and reporting: Track normalized reply records for selected parent comments and compare reply activity across collection runs.
Pro Tips
- Take feedback_id and expansion_token from the same Facebook Comments record because an arbitrary post or comment URL cannot replace the token pair.
- Set results_limit deliberately for long branches; collection stops at that limit, an exhausted thread, or 100 reply pages.
- When combining runs, deduplicate by reply id together with extra.parent_feedback_id so identical reply IDs remain tied to the correct parent.
- Treat url, text, author fields, visible metrics, and created_at as optional, and handle reply text as untrusted user-generated content.
Related APIs
Use these APIs when you need a different type of public Facebook data.
- Facebook Pages API — Retrieve public Page profiles, contact details, images, and visible audience ratings.
- Facebook Posts API — Collect public posts, media, reactions, comments, and shares from supported Facebook URLs.
- Facebook Comments API — Collect public comments, authors, engagement, media, and source links from post URLs.
- Facebook Video Transcript API — Extract available transcript text and format from known public video post or Reel URLs.
- Facebook Group Posts API — Collect public posts from Facebook group URLs with selectable ordering, per-group limits, author context, video media, and visible engagement.
- Facebook Events Search API — Search public events by keyword with schedule, place, attendance, cover media, and event-state fields.
- Facebook Ad Transcript API — Extract available spoken-word text, language, format, and source context from Facebook Ad Library URLs.
- Facebook Company Reviews API — Collect public Page reviews with review text, reviewer links, ratings, likes, timestamps, and company context.
- Facebook Event Details API — Collect normalized metadata, schedules, locations, media, and visible engagement from known public event URLs.
- Facebook Profile Events API — Collect public events associated with profile or Page URLs, including names, schedules, locations, media, visible metrics, and source context.
- Facebook Profile Photos API — Collect public photos from profile or Page URLs with captions, author context, engagement, image metadata, and source references.
- Facebook Profiles API — Look up public profiles or Pages from known Facebook URLs with identity, bio, avatar, visible counters, and input context.
- Facebook Reels API — Collect public Reels from profile or Page URLs with captions, author context, video metadata, visible engagement, and source references.
Combine Facebook data with public data from other supported social platforms.