Threads User Replies
Threads user replies are the responses an account leaves in other people's threads, each with its own text, timestamp, attached media, link and counts of the likes, replies and reposts it received. Because replies are quicker and less polished than headline posts, they show an account's tone, expertise and way of handling conversations, which matters when vetting creators, following a spokesperson or studying customer care.
Threads User Replies API Features
- Replies rather than postsFrom a profile link such as https://www.threads.com/@reuters, the response holds what the account wrote in reply to others, its latest public replies up to about 25.
- Each reply's text, media and linktext holds what was said, media any images or video attached, and url opens the reply in its thread on Threads.
- How each reply was receivedmetrics.likes_count, metrics.comments_count and metrics.shares_count show the likes, follow-up replies and reposts each reply collected.
Threads User Replies API Parameters
| Parameters | Required | Description |
|---|---|---|
urls | Required | Threads profile links in the /@{username} form on threads.com or threads.net, such as https://www.threads.com/@reuters. |
How to Use the Threads User Replies API
Submit profile links to the Threads User Replies API and read each account's recent replies.
- Send {"urls": ["https://www.threads.com/@reuters"]} to POST /v1/threads/user-replies and keep the task_id.
- Poll GET /v1/tasks/{task_id} until the task has succeeded.
- Read the replies from results.items; when has_more is true, load the next page with results.next_cursor.
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"]}'
# 0.5 credits per reply returned.Threads User Replies API Use Cases
- Vetting a creator before a partnership: Read a creator's recent reply text to judge tone, expertise and how they treat their audience beyond their polished posts.
- Following a spokesperson's public replies: Collect an executive's or spokesperson's replies on a schedule and log new ones by published_at to catch statements made in conversation.
- Reviewing how a brand handles customer conversations: Study a brand account's replies, how often they appear by published_at and which earn likes, to see how its support and community team responds in public.
Threads User Replies API Pro Tips
- Use the profile link, not a post link; for the replies other people left under a particular post, use Threads Post Replies API instead.
- Keep a longer record by collecting on a schedule and deduplicating on id, since each run covers only the latest replies, up to about 25 per account.
- Read metrics.comments_count as the number of replies the reply itself received, which flags the exchanges that turned into longer discussions.
- Open a row's url to see what the reply was answering, because the link shows the reply inside its thread.
Related APIs
Beyond the Threads User 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 Post Replies API — Collect the replies under Threads posts from post URLs, with reply text, authors, like and reply counts, media and the ID of the post answered.
- 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 Reposts API — Collect the posts an account recently reposted from Threads profile URLs, each as the original post with its author, text, engagement and media.