GET https://xquik.com/api/v1/x/users/{id}/replies
When to use the With Replies timeline
Use this route when every page must include replies. It can include parent context for each reply row. Use the standard user timeline when original posts are the primary target. Like x.com’s Replies tab, this route never opens with the pinned tweet. 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 returns402 insufficient_credits.1 credit per tweet returned · All plans from $0.00012/credit · Supports guest paid reads
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.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 With Replies timeline for one
public X profile. It includes replies by default. You do not need
includeReplies=true on 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.Build a profile reply archive
Use this route to collect replies authored by one profile. Keep the source profile ID with every reply. Also keep the replied-to tweet ID when available. Use reply rows for support review, conversation research, or approved archiving. Do not merge them into original posts without a clear reply flag. Deduplicate by reply tweet ID. Save every page before advancing its cursor. New replies can shift the first page between runs.Path parameters
Query parameters
Tweet result filters
These optional filters apply totweets[] 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 400invalid_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.401 Unauthenticated
Anonymous requests getWWW-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 theRetry-After header before retrying.424 Dependency failed
The normalized v1 response contract can return 424 when the read service is unavailable.Related. Get user timeline · Tweet replies · User media
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." }