Threads Comments API
The Threads Comments API lets a SaaS product, community tool, agency workflow, or automation list and reply to Threads conversations through one unified comments endpoint.
curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=threads&accountId=acc_th_123&postId=18000000000000000&limit=25" \
-H "x-access-key: your-api-key"curl -X GET "{{API_BASE_URL}}/v1/comments/?platform=threads&accountId=acc_th_123&postId=18000000000000000&l…
-H "x-access-key: your-api-key"
Threads calls comments replies, and this API returns them in the same shape as Instagram and Facebook comments, so a team can add Threads reply management without writing a separate integration for each network.
Bring Threads reply management into your product or workflow
Bring Threads reply management into a SaaS product, community tool, agency workflow, or automation through one API. The core tasks are to List Replies on a post, Reply to Threads, and create a new top-level Threads post when the workflow calls for it. The same /v1/comments endpoint and response shape are used for Instagram and Facebook comments, which keeps moderation and engagement code reusable across platforms.
List Replies
List Replies retrieves the replies attached to a Threads post, including who wrote each one, its wording and when it appeared. Call GET /v1/comments/ with platform set to threads, your connected accountId, and the platform post identifier in postId. Results contain top-level replies, each with first-level nested replies, and the call works for any post belonging to the connected Threads account rather than only posts created through this API. The List Replies request and List Replies response examples show the exact call and payload.
Reply to Threads
Reply to Threads sends a response to a post or to a reply that already exists, in a single call. Send POST /v1/comments with the target post or reply identifier in commentId, together with accountId for the connected account and the wording you want published. Before sending, confirm commentId points at the intended target and review the wording, since the identifier you choose determines whether you are answering or starting something new. See the Reply to Threads request using commentId example, which shows only the fields captured in the source.
Create Top-Level Threads
Create Top-Level Threads starts a fresh Threads post through the Comments API. On POST /v1/comments, supplying postId instead of commentId is the documented signal for a new post, which suits scheduled community prompts or reply-and-continue threads. Choose commentId when answering an existing item and postId when starting a new top-level post. See the Create top-level Threads post request using postId example and the decision table below.
Pagination with nextCursor and after
Paging through Threads replies uses a cursor. Requests return 25 items by default, and limit can be set anywhere from 1 to 100. When nextCursor is present in a response, feed that value back as after to fetch the following page; when it is null, paging is finished. As a sanity check, confirm the after value matches the previous nextCursor exactly and that limit remains inside the 1 to 100 range.
Limitations and failure checks
Hide, unhide and delete are not available for Threads replies through this API. Those moderation controls exist only on platforms that support them, so a Threads workflow should not depend on them here. Nested replies returned by the list call go one level deep only, so deeper threading is not represented in this shape. The threads_manage_replies permission identifier is associated with reply management in the source material, and accountId identifies which connected Threads account a call applies to.
| Field | Location | Type in example | Meaning |
|---|---|---|---|
| success | Response body | boolean | Whether the request succeeded. |
| comments | Response body | array | Top-level replies for the post. |
| comments[].id | Response body | string | Reply identifier; use as commentId when replying to this reply. |
| comments[].text | Response body | string | Reply text. |
| comments[].author.id | Response body | string | Author identifier. |
| comments[].author.name | Response body | string | Author display name or handle. |
| comments[].timestamp | Response body | string | Reply timestamp in ISO 8601 format in the example. |
| comments[].likeCount | Response body | number | Like count for the reply. |
| comments[].hidden | Response body | null in example | Hidden state as returned in the example. |
| comments[].replies | Response body | array | First-level nested replies. |
| comments[].replies[].id | Response body | string | Nested reply identifier. |
| comments[].replies[].text | Response body | string | Nested reply text. |
| comments[].replies[].author.id | Response body | string | Nested reply author identifier. |
| comments[].replies[].author.name | Response body | string | Nested reply author display name or handle. |
| comments[].replies[].timestamp | Response body | string | Nested reply timestamp in ISO 8601 format in the example. |
| comments[].replies[].likeCount | Response body | number | Like count for the nested reply. |
| nextCursor | Response body | string or null | Cursor for the next page; pass as after, or stop when null. |
Types are as shown in the supplied example response; no additional schema was captured.
| Intent | Endpoint | Target field | Other fields described in source | Result |
|---|---|---|---|---|
| Reply to a post or existing reply | POST /v1/comments | commentId | accountId and the reply wording (field name not captured) | Creates a reply to the post or reply identified by commentId. |
| Create a new top-level Threads post | POST /v1/comments | postId | accountId and the post wording (field name not captured) | Creates a new Threads post instead of a reply. |
POST body field types, the field name for the published wording, requiredness and enums were not captured; only commentId, postId and accountId are listed as captured fields.
| Request parameter | Required in example | Default / range | Notes |
|---|---|---|---|
| platform | Yes in example: threads | Not stated | Set to threads for Threads replies. |
| accountId | Yes in example | Not stated | Connected Threads account identifier, for example acc_th_123. |
| postId | Yes in example | Not stated | Threads platform post ID, for example 18000000000000000. |
| limit | No in example request it is 25 | Default 25; range 1 to 100 | Controls page size. |
| after | No | Not stated | Pass the previous nextCursor value to get the next page. |
Requiredness beyond the example and FAQ description was not fully captured.
| Action or structure | Supported for Threads via this API | Notes |
|---|---|---|
| List top-level replies | Yes | GET /v1/comments/ with platform=threads. |
| List first-level nested replies | Yes | Returned inside comments[].replies. |
| Reply to a post or existing reply | Yes | POST /v1/comments with commentId. |
| Create a new top-level Threads post | Yes | POST /v1/comments with postId instead of commentId. |
| Hide a Threads reply | No | Not supported for Threads through this API. |
| Unhide a Threads reply | No | Not supported for Threads through this API. |
| Delete a Threads reply | No | Not supported for Threads through this API. |
| Deeper than first-level nested replies | No | Response shape includes first-level nested replies only. |
Based on the captured FAQ answers for this page.
Frequently asked questions
What is a comment on Threads?
On Threads the unit is called a reply, not a comment. This API surfaces those replies through the shared comments structure, so your code treats a Threads reply as the item to fetch and answer.
Can I list replies on a Threads post?
Yes. Call GET /v1/comments/ passing platform=threads plus your connected accountId and the platform post identifier in postId. Returned items cover top-level replies, each carrying its first-level nested replies.
How does Threads reply pagination work?
Paging is cursor-based. A request returns 25 items unless you set limit, which accepts 1 through 100. When a nextCursor value comes back, send that same value in after on the following request; a null nextCursor means there are no further pages.
Can I reply to a Threads post or an existing reply?
Yes. Send POST /v1/comments, placing the target post or reply identifier in commentId, alongside accountId for the connected account and the wording you want published.
Can I publish a new top-level Threads post through the Comments API?
Yes. Supplying postId rather than commentId on POST /v1/comments is the documented way to start a fresh Threads post. Reserve commentId for cases where you are answering something that already exists.
Can I hide or delete Threads replies through the Comments API?
No. Hide, unhide and delete operations for Threads replies are not offered by this API. Such moderation controls exist only on platforms that support them.
Can I read replies on existing Threads posts?
Yes. Because postId takes the platform's own post identifier, replies can be fetched for posts that already existed on the connected account, regardless of how they were originally published.
Can I build a Threads community engagement workflow with the Comments API?
Yes. Typical builds include a community inbox, an engagement dashboard, an agency queue, or automation that pulls replies and posts responses back into the conversation.
{
"success": true,
"comments": [
{
"id": "18000000000000001",
"text": "An example comment.",
"author": {
"id": "31000000000000",
"name": "sam.builds"
},
"timestamp": "2026-08-03T18:30:00Z",
"likeCount": 6,
"hidden": null,
"replies": [
{
"id": "18000000000000002",
"text": "An example comment.",
"author": {
"id": "31000000000001",
"name": "alex.builds"
},
"timestamp": "2026-08-03T18:35:00Z",
"likeCount": 2
}
]
}
],
"nextCursor": null
}curl -X POST "{{API_BASE_URL}}/v1/comments" \
-H "x-access-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platform": "threads",
"accountId": "acc_th_123",
"commentId": "18000000000000001",
"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": "threads",
"accountId": "acc_th_123",
"postId": "18000000000000000",
"text": "An example comment."
}'