threads/
post-replies

The Threads Post Replies API collects replies under Threads posts from post URLs, with reply text, author and verified badge, like and reply counts, media, time and the ID of the post answered.

Threads Post Replies API

Post URL input
About 20 replies per post
Likes and reply counts
Verified author flag
0.3 credits / result
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Threads Post Replies

Threads post replies are the conversation that forms under a post, where each reply carries its own text, the account that wrote it, any images or video, a timestamp and counts of the likes and further replies it drew. Read together, they show how an audience actually reacted to an announcement, which questions and complaints came up, and which voices pulled the most agreement.

Threads Post Replies API Features

  • Replies straight from post linksGive urls one or more /@{username}/post/{code} links on threads.com or threads.net and receive the replies Threads shows under each post, around 20 per post.
  • Engagement on every replymetrics.likes_count shows how much agreement a reply earned and metrics.replies_count how much further discussion it started.
  • Reply authors with verificationauthor gives each replier's username, display name, profile url and avatar, and is_verified separates badge holders from everyone else.
  • Tied to the post it answerspost_id identifies the post each reply belongs to, and url opens the reply itself, so mixed batches stay easy to split and check.

Threads Post Replies API Parameters

ParametersRequiredDescription
urlsRequiredThreads post links in the /@{username}/post/{code} form on threads.com or threads.net, such as https://www.threads.com/@unrivaledbasketball/post/Dfa88pLDs_1.

How to Use the Threads Post Replies API

Submit post links to the Threads Post Replies API and read back the replies under each one.

  1. POST {"urls": ["https://www.threads.com/@unrivaledbasketball/post/Dfa88pLDs_1"]} to /v1/threads/post-replies and note the task_id.
  2. Poll GET /v1/tasks/{task_id}; the replies are ready once status is succeeded.
  3. Read the replies from results.items and, when has_more is true, continue with results.next_cursor.
curl -X POST "https://api.socq.ai/v1/threads/post-replies" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://www.threads.com/@unrivaledbasketball/post/Dfa88pLDs_1"]}'

# 0.3 credits per reply; posts without replies are free.

Threads Post Replies API Use Cases

  • Gauging reaction to an announcement: Read the reply text under a launch or news post and weight it by likes_count to see which responses the audience backed.
  • Collecting customer feedback from brand posts: Gather replies under a brand's posts with their published_at times to log questions, complaints and requests as they arrive.
  • Spotting the most engaged people in an audience: Count how often each author.username replies across a creator's posts and how many likes those replies collect to find the regulars worth reaching out to.
  • Comparing how different posts landed: Submit several posts to the Threads Post Replies API together and group replies by post_id to compare the volume and tone of responses each one drew.

Threads Post Replies API Pro Tips

  • Copy the link of the post itself; a profile address such as /@username is rejected here, and an account's own replies elsewhere come from Threads User Replies API.
  • Expect around 20 replies per post, roughly 6 credits at 0.3 each, and budget a batch by multiplying that by the number of posts.
  • Deduplicate on id when you run the Threads Post Replies API on the same post again later, because the replies Threads shows can overlap from one run to the next.

Beyond the Threads Post Replies API, use these APIs when you need a different type of public Threads data.

  • Threads Posts API — Collect public post text, author context, media, timestamps, and visible engagement from supported Threads post URLs.
  • Threads Profiles API — Collect public profile identity, biographies, images, websites, visible account counts, and collection context from supported Threads profile URLs.
  • Threads User Posts API — Discover public posts from Threads profile URLs with a per-profile limit, normalized content, authors, media, timestamps, visible engagement, and source context.
  • Threads Search API — Search Threads by keyword or hashtag for the top posts, with text, authors, likes, replies, reposts, media and publish time.
  • Threads User Search API — Find Threads accounts by name or username, returning usernames, display names, profile URLs, avatars and verification status.
  • Threads User Replies API — Collect the latest public replies an account has posted from Threads profile URLs, with reply text, engagement, media and links.

Explore other platforms

Combine Threads data with public data from other supported social platforms.

Threads Post Replies API — FAQ

Threads Post Replies API is a programmatic interface for reading the replies under public Threads posts from the posts' URLs. It returns each reply's text, author with verification status, like and reply counts, media, publish time and the ID of the post it answers.

Use the post's own link in the /@{username}/post/{code} form. Both threads.com and threads.net addresses work.

Each post returns the replies Threads shows under it, around 20, so the request needs only the post links.

Add every post link to urls. Each reply carries post_id, which tells you which post it came from.

The Threads Post Replies API charges 0.3 credits for each reply returned, so a post with about 20 replies costs around 6 credits.