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

This route reads the newest tweets of many users at once. It charges only for returned tweets. Use Get user timeline to page through 1 user’s older tweets.
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. Send unprocessed_ids again. Skip unavailable_ids.

Several timelines in 1 call

Tweets arrive user by user, in the order you named the users. Each user’s tweets are newest first, after the pinned tweet. Group rows by author.id. A call returns up to 20 tweets per user. Set pageSize to return fewer, or up to 300. A batch returns 1 page, so has_next_page is false & next_cursor is empty.A user with no tweets appears in neither list & adds no rows.

Query parameters

Choose fields

Headers

Response

200 OK

Both lists name each user as you sent it, by ID or username. A profile link is named by its username.

400 Missing IDs

{ "error": "missing_ids", "message": "Send ids or usernames, such as ids=11348282 or usernames=nasa." } Send ids or usernames.

400 Invalid user IDs

{ "error": "invalid_user_ids", "message": "usernames must contain X usernames or profile links such as x.com/nasa." } Each ids value must be a numeric user ID. Each usernames value must be a username or a profile link. Profile links must be on x.com or twitter.com. Sending both ids & usernames also answers 400. 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.

503 No user could be read

No user’s tweets could be read. The request costs nothing. Wait for the Retry-After header, then send it again.

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