Social Fetch
Start for freeStart free
Facebook hub

Facebook comment replies API

Expand a comment thread with nested replies — text, author, reactions, and deeper reply cursors — using the cursor from post comments.

GET /v1/facebook/posts/comments/replies

1 credit Failed requests are free

Try in playgroundFull API docs

About this endpoint

Top-level Facebook comments often stop at a reply count. The useful back-and-forth lives one level down: a buyer asking about shipping under a group listing, a brand clarifying a product claim, a neighbor naming a vendor. You already listed comments with GET /v1/facebook/posts/comments and have a non-null repliesCursor on a row. You need those nested replies as structured JSON, not another HTML scrape of the expand-thread UI.

GET /v1/facebook/posts/comments/replies takes a required cursor query param. Pass a comment's repliesCursor for the first page of that thread, or data.page.nextCursor from a previous replies response to continue. Read data.replies and data.page. Each reply can include id, text, createdAt (ISO-8601), replyCount, reactionCount, repliesCursor (string or null for a deeper nest), and an author with name, optional platformUserId, and shortName. When data.page.hasMore is true, pass data.page.nextCursor as cursor on the next call. The cursor is opaque.

This route expands replies under one comment cursor. Top-level comments for a post or Reel are GET /v1/facebook/posts/comments. Post or Reel metadata is GET /v1/facebook/posts. Bill from meta.creditsCharged.

Facebook comment replies API FAQ

How do I list Facebook comment replies via API?

Call GET /v1/facebook/posts/comments/replies with your Social Fetch API key (x-api-key) and a required cursor query param. Start from a comment's repliesCursor on GET /v1/facebook/posts/comments. Read data.replies and data.page. See the API docs for parameters and examples.

How much does the Facebook comment replies endpoint cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

Where does the cursor come from?

Use repliesCursor from a top-level comment in GET /v1/facebook/posts/comments (or from a reply that itself has a non-null repliesCursor). To paginate further under the same thread, pass data.page.nextCursor from this replies response as cursor. Missing or empty cursor fails validation.

How does pagination work on Facebook comment replies?

Each response includes data.page.nextCursor and data.page.hasMore. When hasMore is true, pass nextCursor as the cursor query param on the next request. The cursor is opaque.

What fields are in each Facebook reply?

Items can include id, text, createdAt (ISO-8601), replyCount, reactionCount, repliesCursor (string or null), and author with name, optional platformUserId, and shortName when Facebook exposes them.

Facebook comment replies vs top-level comments vs post detail?

Use this route to expand nested replies from a repliesCursor. Use GET /v1/facebook/posts/comments for top-level comments on a post or Reel. Use GET /v1/facebook/posts for the post or Reel card itself. See the Facebook platform hub for the full list.

Can a successful replies call return an empty list?

Yes. A completed lookup can return data.replies as an empty array when that page has no replies (or none were returned). You still pay the credit. If a comment has repliesCursor: null, there is nothing to expand on this route for that row.

Other Facebook endpoints