sapi_cmt_ ID. You can list replies, answer a post or a reply, hide and unhide replies from other accounts, and delete replies your account wrote. A public reply costs 1 interaction credit, and reading, hiding, and deleting cost none. The rules shared by every platform are in Comments.
Endpoints
{post_id} is the Threads post ID: targets[].platform_post_id on a post you published through SocialAPI, or id from GET /v1/inbox/comments. A Threads post ID is digits, optionally followed by an underscore and more digits, such as 18045720651234567. Any other value returns 400 validation.field_invalid on GET /v1/inbox/comments/{post_id}. {comment_id} and comment_id accept the reply’s sapi_cmt_ ID or its Threads ID: see IDs.
The like and private reply endpoints return 501 resource.not_supported on Threads: see What Threads does not support.
Your first reply
List the replies to one post.account_id is required:
comment_id in the response is the sapi_cmt_ ID of your new reply. The reply is public on Threads when the call returns.
List replies
GET /v1/inbox/comments/{post_id} lists the direct replies to a post. GET /v1/inbox/comments/{post_id}/{comment_id}/replies lists the direct replies to one reply, in the same shape.
Threads lists replies newest first. A page can hold fewer replies than
limit. Follow next_cursor until has_more is false: see Pagination. On Threads, SocialAPI ignores moderation_status, order, and q. On GET /v1/inbox/comments/{post_id}, an invalid value still returns 400 validation.field_invalid.
Each reply has the fields described in List comments and replies. On Threads, these fields have fixed values:
The
capabilities object is the same on every Threads reply:
Nested replies
A Threads conversation is a tree: a reply can have its own replies, at any depth. The post’s replies list returns only the replies made directly to the post. When a reply hashas_replies: true, list its replies with GET /v1/inbox/comments/{post_id}/{comment_id}/replies, passing the reply’s id as {comment_id} and keeping the original post as {post_id}. Repeat on each reply that has has_replies: true to read the whole tree.
Reply to a post or a reply
POST /v1/inbox/comments/{post_id} publishes a public reply from the connected account.
SocialAPI sends replies as text only, and a listed reply returns its text without its image or video. A reply costs 1 interaction credit. When the plan’s interaction allowance is used up, the call returns
429 validation.interaction_limit_exhausted. The credit comes back only when the request fails with a validation.* error: see When a credit comes back.
Threads allows 1,000 replies per rolling 24 hours for each account. GET /v1/accounts/{account_id}/limits returns the replies left in replies_remaining and the total in replies_total: see Read a platform’s remaining quota.
Hide and unhide a reply
Hiding removes a direct reply to your post from public view. The person who wrote the reply still sees it, and hiding a reply also hides every reply under it. Unhiding restores it.DELETE on the same path and account_id as a query parameter:
- Only replies from other accounts. Hiding your account’s own reply returns
403 platform.threads.10.4279017. Delete your own reply instead. - Only replies on your posts. You can hide a reply only under a post your account owns.
- Only direct replies to your post. A reply to a reply cannot be hidden on its own. Hide the direct reply to your post that it sits under, which also hides every reply under it.
- Needs the
threads_manage_repliesscope. An account connected before 2026-10-17 does not hold it, and a hide or unhide on such an account returnsplatform.threads.<code>(HTTP 403), where<code>is from 200 to 299, or422 platform.threads.10with Meta’s reason inerror.message. Reconnect the account with thecomments.writepermission to add the scope: see Reconnect an account.
Delete a reply
DELETE /v1/inbox/comments/{post_id}/{comment_id}?account_id={account_id} deletes a reply on Threads. It cannot be undone.
- Only replies your account wrote. Threads refuses to delete a reply from another account, even under your own post. Hide that reply instead.
- Nested replies go with it. Deleting a reply also deletes every reply under it.
- Threads’ deletion quota. Threads allows 100 deletions per rolling 24 hours for each account, shared between replies and posts: see Platform limits.
threads_delete scope, not threads_manage_replies.
What Threads does not support
- Liking a reply.
POSTandDELETE /v1/inbox/comments/{post_id}/{comment_id}/likereturn501 resource.not_supported. - Private replies.
POST /v1/inbox/comments/{post_id}/{comment_id}/private-replyreturns501 resource.not_supported. Threads has no direct messages in its API, so there is no DM to start: answer with a public reply. - Editing a reply. Threads’ API cannot edit a published reply. Delete it and send a new one.
- Replies held for approval. A post published with
enable_reply_approvals(see Threads publishing) holds new replies until you approve them. SocialAPI has no endpoint to list or approve held replies: approve them in the Threads app.
Limits
When Threads refuses a call for its own rate limit, including too many calls for one Threads profile, the call returns
429 platform.threads.rate_limit. Wait for Retry-After when it is present, or at least 60 seconds: see Platform limits.
Errors and debugging
Check these in order when a Threads reply call fails:403 account.permission_missing. The account lacks the permission the call needs:comments.readto list replies,comments.writeto reply, hide, unhide, or delete.error.meta.permissionnames it.404 account.not_found,403 account.reconnection_required,401 platform.threads.auth. Theacc_ID is not yours, or the account needs reconnecting because the person revoked access or the token expired: see Reconnect an account.400 validation.body_invalid,400 validation.field_required,400 validation.field_invalid. The JSON body of a reply or a hide is malformed,account_idortextis missing,limitis not a positive integer, or{post_id}is not a Threads post ID.error.meta.fieldnames the field. Fix the request and send it again.400 validation.id_invalid,400 validation.id_platform_mismatch. The reply ID is not a comment ID, or it belongs to another platform.platform.threads.<code>(HTTP 403), where<code>is from 200 to 299. The account lacks a Threads scope the call needs. Reconnect the account.422 platform.threads.10. Threads refused the call as not permitted.error.messagecarries Meta’s reason. When it names a missing permission, reconnect the account.422 platform.threads.1. Threads reported an unknown error.error.messagecarries Meta’s reason. Retry the request with backoff.platform.threads.10.<subcode>(HTTP 403). Threads refused this action on this specific post or reply, anderror.messagesays why.403 platform.threads.10.4279017means you tried to hide a reply your own account wrote: delete it instead.404 resource.not_found. The post or reply does not exist, or Threads refused a value in the request as invalid, for example an ID or the reply text. Check the ID, and keep the reply to 500 characters or fewer.429 validation.interaction_limit_exhausted,429 platform.threads.rate_limit. Your plan’s interaction allowance, or Threads’ own limit. See Rate limits.501 resource.not_supported. You called the like or private reply endpoint.- Any other error on a hide or a delete. Check the Threads rules above: Threads refuses a hide of a reply to a reply and a delete of another account’s reply. Hide the direct reply above it, or hide the other account’s reply instead of deleting it.
Scopes
Listing posts with
GET /v1/inbox/comments needs the inbox:read API key scope. API key scopes are in Scoped API keys. Every Threads scope SocialAPI requests is in Threads scopes.
Events
SocialAPI sendscomment.received when a person replies to one of your Threads posts. Your account’s own replies do not emit it. Your webhook endpoint receives no comment.received events for a connected account without comments.read. The Threads payload carries the person’s author.username, the root post’s ID in platform_post_id, the reply’s URL in permalink, and the ID of the post or reply being answered in metadata.parent_id. In the Threads event, account_id is the Threads user ID, not an acc_ ID. See comment.received.
Use from an AI agent
social_api_like_comment, social_api_unlike_comment, and social_api_private_reply_to_comment return resource.not_supported on Threads. The tool list is in MCP tools.
Related
- Threads API: capabilities, connect, mentions, insights, and every Threads scope
- Threads publishing:
reply_controlandenable_reply_approvalsset who can reply to a post - Comments: the comments endpoints and rules shared by every platform
- Webhook events: the
comment.receivedpayload - Plans and usage: what costs an interaction credit