Skip to main content
GET https://xquik.com/api/v1/x/tweets/{id}/thread
Repost records include retweetedAt, the repost event’s UTC ISO 8601 timestamp. It is null when that timestamp is unavailable. The API omits it for original posts. The nested original post keeps its own creation date. This field does not report every account that reposted a post. Request per-account timestamps with Get retweeters.
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per tweet returned · All plans from $0.00012/credit · Supports guest paid reads
Get tweet thread returns tweet rows in the conversation thread around one source tweet. Results exclude X ads. The endpoint is GET /api/v1/x/tweets/{id}/thread. A post X does not have returns 404 tweet_not_found, as Get tweet does. Deleted, suspended-account & protected posts count as missing. A 404 costs no credits.
The Node.js and Python snippets write JSON Lines thread rows plus a separate checkpoint. They do not write raw response pages. Store each mapped row and the latest next_cursor. A support timeline, research job, moderation queue, or agent handoff can then resume. It can resume from the last completed page without duplicate rows.

Direct tweet thread handoff

Use GET /api/v1/x/tweets/{id}/thread when a workflow needs ordered thread rows around one tweet. Store source_tweet_id, thread_tweet_id, text, author_id, author_username, author_name, author_followers, author_verified, author_profile_picture, and created_at. Also store conversation_id, in_reply_to_id, media URLs, and a separate next_cursor checkpoint for later jobs.

Thread rows

Store tweets[] as the thread context rows returned for one source tweet.

Stable upserts

Store tweets[].id as thread_tweet_id with source_tweet_id for idempotent imports.

Reply joins

Store conversationId, inReplyToId, inReplyToUserId, and inReplyToUsername to rebuild thread structure.

Author joins

Store tweets[].author.id, username, name, followers, verified, and profilePicture for review, CRM, or research tools.

Media context

Store media[].mediaUrl, entities, quoted_tweet, and retweeted_tweet when returned to keep attached context.

Next page

Store has_next_page and next_cursor. Then pass next_cursor back as cursor only when has_next_page is true.

Credit-limited pages

Use tweets.length, not a requested page size, for row counts. Low balances can return fewer rows.

Saved exports

Use thread_extractor for a saved extraction job or CSV, JSON, or XLSX export.
Direct tweet thread reads cost 1 credit per tweet returned. Low credit balances can return fewer tweets than a full page. Zero affordable results return 402 insufficient_credits.

Reconstruct an ordered tweet thread

Use this route when several connected posts form one authored sequence. Start from a known tweet ID. Store each tweet ID, text, author, creation time, engagement counts, media, and thread position. Keep the starting tweet ID with the complete result. Render posts in the returned thread order. Do not sort by engagement counts. Keep media and quote relationships inside each post. Thread results can support long-form reading, approved archiving, or conversation context. A reply from another author may belong to a different conversation path. Use tweet replies for responses under one post. Use quote tweets for external commentary. Use exact tweet lookup when only one post is required.

Path parameters

Query parameters

Tweet result filters

See tweet filters for every filter. Common ones are fromUser, language, sinceDate, mediaType, minLikes, and hashtags.

Choose fields

Which thread endpoint?

Tweet thread

Use GET /x/tweets/{id}/thread for conversation thread context around one tweet.

Tweet replies

Use GET /x/tweets/{id}/replies when you need reply tweet rows under one source tweet.

Quote tweets

Use GET /x/tweets/{id}/quotes for tweet rows that quote one source tweet.

Search tweets

Use GET /x/tweets/search when you need keyword, operator, or structured-filter discovery across many tweets.

Saved exports

Use Create extraction with toolType=thread_extractor for a saved job or CSV, JSON, or XLSX export.

Single tweet

Use Get tweet when you only need one tweet object by ID.

Headers

Response

200 OK

400 Invalid tweet ID

{ "error": "invalid_tweet_id" }

401 Unauthenticated

Anonymous requests get WWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge.

402 Payment required

Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.

502 X API unavailable

The read service returned an error. Retry after a short delay.

429 Rate limit exceeded

You exceeded your tier rate limit. Wait for the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.

Response examples

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "tweet_not_found", "message": "Tweet not found. Check the tweet ID." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }