Skip to main content
GET
/
x
/
tweets
/
{id}
/
replies
Get tweet replies
curl --request GET \
  --url https://xquik.com/api/v1/x/tweets/{id}/replies \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, 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 · Accepts MPP
Get tweet replies returns reply tweets for one X post by numeric tweet ID. Use it for conversation analysis, support queues, moderation review, giveaway audits, and agent handoffs. The canonical route stays GET /api/v1/x/tweets/{id}/replies.
# First page of replies
curl "https://xquik.com/api/v1/x/tweets/1893456789012345678/replies" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Resume with the previous next_cursor
curl -G "https://xquik.com/api/v1/x/tweets/1893456789012345678/replies" \
  --data-urlencode "cursor=DAACCgACGE..." \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Bound a campaign or moderation window
curl -G "https://xquik.com/api/v1/x/tweets/1893456789012345678/replies" \
  --data-urlencode "sinceTime=1777392000" \
  --data-urlencode "untilTime=1777478400" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

​
Direct replies handoff

Use GET /x/tweets/{id}/replies when a support, community, moderation, giveaway, or agent workflow needs reply rows as JSON. The examples above write JSON Lines rows with parent_tweet_id, reply_id, text, author ID, username, display name, follower count, verified state, profile image URL, thread joins, engagement counts, media URLs, and cursor fields. Each line represents one reply for a single tweet, so a worker can resume from the last saved next_cursor. Use reply_extractor instead when a team needs an estimate, durable extraction ID, stored result pages, or CSV, JSON, and XLSX downloads after completion.

Live reply page

Call GET /x/tweets/{id}/replies when queues, agents, or dashboards need current JSON rows and can store next_cursor.

Saved reply export

Run reply_extractor for estimates, job status, stored pages, and downloadable reply files.

Reply rows

Store tweets[] as reply rows for moderation queues, support triage, giveaway audits, or agents.

Reply keys

Store tweets[].id as the stable reply key for dedupe, labels, and follow-up actions.

Reply context

Store tweets[].text and tweets[].createdAt for reply context and time ordering.

Author joins

Store tweets[].author.id, tweets[].author.username, tweets[].author.name, tweets[].author.followers, tweets[].author.verified, and tweets[].author.profilePicture for joins, display names, trust cues, and avatars.

Thread joins

Store tweets[].inReplyToId and conversationId to join replies back to the parent tweet and thread.

Reply priority

Store engagement counts to prioritize high-signal or high-risk replies.

Attached context

Store tweets[].media, quoted_tweet, and retweeted_tweet to preserve attachments and relationship context when available.

Older replies

Store has_next_page and next_cursor, then pass next_cursor as cursor to fetch older reply pages.
sinceTime and untilTime are Unix timestamps in seconds. Use them to bound moderation windows, campaign periods, or giveaway audit ranges. Direct replies calls use the default paid page size; use reply_extractor with resultsLimit when you need a predictable file export cap. Direct replies cost 1 credit per tweet returned. Low credit balances can return fewer replies than a full page; zero affordable results return 402 insufficient_credits. Retry 429 with the Retry-After header, and retry 424 or 502 after a short backoff.

​
Which replies endpoint?

  • Use GET /api/v1/x/tweets/{id}/replies for one tweet’s replies as JSON rows.
  • Use reply_extractor when you need saved CSV, JSON, or XLSX exports.
  • Use GET /api/v1/x/tweets/search when you need keyword, operator, structured-filter, or queryType search.
  • Use GET /api/v1/x/tweets/{id}/thread when you need ordered thread context around a tweet.

​
Path parameters

​
id
string
required
Numeric X tweet ID. Pass the source tweet whose replies you want to retrieve.

​
Query parameters

​
cursor
string
Opaque pagination cursor for older reply pages. Omit it for the first page, then pass the next_cursor value from the previous response.
​
sinceTime
string
Unix timestamp in seconds. Only return replies after this time when a poller, moderation queue, or campaign report needs a bounded window.
​
untilTime
string
Unix timestamp in seconds. Only return replies before this time. Pair with sinceTime for closed campaign, support, or audit windows.

​
Tweet result filters

These optional filters apply to tweets[] returned by this route. They keep the same parent tweet and filter rows after each page is fetched, so selective filters can return fewer rows than an unfiltered page.
​
fromUser
string
Filter to tweets authored by this username. The @ prefix is optional.
​
toUser
string
Filter to replies directed to this username.
​
mentioning
string
Filter to tweets that mention this username.
​
language
string
Filter by tweet language code, such as en, tr, or es.
​
sinceDate
string
Filter to tweets created on or after this date or timestamp.
​
untilDate
string
Filter to tweets created before this date or timestamp. A YYYY-MM-DD value includes the whole day before the boundary.
​
mediaType
string
Filter by attached media or links. Values: images, videos, gifs, media, links, none.
​
minFaves
integer
Minimum like count.
​
minRetweets
integer
Minimum retweet count.
​
minReplies
integer
Minimum reply count.
​
minQuotes
integer
Minimum quote count.
​
verifiedOnly
boolean
When true, only return tweets from verified authors.
​
replies
string
Reply mode. Values: include, exclude, only.
​
retweets
string
Retweet mode. Values: include, exclude, only.
​
quotes
string
Quote mode. Values: include, exclude, only.
​
exactPhrase
string
Exact text that must appear in the tweet.
​
excludeWords
string
Words or quoted phrases to exclude from returned tweets. Separate with spaces, commas, or lines.
​
anyWords
string
Words or quoted phrases where at least 1 term must appear in the tweet. Separate with spaces, commas, or lines.
​
hashtags
string
Hashtags to match. Separate with spaces, commas, or lines. The # prefix is optional.
​
cashtags
string
Cashtags to match. Separate with spaces, commas, or lines. The $ prefix is optional.
​
url
string
URL substring or domain that must appear in tweet URL entities.
​
conversationId
string
Filter to tweets in this conversation thread.
​
inReplyToTweetId
string
Filter to replies to this tweet ID.
​
quotesOfTweetId
string
Filter to quote tweets of this tweet ID.
​
retweetsOfTweetId
string
Filter to retweets of this tweet ID.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
tweets
object[]
Array of reply tweets.
​
has_next_page
boolean
Whether more results are available.
​
next_cursor
string
Cursor for the next page.
{
  "tweets": [
    {
      "id": "1893456789012345679",
      "text": "I agree with this!",
      "createdAt": "2026-03-27T11:00:00.000Z",
      "isReply": true,
      "inReplyToId": "1893456789012345678",
      "author": {
        "id": "44196397",
        "username": "xquikcom",
        "name": "Xquik",
        "followers": 1200,
        "verified": true,
        "profilePicture": "https://pbs.twimg.com/profile_images/example.jpg"
      }
    }
  ],
  "has_next_page": true,
  "next_cursor": "DAACCgACGE..."
}
Related: Tweet Replies Export Workflow when you need saved CSV, JSON, or XLSX files, Tweet Quotes, Tweet Thread, Retweeters, and Favoriters.
Last modified on May 24, 2026