GET https://xquik.com/api/v1/x/tweets/{id}/replies
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.402 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.
Get replies by tweet ID for analysis, support, moderation, giveaways, and agents.
See reply coverage and optional fields.
X (Twitter) API reply questions
How complete is a tweet reply collection?
Protected accounts’ replies count toward coverage but aren’t returned. X may omit deleted, hidden, or unavailable replies.mode=complete adds nested replies & a coverage diagnostic.
Direct replies match inReplyToId to the source tweet.
Trust diagnostic.complete for direct coverage only. On a sinceTime or
untilTime request it means the whole window was covered.
It does not prove that Xquik returned every nested reply.
Requested limits & deadlines still apply.
Check strategiesAttempted for early stops.How can applications control reply API costs?
Direct replies handoff
UseGET /x/tweets/{id}/replies for support, community, moderation, giveaway, or agent workflows.
The examples above write rows. They are JSON Lines rows with parent_tweet_id, reply_id,
text, author IDs and usernames. They also have thread joins, media URLs, & cursors.
The moderation table below adds follower, verification, timing,
and engagement projections.
Use reply_extractor instead when a team needs
an estimate or a reusable extraction ID. Use it for stored result pages or CSV,
JSON, and XLSX downloads after completion.Build a reply moderation table
Store one row per reply. Keep the parent Tweet ID and conversation ID beside the reply. Support, moderation, campaign, and giveaway reviews can then reconstruct each conversation branch.Which replies endpoint?
- Use
GET /api/v1/x/tweets/{id}/repliesfor one tweet’s replies as JSON rows. - Use
reply_extractorwhen you need saved CSV, JSON, or XLSX exports. - Use
GET /api/v1/x/tweets/searchwhen you need keyword, operator, structured-filter, orqueryTypesearch. To search one post’s replies, sendq=conversation_id:{id}there. This route reads replies without a search. Soqorqueryhere answers 400 before any read or charge. - Use
GET /api/v1/x/tweets/{id}/threadwhen you need ordered thread context around a tweet.
Path parameters
Query parameters
Tweet result filters
These filters apply to automatic and standard pagination. Remove every filter before requesting complete mode.See tweet filters for every filter. Common ones arefromUser, language, sinceDate, mediaType, minLikes, and hashtags.Choose fields
Headers
Response
200 OK
400 Invalid tweet ID
The response usesinvalid_tweet_id. Send a post ID or post URL instead.401 Unauthenticated
Anonymous requests getWWW-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 theRetry-After header before retrying.424 Replies incomplete
Collected rows & diagnostics stay in the answer. Rows are billed as usual.recommendedFallback says what to do next. A cut at your limit returns 200
with limit_reached: true.503 Complete reply extraction busy
Wait for theRetry-After duration before repeating complete mode.Response examples
200 example
- 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." } - 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": "replies_incomplete", "message": "Replies are incomplete. Retry complete mode 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." }