X Thread Context API

X Thread Context

Features

• Read the selected post with its surrounding discussionUse a post link to collect the target message together with earlier public messages along its reply chain and the available replies that follow, giving you context beyond the selected message alone.
• Understand which posts belong together and who replies to whomAlongside text, authors and interaction counts, conversation_id identifies the conversation a post belongs to and in_reply_to_id identifies the post it directly replies to, giving you links between the individual records.

Parameters

How to Use

The request starts a background collection task, so its first response gives you a task ID rather than the finished data; use that ID to check progress and retrieve the results.

1. Copy the public post link you want to understand and choose how many context records to request for it; if you have several links, put each one in the urls list.
2. Before running the example, replace $SOCQ_API_KEY with your own API key or set that environment variable. Send the JSON input to POST /v1/x/thread-context with the Authorization header shown below, then save the task_id from the response.
3. Use GET /v1/tasks/{task_id} with the saved ID to check progress. queued means waiting, running means collection is in progress, and retrying means another attempt is underway. Wait for succeeded before reading the results; if the task is failed, read error_message for the reason.
4. When the task succeeds, read data.results.items: each item in this list describes one post and its available conversation relationships. An empty list means the task completed without returning any records.
5. If data.results.has_more is true, the next_cursor value is the marker for another page of saved results. Copy it unchanged into the cursor parameter of GET /v1/tasks/{task_id}?cursor=... and continue until has_more is false.

curl -X POST "https://api.socq.ai/v1/x/thread-context" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://x.com/BaganiTohid/status/2110635249889919362"],"results_limit":20}'

Best Use Cases

• Review a message with the context needed to read it: Place the target post next to the returned earlier messages and replies, including their text and authors, to prepare a reading view for someone checking what the selected message was responding to.
• Build a map of the returned reply relationships: Group posts by conversation_id and match each in_reply_to_id to another record’s id to draw the reply links that are present, leaving gaps visible when a referenced post was not returned.
• Prepare source material for a conversation summary: Save the post text, author names, times and reply relationships as an ordered reading set for a separate human or software summarization step, rather than expecting a finished summary in the response.

Pro Tips

• When arranging a discussion for reading, connect posts using their relationship IDs first and use publication time only as supporting context, because a time-sorted list alone does not tell you which message each post answers.
• If in_reply_to_id refers to an ID that is absent from your saved records, keep that reference as a missing link instead of attaching the reply to a different post or inventing the missing text.
• When several submitted links belong to the same conversation, merge saved results by post ID so a shared earlier post does not appear several times in your reading set.
• If you only need a selected post’s replies, use X Post Replies; if you only need the selected post itself, use X Posts instead of collecting surrounding context.

Related APIs