ThreadsThreads SearchThreads RepliesAPI Guide

Threads Search API: Search Posts and Users, Collect Replies and Reposts

Five new SocQ Threads endpoints: keyword and hashtag post search, user search, replies under a post, a user's replies and a user's reposts, with requests and per-result prices.

SocQUpdated November 19, 20266 min read

SocQ's first Threads endpoints read public profiles, single posts and a user's posts. On 2026-11-17 five more launched. Two of them are search: find posts by keyword or hashtag, and find accounts by name. The other three read conversations and amplification: the replies under a post, the replies an account leaves elsewhere, and the posts it reposts.

This guide covers what each new endpoint returns, the request, the price and when to use it. For how these compare with Meta's own Threads API and other providers, see Threads API alternatives.

Quick answer: Send a query to POST /v1/threads/search or /search-users, or Threads URLs in urls to /post-replies, /user-replies or /user-reposts, with Authorization: Bearer $SOCQ_API_KEY. Poll GET /v1/tasks/{task_id} until status is succeeded, then read data.results.items. Prices run from 0.3 to 0.6 credits per result ($0.0015 to $0.003 at $0.005 per credit), with no base fee.

The Five New Threads Endpoints

EndpointWhat it returnsInputPrice
SearchTop posts for a keyword or hashtag, about 20, with text, author, likes, replies, reposts, media and timequery0.6 credits ($0.003) per post
User SearchAccounts matching a name or username, usually up to 10, with display name, avatar and verificationquery0.6 credits ($0.003) per account
Post RepliesReplies under a post, around 20 per post, with author, likes, replies, media and timePost URLs0.3 credits ($0.0015) per reply
User RepliesAn account's latest public replies, up to about 25, with engagement and mediaProfile URLs0.5 credits ($0.0025) per reply
User RepostsPosts an account recently reposted, up to about 25, each with its original authorProfile URLs0.5 credits ($0.0025) per post

Search Threads

Threads Search: Posts by Keyword or Hashtag

The Threads Search API searches Threads the way the app does and returns the top posts for a keyword or hashtag. Every post comes with its text, author, likes, replies, reposts, media and publish time. It is the fastest way to see how a topic, product or event is discussed on Threads and to find the accounts driving that conversation.

curl -X POST "https://api.socq.ai/v1/threads/search" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "basketball"
  }'

Each search returns the top posts Threads shows for the query, about 20. Engagement sits under metrics: likes_count, comments_count and shares_count. See the Search docs.

Threads User Search: Accounts by Name

The Threads User Search API finds accounts by name or username. Each match returns the username, display name, profile URL, avatar and verification status. Use it to confirm the right handle before you pull posts or replies, or to turn a list of names into Threads profiles for influencer research.

curl -X POST "https://api.socq.ai/v1/threads/search-users" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "shams"
  }'

Each search returns the accounts Threads suggests, usually up to 10. See the User Search docs.

Read Conversations and Reposts

Threads Post Replies: The Conversation Under a Post

The Threads Post Replies API reads the conversation under a post. Each reply includes its text, author, like and reply counts, attached media and time, plus the post_id of the post it answers. Use it to gauge reaction to an announcement, collect customer feedback from a brand's posts, or find the most engaged people in a creator's audience.

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"]
  }'

Use post URLs in the form /@{username}/post/{code}. Each post returns the replies Threads shows under it, around 20. See the Post Replies docs.

Threads User Replies: How an Account Talks to Others

The Threads User Replies API returns an account's latest public replies with text, likes, replies, media, time and a link to each reply. Replies show tone and expertise more directly than polished posts, which makes them useful for vetting creators, monitoring a spokesperson or studying how a brand handles customer conversations.

curl -X POST "https://api.socq.ai/v1/threads/user-replies" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": ["https://www.threads.com/@reuters"]
  }'

Use profile URLs such as https://www.threads.com/@username. Each profile returns up to about 25 replies. See the User Replies docs.

Threads User Reposts: Whom an Account Amplifies

The Threads User Reposts API returns the posts an account chose to repost. Each row is the original post with its author, text, engagement and media. Repost history is a direct signal of affinity: it maps the voices a creator trusts, the partners a brand promotes and the content that spreads through a community.

curl -X POST "https://api.socq.ai/v1/threads/user-reposts" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "urls": ["https://www.threads.com/@shams"]
  }'

Each profile returns up to about 25 recent reposts; author is the original poster, not the account that reposted. See the User Reposts docs.

A Simple Research Workflow

  1. Run Search on a product name or hashtag to find the posts people engage with.
  2. Pass the strongest post URLs to Post Replies to read the reactions.
  3. Use User Search to resolve the names that come up into handles, then User Replies and User Reposts on those profiles to see how they talk and whom they amplify.
  4. For an account's own posts or profile details, use the earlier User Posts and Profiles endpoints.

Authentication and the Async Task Flow

Every request carries your API key and a JSON content type:

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Each submit call starts a background task:

submit -> task_id -> queued -> running -> succeeded
                                   \-> failed

The submit response returns data.task_id and data.status. Poll the task with the same key:

curl "https://api.socq.ai/v1/tasks/$TASK_ID?limit=50" \
  -H "Authorization: Bearer $SOCQ_API_KEY"

While the task is queued, running or failed, the response holds task metadata only; on failed, read error_message. When it is succeeded, the same response includes the first page of normalized records in data.results.items. limit defaults to 50 and goes up to 500. If has_more is true, pass results.next_cursor as cursor to read the next page. fields accepts up to 50 comma-separated fields or dot paths.

A client-side timeout does not cancel a task, so resume with the same task_id instead of submitting and paying for a duplicate. You can also add callback_url to the submit body to receive one POST with a task summary when the task finishes.

What a Typical Job Costs

  • One keyword search returning 20 posts: 20 × 0.6 = 12 credits, $0.06.
  • Replies under 10 posts at about 20 each: 200 × 0.3 = 60 credits, $0.30.
  • Replies and reposts for 10 accounts at about 25 each: 500 × 0.5 = 250 credits, $1.25.

FAQ

Can I page past the first 20 search results?

Search returns the top posts Threads shows for the query, about 20 per search. To widen coverage, run related keywords or hashtags as separate searches.

Do I need a Threads or Instagram login?

No. A request contains only your SocQ API key and a query or public Threads URLs; no Threads account credentials are part of it.

Does User Reposts show who reposted?

You request it for one profile, so every row was reposted by that profile. Each row's author is the original poster.

Can I send several profiles or posts at once?

Yes. Post Replies, User Replies and User Reposts take a list in urls, and the result counts apply per URL.

Where can I see all Threads endpoints and prices?

On the Threads platform page and the pricing page.

THREADS API

Test the workflow with a public Threads URL

Submit public inputs and receive normalized records with traceable source context.

Explore Threads APIs