Facebook Comments API

Facebook Comments

Features

• Multi-post comment collectionCollect public comments from one or more Facebook post URLs in a single request.
• Normalized comment recordsReturn comment IDs, text, author details, timestamps, visible engagement, media, and source links in a consistent structure.
• Traceable conversation contextPreserve post, parent-comment, and submitted input references for joins, deduplication, and audit trails.
• Public data boundaryKeep private, restricted, removed, and login-only content outside the result scope.

Parameters

How to Use

Submit public Facebook post URLs as an asynchronous task, poll its task ID, then read normalized comment records with cursor pagination.

1. Prepare one or more public Facebook post URLs.
2. POST urls to /v1/facebook/comments.
3. Poll /v1/tasks/{task_id} until the status is succeeded.
4. Read /v1/tasks/{task_id}?limit=50 and follow results.next_cursor when more records exist.

curl -X POST "https://api.socq.ai/v1/facebook/comments" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.facebook.com/facebook/posts/POST_ID"]}'

# Poll GET /v1/tasks/{task_id}, then read /v1/tasks/{task_id}?limit=50 and use data.results.

Best Use Cases

• Customer feedback and sentiment analysis: Analyze public comment text to understand opinions, product feedback, questions, and recurring themes.
• Campaign content optimization: Compare comment sentiment and visible engagement across campaign posts to refine messaging and creative decisions.
• Brand conversation monitoring: Organize public comments from selected brand posts by topic, time, author, and engagement signals.
• Competitive audience research: Study public reactions on competitor posts to compare audience interests, questions, and engagement patterns.
• Audience topic discovery: Build datasets of comment text and timestamps for topic clustering, trend discovery, and language analysis.
• Engaged commenter discovery: Use author details, likes, and reply counts to identify commenters who consistently drive discussion.
• Analytics and data enrichment: Connect structured comment records with campaign, post, and analytics datasets through IDs and source URLs.

Pro Tips

• Use canonical public Facebook post URLs so each input maps cleanly to its source post.
• Group related public post URLs in one request to organize each collection task by campaign or topic.
• Save the task ID immediately after submission so your application can poll and resume the collection workflow.
• Follow results.next_cursor until it is empty to read every result page returned by the task.
• Store comment IDs, post IDs, parent comment IDs, input URLs, and source URLs with every record.
• Use comment ID to identify and merge repeated records in the same dataset.
• Use created_at and collected_at to organize comment history and incremental analysis.
• Review Raw JSON when validating field mappings or connecting results to a new data pipeline.

Related APIs