Facebook Post Comments Scraper

Scrape public comments from any Facebook post or reel URL into clean, structured JSON. Give the actor one or more post URLs and it returns one record per comment — author name, comment text, timestamp, reaction count, and reply count — with no login, no cookies, and no browser session to manage.

Built for social listening, audience research, sentiment analysis, brand monitoring, and AI-agent workflows that need structured public Facebook comment data on demand.

What it extracts

Each dataset item is a single comment:

Field	Description
postUrl	The Facebook post/reel the comment belongs to
commentId	Provider-encoded comment identifier
text	The comment body
authorName	Display name of the commenter
authorId	Encoded Facebook user ID of the commenter
authorGender	Author gender when exposed (MALE / FEMALE)
createdAt	ISO 8601 timestamp of the comment
replyCount	Number of replies to the comment
reactionCount	Total reactions on the comment
reactions	Per-type breakdown (like, love, haha, …) — only when enabled
scrapeSource	Which data backend returned the comment
scrapedAt	ISO 8601 timestamp of extraction

When to use it

• Pull the comment thread under a specific post, reel, ad creative, or viral video.
• Run sentiment or theme analysis over real audience reactions.
• Feed a Claude / GPT agent structured public comment data via Apify MCP.

Do not use it for page/profile feeds, post captions, or follower lists — give it the URL of a single post or reel. For post captions and engagement totals use the Facebook Posts Scraper. For ad creatives use the Facebook Ad Library Scraper.

Input

{
  "postUrls": [
    "https://www.facebook.com/reel/753347914167361",
    "https://www.facebook.com/NASA/posts/10159744600446772"
  ],
  "maxComments": 200,
  "maxCommentsPerPost": 1000,
  "includeReactionBreakdown": false,
  "provider": "auto"
}

postUrls accepts plain URL strings or { "url": "..." } objects. maxComments is your global cost cap; maxCommentsPerPost balances coverage across many posts within that cap.

Output

{
  "postUrl": "https://www.facebook.com/reel/753347914167361",
  "commentId": "Y29tbWVudDoxMjM=",
  "text": "This is incredible, thanks for sharing!",
  "authorName": "Jane Doe",
  "authorId": "100001",
  "createdAt": "2026-06-01T12:30:00.000Z",
  "replyCount": 4,
  "reactionCount": 27,
  "scrapeSource": "scrapecreators",
  "scrapedAt": "2026-06-26T00:00:00.000Z"
}

A machine-readable run summary (OUTPUT key) reports outcome, totalComments, posts, blockedPosts, emptyPosts, providerUsage, event-charge counts, and cost totals. RUN_SUMMARY includes provider attempts, validation errors, storage IDs, and detailed diagnostics.

How it works

The actor is provider-backed. Public Facebook comments are login-gated for raw HTTP, so this actor reads them through managed data providers (ScrapeCreators, with SociaVault as automatic fallback) that return clean public-comment JSON. It paginates through each post's comment cursor until maxComments is reached. There is no proxy to configure and nothing to log in to — the provider keys are pre-configured by the actor owner.

If a post is private, deleted, age-gated, or has comments turned off, it is reported in the run summary rather than crashing the run. If every post fails at the provider, the run fails honestly with a clear message instead of returning a silent empty dataset.

Pricing

Pay-per-event:

• Actor start — $0.00005 per run
• Comment scraped — $0.003 per comment written to the dataset

You are charged for comments actually returned, plus Apify platform usage under Pay per event + usage. Use maxComments to cap comment event spend exactly; platform usage is reported separately by Apify.

Use with AI agents (MCP)

This actor is MCP-ready. Connect it through Apify MCP and an agent can call it with a single post URL and receive structured comment JSON, ideal for sentiment summaries and audience-reaction analysis.

FAQ

Do I need a Facebook login or cookies? No. The actor reads only public comments via managed providers.

Does it scrape replies to comments? v1 returns top-level comments with a replyCount. Nested reply text is on the roadmap.

Why did a post return no comments? It is likely private, deleted, age-gated, has comments disabled, or genuinely has none. Check the OUTPUT summary's blockedPosts vs emptyPosts.

Legal

Use this actor only to collect publicly available data and in compliance with Facebook's terms, applicable laws (including GDPR/CCPA), and the rights of data subjects. You are responsible for how you use scraped data. This actor does not access private, login-gated, or non-public content.