X Post Replies API

X Post Replies

Features

• Known-post conversation scopeAccept one or more public X status URLs, extract each numeric post ID, and return replies while excluding the submitted parent post itself.
• Reply and author recordsReturn reply IDs, canonical URLs, text, language, publication times, and normalized public author identity for each saved response.
• Visible response signalsKeep public like, reply, repost, quote, view, and bookmark counts together with media, hashtags, and mentions.
• Selectable timeline orderingRequest relevance, latest, or likes ordering for every submitted post while applying a separate result limit to each conversation.
• Conversation traceabilityPreserve the submitted URL, parent post ID, conversation ID, reply target, source, quote, repost, and limited-reply signals in normalized context.

Parameters

How to Use

Submit known public post URLs as an asynchronous task, then read normalized reply records from the completed task.

1. Prepare one or more public x.com or twitter.com URLs containing a numeric /status/{id}, then choose relevance, latest, or likes ordering.
2. POST urls, a per-post results_limit from 20 through 2000 in increments of 20, and sort_by to /v1/x/post-replies.
3. Retain the returned task_id and poll GET /v1/tasks/{task_id} while the task is queued, running, or retrying.
4. After success, read data.results.items and request the same task with cursor=data.results.next_cursor while data.results.has_more is true.

curl -X POST "https://api.socq.ai/v1/x/post-replies" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://x.com/OpenAI/status/1950240351547248941"],"results_limit":100,"sort_by":"relevance"}'

# Poll GET /v1/tasks/{task_id}
# Read data.results.items and pass data.results.next_cursor as cursor while has_more is true

Best Use Cases

• Public response analysis: Compare reply text, language, authors, and visible engagement across selected parent posts to examine how public conversations differ.
• Conversation thread reconstruction: Use parent_post_id, conversation_id, in_reply_to fields, reply IDs, and canonical URLs to reconnect saved responses with their visible thread context.
• Reply monitoring across collection runs: Track reply publication times, collected_at, authors, and public counters for a stable set of post URLs across scheduled snapshots.
• Manual triage dataset preparation: Combine reply text, author identity, timestamps, URLs, and visible engagement to prepare response records for downstream review queues.

Pro Tips

• Validate every URL against an accepted X or Twitter host and a numeric /status/ ID before submission so profile and search links do not create failed tasks.
• Extract and deduplicate the numeric status ID across x.com and twitter.com URL variants because different URL strings can point to the same parent post.
• Size results_limit per parent post in increments of 20; total candidates can approach urls × results_limit before conversation endings and task-level deduplication.
• Choose sort_by for the collection goal, but do not compare positions across relevance, latest, and likes modes as a shared ranking score.
• When reconstructing many parent conversations, account for task-level reply deduplication because one saved reply retains one submitted URL and parent-post context.
• Treat a short or empty result as a public-visibility outcome, and store nullable author, media, metric, and relationship fields without inventing placeholders.

Related APIs