Facebook Comments API
API health
- 24h health
- 85%
- 24h average time
- 31.02 s
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Pull comments on a Facebook post from its url. Each comment has author, author ID, likes, reply count, post time and permalink. Reply rows reuse the parent group's ID, so rebuild threads with depth and reply_to_id. A complete tree is not guaranteed.
Send POST https://api.everyinfra.com/api/v1/social with platform set to facebook and action set to comments. Price $2.78 per 1,000 requests ($0.002778 per call). Failed calls and empty results are not charged. Asynchronous by default: returns a job_id first; poll GET /api/v1/jobs/{job_id}.
AI prompt
#Please help me write a data collection script with the EveryInfra Facebook Comments endpoint (facebook/comments).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to facebook and action to comments, and put the parameters inside params.
- Required parameters:
- url: Specifies the target URL corresponding to the requested action. Use public Page URLs for profile and user_posts, post URLs for post and comments, group page URLs or group identifiers for group_posts, and business page UR…
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 10)
- Returns a list of records. Main fields of each record: id, text, author_name, author_username, depth (Comment level: 0 is a top-level comment…), reply_to_id (Id of the comment this row replies to (…), comment_url (Permanent link to this comment), author_id (Numeric user id of the comment author (…), author_url (Profile link of the comment author), like_count, reply_count, posted_at.
- Example request body:
{
"platform": "facebook",
"action": "comments",
"params": {
"url": "https://www.facebook.com/nasa"
}
}
- Price: $2.78 per 1,000 requests; failed and empty results are not charged.
- This endpoint is asynchronous by default: it returns 202 and a job_id, then you poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} until the status is succeeded or failed.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | facebook | Platform identifier, fixed value. |
action | body | string | Yes | comments | Capability identifier, fixed value. |
url | body.params | string | Yes | - | Specifies the target URL corresponding to the requested action. Use public Page URLs for profile and user_posts, post URLs for post and comments, group page URLs or group identifiers for group_posts, and business page URLs for reviews (which appends /reviews). Arbitrary Facebook URLs cannot be interchanged across actions. |
limit | body.params | integer (1–50) | No | 10 | The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "facebook",
"action": "comments",
"params": {
"url": "https://www.facebook.com/nasa"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "facebook", "action": "comments", "results": [ { "id": "•••", "text": "Houston, we have a Saturday. Four astronauts, one very big rocket, and zero 'just needs a little duct tape.' Go get 'em, Artemis crew. 🚀", "author_name": "•••", "author_username": "•••", "depth": 0, "comment_url": "https://www.facebook.com/reel/1803909017420449/?comment_id=1886311312779861", "author_id": "•••", "author_url": "https://www.facebook.com/•••", "like_count": 0, "posted_at": "2026-10-24T12:11:38+00:00", "platform": "facebook" }, { "id": "•••", "text": "Excited to follow the next steps toward the lunar surface! 🚀 Which Artemis III test will be most critical to preparing for the landing?", "author_name": "•••", "author_username": "•••", "depth": 0, "comment_url": "https://www.facebook.com/reel/1803909017420449/?comment_id=2063125671029513", "author_id": "•••", "like_count": 0, "posted_at": "2026-10-24T08:06:31+00:00", "platform": "facebook" } ], "count": 16, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
author_name | Author's display name. |
author_username | Author's username (@handle), usually usable in URLs. |
depth | Comment level: 0 is a top-level comment, 1 is a reply to it, 2 is a reply to a reply. Rows at depth >= 1 reuse their parent comment group id — rebuild the tree with depth + reply_to_id. When the main source is unavailable, a backup returns top-level comments only, so every row has depth 0 and there are no reply rows. |
reply_to_id | Id of the comment this row replies to (present only at depth >= 1; always null at depth 0). Reply rows reuse the parent group id as their row id, so treat this field as the parent link. |
comment_url | Permanent link to this comment; on reply rows the link carries a reply_comment_id parameter pointing at the commented row. |
author_id | Numeric user id of the comment author (stable identifier for cross-request deduplication). |
author_url | Profile link of the comment author. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Facebook Official: Public Visibility of Page Profiles, Posts, and Comments ↗
Official Meta documentation discusses public details across Pages, profiles, posts, and comments; this definition of visibility does not guarantee that every URL can be read, that every field will be returned, or that this endpoint holds Meta access authorization.
Checked 2026-09-04
- Meta Official Documentation: Automated Data Collection Requires Prior Permission ↗
Meta explicitly states that automated collection of Facebook data without prior permission violates its terms, even for publicly visible data. Citing authoritative sources does not constitute proof of authorization for platform collection or reuse.
Checked 2026-09-04