Skip to main content
GET https://xquik.com/api/v1/x/tweets
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.

When to use batch lookup

Use this route to look up many tweet IDs at once. It charges only for returned tweets. Use list-tweets when reading a list feed instead.
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 · Accepts account credits and guest paid_reads
The Node.js and Python snippets build tweet rows. They do not print full response pages. Store tweetRows or tweet_rows and missingIds or missing_ids with the original ID list. Retries then request only missing tweets.

Direct batch tweet handoff

Use GET /x/tweets when a workflow already has tweet IDs. It can be a CRM, warehouse, newsroom, moderation queue, or agent workflow. One response returns tweet text, authors, metrics, media URLs, and missing-ID handling. Use Get Tweet for one tweet by ID. Use Search Tweets to find tweets by query. Store requested_ids, tweet_id, text, author_id, author_username, author_name, author_followers, author_verified, author_profile_picture, created_at, and conversation_id. Also store engagement counts, media URLs, has_next_page, and next_cursor. Join returned tweets by tweet_id. Do not rely on response order. Send as many IDs as fit in 1 URL. Batch requests always return has_next_page: false and next_cursor: "". Zero affordable results return 402 insufficient_credits.

Store exact batch lookup results

Keep the original request order separately. Join tweets by numeric Tweet ID because unavailable or unaffordable IDs can be absent.

Query parameters

Choose fields

Headers

Response

200 OK

400 Missing IDs

{ "error": "missing_ids", "message": "ids parameter required" }

400 Invalid tweet ID

{ "error": "invalid_tweet_id", "message": "Send ids as tweet IDs or tweet links, separated by commas." } An entry of ids names no tweet. Send each entry as a tweet ID or a tweet URL. The request costs nothing.

401 Unauthenticated

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

402 Payment required

Full account keys can receive no_subscription, subscription_inactive, no_credits, or insufficient_credits with account payment options. Guest keys receive only the guest top-up action. The failed request creates no checkout. Ask the user to confirm before calling any checkout or top-up route.

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." }
  • 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." }