Skip to main content
GET https://xquik.com/api/v1/x/users/{id}/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.
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
Omit mode to get the fullest results. The response shape stays the same. Pass next_cursor back unchanged as cursor. Keep the same endpoint, target, query, and filters.
Existing unprefixed cursors keep their legacy behavior. after, limit, and pageSize aliases also keep working. Billing still counts only returned rows. Use mode=standard only to keep the legacy pagination. A page can be empty or underfilled. Continue while has_next_page is true. Stop only after the response reports has_next_page=false. First-page requests do not support Idempotency-Key retries. Repeating a cursorless request starts a separate extraction. Results returned by that extraction incur their normal charges. Save each response before requesting its next page. A cursor sent again within 10 minutes returns the same page at no charge. After 10 minutes, you cannot replay earlier or terminal responses. If automatic coverage is busy, an initial request returns a standard data page. Live coverage cursors remain atomic. A cursor sent again while its page loads returns that page at no charge. Other repeats return 409 coverage_cursor_unavailable with exact Retry-After seconds. Wait, then send the same cursor again. Repeated busy responses never authorize restarting with another cursor. Expired, superseded, or identity-mismatched cursors return 410 coverage_cursor_gone. So does a cursor sent again after 10 minutes. The response omits Retry-After. Restart without a cursor. Keep received results. Deduplicate restarted results by id. Malformed cursors return 400 invalid_coverage_cursor. Restart without them. This route returns the public profile timeline for one Twitter or X account. The route is GET /api/v1/x/users/{id}/tweets. Protected accounts return HTTP 403 with x_account_protected. Choose a public account. This applies to every mode, including continuation requests. Xquik collects no results and charges nothing. Public profile lookup remains available.

Archive tweets from one profile

Use this user-tweets route when the source profile is already known. It fits profile timeline exports, account research, and approved historical backfills. Follow these steps for a repeatable profile timeline.
  • Resolve the profile to a numeric user ID.
  • Choose a stable page size.
  • Save each page before its next cursor.
  • Deduplicate resumed rows by tweet ID.
  • Stop when no next page remains.
Row order does not identify a tweet. New tweets can change the first page. Use tweet IDs for updates and deduplication. The first page opens with the pinned tweet, flagged isPinned. Later pages skip it. With replies included, it never opens the page. Rows stay in newest-first date order on every page. They include the account’s reposts. Pass retweets=exclude to drop reposts.

Path parameters

Query parameters

Tweet result filters

These optional filters apply to tweets[] returned by this route. They keep the same user target. Xquik filters rows after it fetches each page. Selective filters can return fewer rows than an unfiltered page.See tweet filters for every filter. Common ones are fromUser, language, sinceDate, mediaType, minLikes, and hashtags.

Keep posts by topic or photo

Send 1 of these to keep only the posts you want. AI-powered analysis checks each post the page reads. Posts scoring 0.5 or more come back, each with its score. Each kept post costs 2 credits instead of 1. A dropped post costs nothing. The page size counts checked posts. Posts the check can’t answer cost nothing & stay out. They need an Xquik API key, since each kept post bills Xquik credits. RapidAPI & pay-per-request calls with them get 400 invalid_input.

Choose fields

Headers

Response

200 OK

400 Invalid user ID

{ "error": "invalid_user_id", "message": "Send a user ID, @username or profile URL, such as x.com/nasa." } The user ID is empty or invalid.

404 User not found

The username or user ID doesn’t resolve.

401 Unauthenticated

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

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": "user_not_found", "message": "X user not found. Check the username." }
  • 409 { "error": "coverage_cursor_unavailable", "message": "Cursor busy. Retry after the indicated delay." }
  • 410 { "error": "coverage_cursor_gone", "message": "Cursor finished, expired, or superseded. Restart pagination without cursor." }
  • 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": "Maximum coverage is busy. Retry shortly." }