Reply Management

The Threads Reply Management API allows you manage replies to users' own Threads.

Hide Replies

Use the /manage_reply endpoint to hide/unhide any top-level replies. This will automatically hide/unhide all the nested replies. Note: Replies nested deeper than the top-level reply cannot be targeted in isolation to be hidden/unhidden.

Example Request

 curl -X POST \ -F "hide={true | false}" \ -F "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.net/v1.0/<THREADS_REPLY_ID>/manage_reply" 

Example Response

 { "success": true } 

Control Who Can Reply

Use the reply_control parameter to specify who can reply to a post being created for publishing. This parameter accepts one of the five options: everyone, accounts_you_follow, mentioned_only, parent_post_author_only, and followers_only.

Example Request

 curl -X POST \ -F "media_type=<MEDIA_TYPE>" \ -F "text=<TEXT>" \ -F "reply_control=accounts_you_follow" \ -F "access_token=<ACCESS_TOKEN>" \ "https://graph.threads.net/v1.0/me/threads" 

Example Response

 { "id": "1234567890" } 

Use the POST /{threads-user-id}/threads_publish endpoint to publish the media container ID returned in the previous step. It is recommended to wait on average 30 seconds before publishing a Threads media container to give our server enough time to fully process the upload. See the media container status endpoint for more details.

Parameters

• creation_id — Identifier of the Threads media container created from the /threads endpoint.

Example Request

 curl -i -X POST \ "https://graph.threads.net/v1.0/<THREADS_USER_ID>/threads_publish?creation_id=<MEDIA_CONTAINER_ID>&access_token=<ACCESS_TOKEN>" 

Example Response

 { "id": "1234567" // Threads Media ID }