Skip to content

Facebook Comments API

The Facebook Comments API brings Facebook Page comment management into a SaaS product, agency workflow, support tool, or automation through one API.

List Comments request
curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=facebook&accountId=acc_fb_page_456&postId=123456789_987654321&limit=25" \
  -H "x-access-key: your-api-key"
Illustrative request
Example line 1

curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=facebook&accountId=acc_fb_page_456&postId=123456789_987…

Illustrative request
Example line 2

-H "x-access-key: your-api-key"

Use it to list comments, reply to a comment or post a new top-level comment, and delete comments on Facebook Page posts, including existing posts that were not created through the API.

Facebook Comments API overview and supported operations

This API is intended for developers building Facebook Page comment management into their own systems. It supports three operations on connected Pages: retrieving comments along with their first-level replies, adding either a top-level comment or a reply to an existing comment, and removing a comment. Because Page selection happens once during connection, each later request simply references that Page through accountId. That structure fits comment inboxes, community-management dashboards, support workflows, and automations that should inspect a thread before taking action.

Connect a Facebook Page and choose the right operation

Begin by obtaining an API key and connecting the Facebook Page accounts your users intend to manage. Each Page you select becomes a separate integration with its own accountId, so any workflow spanning multiple Pages needs to keep the intended Page's accountId alongside the postId or commentId it targets. After connection, integrate through REST calls or the SDK and tooling options suited to your stack, including no-code and AI-agent workflows where applicable. A sensible sequence is to list comments first to confirm the correct Page, post, and comment IDs, then create or reply, and delete only when cleanup is intended, checking the target comment ID in the list response before sending the delete request.

Origin-modular HTTP examples with exact source paths

The List Comments request and response example shows the exact request shape and the fields returned for each comment and its first-level replies. The Create Comment or Reply to Comment example shows the same-endpoint switch between postId for a top-level comment and commentId for a reply, and the Delete Comment example shows deletion by comment ID. Keep the platform value set to facebook and pass the connected Page accountId on every operation so the request is scoped to the intended Page.

Pagination, existing posts, and Page selection

Paging is cursor-based rather than page-number-based. A list request returns 25 comments by default, and limit can be set to any value from 1 through 100. When a response contains nextCursor, pass that value as the after parameter to fetch the next page, and stop when no further cursor is returned. For existing posts, supply the identifier Facebook itself assigned to the post as postId, alongside the connected Page's accountId; nothing requires the post to have been created through this API. Before replying or deleting, confirm from the list response that the commentId belongs to the expected post and Page, because the create/reply and delete operations act directly on the IDs you supply.

Failure matrix and unsupported actions

Choose list when you need the current thread, author, timestamp, like count, hidden flag, or first-level replies before deciding what to do next. Choose create or reply when you need to add a top-level comment with postId or respond to a specific comment with commentId. Choose delete when a comment needs to be removed, for example for spam or abuse cleanup, and verify the commentId first. Hide and unhide are not available for Facebook through this API; that action is documented for Instagram only, so do not build a Facebook moderation flow that depends on hiding or unhiding comments.

Permissions and OAuth scope

The source states that the underlying integration is approved for pages_read_user_content and pages_manage_engagement and runs the OAuth flow, so the implementer does not need a separate Meta App Review for this scope. Treat that as a source-stated claim to verify against current official documentation before publication rather than as a universal guarantee, since platform permissions and review requirements can change.

Frequently asked questions

Facebook comment management works with connected Facebook Pages, with each selected Page stored as its own integration and identified by its own accountId. Listing returns comments with first-level replies, author information, timestamps, like counts, and the pagination cursor. Creating uses postId for a top-level comment and commentId for a reply on the same endpoint, while deletion uses the comment ID in the path with platform and accountId. Existing posts can be managed using the Facebook platform post ID, and support or community teams can build inboxes, dashboards, and support workflows on top of these operations.

Field map and input contract for list, create/reply, and delete
OperationMethod and pathRequired parameters / fieldsOptional parametersResponse fields / status supplied
List commentsGET /v1/comments/platform=facebook; accountId; postIdlimit (default 25, range 1-100); after (previous nextCursor)Status 202 in captured sample; success; comments[].id, text, author.id, author.name, timestamp, likeCount, hidden, replies[]; nextCursor
Create commentPOST /v1/comments/platform (required, enum including facebook); accountId (required); text (required, length>=1); postId (provide either postId or commentId)commentId not used for top-level creationNot fully supplied in captured page; held
Reply to commentPOST /v1/comments/platform (required, enum including facebook); accountId (required); text (required, length>=1); commentId (provide either postId or commentId)postId not used for a replyNot fully supplied in captured page; held
Delete commentsDELETE /v1/comments/{commentId}commentId in path; platform=facebook; accountIdNone suppliedNot fully supplied in captured page; held

POST body requiredness is supplied by cross-page exact createComment contract; POST/DELETE response status/body and error contracts remain held in private notes. List status 202 is from the captured sample.

Failure and edge-case matrix
SituationWhat to doCheck before sending
Neither postId nor commentId supplied on POST /v1/comments/Stop; the create/reply choice cannot be determinedSupply exactly the identifier for the intended action: postId for top-level, commentId for reply
Wrong Page accountIdStop and select the connected Page for the target postConfirm accountId matches the Page that owns the postId or commentId
limit outside 1-100Adjust limit; default is 25Keep limit within 1-100 and use after with the returned nextCursor for the next page
Post was not created through the APIProceed using the Facebook platform post ID as postId with the connected Page accountIdConfirm the ID is the platform post ID, not an API-generated post ID
Hide/unhide needed for FacebookDo not use this API for that action; it is documented for Instagram onlyUse listing, creating, replying, and deleting for Facebook comment management
Delete requestedVerify the target first, then delete by commentIdConfirm commentId, platform=facebook, and accountId from the list response

Failure checks are implementation guidance derived from the supplied contract; no error status/body contract was supplied, so none is asserted.

Frequently asked questions

What type of Facebook account is required for comment management?

Connect Facebook Pages rather than personal profiles. Every Page you select becomes a separate integration, identified in requests by its own accountId.

Can I list comments and replies on a Facebook Page post?

Yes. Calling GET /v1/comments/ for a Page post returns its comments, each carrying author details, a timestamp, a like count, and any first-level replies, plus a cursor for further pages.

How does Facebook comment pagination work?

Unless you specify limit, a request returns 25 comments; limit may be set anywhere from 1 through 100. Feed the nextCursor from one response into the after parameter of the next request to continue paging.

Can I create a Facebook Page comment or reply to an existing comment?

Yes. Send POST /v1/comments/ with postId when the comment should sit directly on the post, or with commentId when it should answer an existing comment. One of those two identifiers is needed, along with platform, accountId, and text.

Can I delete Facebook Page comments through the API?

Yes. Call DELETE /v1/comments/{commentId}, passing platform=facebook and the accountId of the connected Page that owns the comment.

Can I hide or unhide Facebook comments through this API?

No. Hiding and unhiding are documented only for Instagram. For Facebook, the supported moderation actions are listing, creating, replying, and deleting.

Can I manage comments on existing Facebook Page posts?

Yes. Supply the identifier Facebook itself assigned to the post as postId, alongside the connected Page's accountId. Nothing requires the post to have been created through this API.

Can support or community teams use the Facebook Comments API for Page engagement?

Yes. The operations suit comment inboxes, community dashboards, and support queues that need to read threads, answer people, and remove unwanted comments.

List Comments response
{"success": true, "comments": [{"id": "987654321001", "text": "An example comment.", "author": {"id": "102030405060", "name": "Priya Anand"}, "timestamp": "2026-08-05T14:22:10Z", "likeCount": 3, "hidden": false, "replies": [{"id": "987654321002", "text": "An example comment.", "author": {"id": "123456789", "name": "Your Page"}, "timestamp": "2026-08-05T14:31:04Z", "likeCount": 1}]}], "nextCursor": "QVFIUlZ..."}
Create a Facebook Page comment and reply to an existing comment
curl -X POST "{{API_BASE_URL}}/v1/comments/" \
  -H "x-access-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "platform": "facebook",
  "accountId": "acc_fb_page_456",
  "postId": "123456789_987654321",
  "text": "An example comment."
}'

curl -X POST "{{API_BASE_URL}}/v1/comments/" \
  -H "x-access-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "platform": "facebook",
  "accountId": "acc_fb_page_456",
  "commentId": "987654321001",
  "text": "An example comment."
}'
Delete Comment request
# Template: DELETE /v1/comments/{commentId} — the value below instantiates {commentId}
curl -X DELETE "{{API_BASE_URL}}/v1/comments/987654321001?platform=facebook&accountId=acc_fb_page_456" \
  -H "x-access-key: your-api-key"