Skip to content

Threads comments API: How to Manage Threads Replies in 2026

The Threads comments API manages Threads replies: reading replies under a Threads post and posting a reply under a thread or an existing reply. Threads uses the term replies rather than comments, and the /v1/comments endpoint mirrors that model for Threads. This guide covers authentication with the x-access-key header, connecting a Threads account, listing replies with GET /v1/comments, replying with POST /v1/comments, and the critical distinction between commentId and postId.

Threads comments API: replies terminology and scope

Threads does not use the word comments for the items under a post. It uses replies. When you read what people said under a Threads post, you are listing Threads replies. When you answer them, you are posting a reply. The Threads comments API therefore centers on two operations: reading replies and posting replies. As described in the source material, deleting or hiding Threads replies through this API is not supported, because the threads_delete permission is described as not approved. Plan moderation workflows around reading and replying, with manual handling in the Threads app for removal.

Prerequisites and the x-access-key header

You need an account with an access key, and a Threads account you can authorize. Every request uses the x-access-key header. Treat the access key like a password and keep it out of public code and logs. Before making comments calls, confirm you have the key value from the Access Keys page and that the Threads account you intend to use is available for authorization.

Connect your Threads account and retrieve accountId

Start by calling the connect endpoint for Threads with your x-access-key header. The response provides an authorization URL. Open that URL, authorize the app, and link your Threads account. The Meta scope described for this flow is threads_manage_replies, which covers reading and posting replies. After authorization, call the integrations endpoint with the same header and find the connected account entry. Its id value is the accountId you pass in every comments call. If you prefer a dashboard flow, the same connection can be completed from the integrations dashboard, but the accountId retrieval step remains the same.

List replies with GET /v1/comments

Reading replies is a GET request to /v1/comments with platform set to threads. Pass accountId for the connected Threads account and postId for the thread you want to read. The limit parameter controls how many items are returned, ranging from 1 to 100 with a default of 25. The response contains top-level replies and the first level of nested replies under each one. Each reply includes id, text, author, timestamp, and likeCount, and top-level replies may also include hidden and a replies array. When more results are available, the response includes nextCursor. Pass that value back as the after parameter on the next request to continue paging. See the example titled List Threads replies with GET /v1/comments and the example titled Example list replies response for the exact request and response shapes.

Reply to a thread with POST /v1/comments

To post a reply, send a POST request to /v1/comments with platform set to threads, your accountId, the commentId of the item you are replying to, and the text of your reply. Use an id returned by the list call as commentId so your reply lands under that specific thread or existing reply. A successful response returns success set to true and the commentId of the reply you just created. Store that returned commentId if you need to reference the new reply later. See the example titled Reply to a Threads reply with POST /v1/comments and the example titled Example reply response.

commentId versus postId on Threads

The choice between commentId and postId changes what the POST creates on Threads. Sending commentId replies under an existing thread or reply, which is the pattern for staying in a conversation. Sending postId on Threads creates a brand new top-level Threads post, because Threads has no standalone top-level comment separate from the post itself. This differs from Instagram and Facebook behavior described in the source, where POSTing with postId adds a top-level comment to that post. For an answer to an existing item, choose commentId. Reserve postId for cases where publishing a fresh post is the actual goal. See the decision table titled commentId versus postId on Threads.

Limitations: delete and hide not supported

Threads replies cannot be deleted or hidden through this API, as described in the source material. The threads_delete permission that would allow delete and hide is described as not approved by Meta, so no third party can offer those operations for Threads. Attempts to remove or conceal a Threads reply through DELETE or hide operations will not succeed. Reading replies with GET and posting replies with POST using commentId are the two supported operations. Build moderation logic around that limit and handle removal manually in the Threads app when needed. See the limitation matrix titled Threads replies operations and limitations.

Cost note

The source states that each comments endpoint call consumes 1 credit, matching the per-endpoint cost described there. Listing replies and posting a reply each count as one call, so plan polling frequency and reply volume around your credit budget. Treat this as a source-stated cost note to verify against current pricing before relying on it for budgeting.

Worked example and next steps

You now have the two moves Threads gives you: pull Threads replies with GET /v1/comments and answer them with POST /v1/comments plus a commentId. Avoid postId in reply workflows, since it publishes a fresh thread instead, and keep in mind that removal and concealment are unavailable for Threads replies. The worked example below chains a list response id into a reply request. For publishing new Threads posts, use the separate posting flow described in how to post on Threads with an API. For a no-code look at the same flow, the Threads reply manager presents the API behind a UI.

Field map for GET /v1/comments and POST /v1/comments
FieldUsed inType as shown in source examplesRequiredness as supported by sourcePurpose
platformGET /v1/comments query; POST /v1/comments bodystring, value threads in examplesShown in both examplesSelects Threads for the comments endpoint
accountIdGET /v1/comments query; POST /v1/comments bodystring, example your-threads-idShown in both examples; retrieved from integrations idIdentifies the connected Threads account
postIdGET /v1/comments query; POST /v1/comments bodystring, example THREAD_IDShown in GET example; in POST it creates a new top-level post on ThreadsIdentifies the thread to read, or a new post to create on POST
commentIdPOST /v1/comments body; returned in POST responsestring, example 17901234567890123Shown in POST example for replyingIdentifies the thread or existing reply to reply under; returned id of a created reply
textPOST /v1/comments bodystringShown in POST exampleBody text of the reply
limitGET /v1/comments querynumber, example 25Optional; range 1 to 100, defaults to 25Controls page size for list replies
nextCursorGET /v1/comments responsestring, example QVFIUm...Returned when more results are availableCursor for the next page
afterGET /v1/comments querystring, value of nextCursorUsed to page through resultsPass nextCursor back to fetch the next page
successGET and POST responsesboolean, example trueShown in both response examplesIndicates the call succeeded in the examples
commentsGET /v1/comments responsearray of reply objectsShown in GET response exampleTop-level replies with first level of nested replies
idReply objects in GET responsestring, example 17901234567890123Shown in GET response exampleIdentifier of a reply; use as commentId to reply to it
authorReply objects in GET responseobject with id and nameShown in GET response exampleAuthor of the reply
timestampReply objects in GET responsestring, example 2026-08-05T14:22:10ZShown in GET response exampleTime of the reply
likeCountReply objects in GET responsenumber, example 4Shown in GET response exampleLike count for the reply
hiddenTop-level reply objects in GET responseboolean, example falseShown on top-level reply in GET response exampleHidden flag as returned for top-level replies
repliesTop-level reply objects in GET responsearray of reply objectsShown in GET response exampleFirst level of nested replies under a top-level reply

Requiredness is stated only where the source examples and prose support it; no additional requiredness invented.

commentId versus postId on Threads
Field sent on POST /v1/commentsWhat it creates on ThreadsWhen to use it
commentIdA reply under the thread or existing reply identified by commentIdAnswering someone or staying in a conversation
postIdA brand new top-level Threads postOnly when you actually mean to publish something new

Threads-specific behavior as described in the source; differs from Instagram and Facebook postId behavior described there.

Threads replies operations and limitations
OperationSupported for Threads replies via this APINotes
List replies with GET /v1/commentsYesReturns top-level replies plus first level of nested replies
Post a reply with POST /v1/comments and commentIdYesReturns the commentId of the created reply
Delete a Threads replyNothreads_delete described as not approved; handle manually in the Threads app
Hide a Threads replyNothreads_delete described as not approved; handle manually in the Threads app

Limitation as described in the source, attributed to threads_delete not being approved; verify current platform status before publication.

Worked example from list to reply
StepRequestValue carried forward
1. List repliesGET /v1/comments with platform=threads, accountId, postId, and limit=25Response comments[0].id is 17901234567890123
2. Reply to that replyPOST /v1/comments with platform=threads, accountId, commentId=17901234567890123, and textResponse commentId is 17901234567891234

Illustrative example using the exact field names and shapes from the source examples; not an executed call.

Connect a Threads account
curl {{API_BASE_URL}}/v1/connect/threads \
  -H "x-access-key: YOUR_API_KEY"
List connected integrations to retrieve accountId
curl {{API_BASE_URL}}/v1/connect/integrations \
  -H "x-access-key: YOUR_API_KEY"
List Threads replies with GET /v1/comments
curl "{{API_BASE_URL}}/v1/comments?platform=threads&accountId=your-threads-id&postId=THREAD_ID&limit=25" \
  -H "x-access-key: YOUR_API_KEY"
Example list replies response
{
	"success": true,
	"comments": [
		{
			"id": "17901234567890123",
			"text": "An example comment.",
			"author": { "id": "9988776655", "name": "maya.builds" },
			"timestamp": "2026-08-05T14:22:10Z",
			"likeCount": 4,
			"hidden": false,
			"replies": [
				{
					"id": "17901234567890999",
					"text": "An example comment.",
					"author": { "id": "1122334455", "name": "you" },
					"timestamp": "2026-08-05T14:40:02Z",
					"likeCount": 1
				}
			]
		}
	],
	"nextCursor": "QVFIUm..."
}
Reply to a Threads reply with POST /v1/comments
curl -X POST {{API_BASE_URL}}/v1/comments \
  -H "x-access-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "platform": "threads",
    "accountId": "your-threads-id",
    "commentId": "17901234567890123",
    "text": "An example comment."
  }'
Example reply response
{
	"success": true,
	"commentId": "17901234567891234"
}