Export Twitter Replies With a Scraper API Guide

Export Twitter replies as CSV, JSON, or XLSX rows. Use reply_extractor for saved files with a defined result cap. Scrape Twitter replies through the live API when an application needs current pages. Send reply authors, text, media, and engagement counts downstream. Route rows to moderators, CRMs, warehouses, queues, or agents.

When to use this workflow

Spreadsheet export

Use reply_extractor plus CSV or XLSX export when analysts need reply rows.

App ingestion

Use reply_extractor plus paginated JSON results for queues, CRMs, or warehouses.

Moderation queue

Use the direct replies API plus JSON Lines rows before storing, hiding, labeling, or routing replies.

Latest page

Use GET /x/tweets/{id}/replies when you only need the newest reply page.

Cost control

Estimate the target tweet first, then set resultsLimit on create requests to cap the run.

Data you get

Reply exports include base user fields, reply tweet fields, engagement counts, and metadata when available.

Reply author

User ID, username, display name, follower count, verified state, and profile image.

Reply tweet

Tweet ID, tweet text, and tweet created time.

Engagement

Likes, reposts, replies, quotes, views, and bookmarks.

Metadata

Language, source app, and conversation ID.

For extraction jobs, GET /extractions/{id} returns job, results, hasMore, and nextCursor. Each reply row includes xUserId, xUsername, xDisplayName, tweetId, tweetText, tweetCreatedAt, createdAt, and optional enrichmentData fields such as likeCount, replyCount, repostCount, quoteCount, viewCount, bookmarkCount, conversationId, lang, and source.

End-to-end reply export handoff

Store one checkpoint that carries the target tweet through estimate, job creation, JSON pagination, and file export:

{
  "workflow": "reply_export",
  "request": {
    "toolType": "reply_extractor",
    "targetTweetId": "1893704267862470862",
    "resultsLimit": 500
  },
  "estimate": {
    "estimatedResults": 1200,
    "creditsRequired": "1200",
    "creditsAvailable": "77000",
    "allowed": true,
    "source": "replyCount"
  },
  "create_receipt": {
    "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
    "toolType": "reply_extractor",
    "status": "running",
    "poll_path": "/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  },
  "json_pages": {
    "limit": 1000,
    "page_cursor": null,
    "next_cursor": "990200",
    "has_more": true
  },
  "export_paths": {
    "csv": "/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=csv",
    "json": "/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=json",
    "xlsx": "/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=xlsx"
  },
  "normalized_row": {
    "parent_tweet_id": "1893704267862470862",
    "reply_tweet_id": "1893710452812718080",
    "reply_text": "Thanks for the update.",
    "reply_created_at": "2026-05-01T10:05:00.000Z",
    "reply_author_id": "44196397",
    "reply_author_username": "username",
    "conversation_id": "1893704267862470862",
    "export_format": "csv"
  },
  "handoff_state": "poll_until_completed_then_export"
}

Estimate checkpoint

Keep estimatedResults, creditsRequired, creditsAvailable, allowed, and source with targetTweetId; source is replyCount when the tweet count lookup succeeds.

Job checkpoint

Store the returned job id, status, and poll_path; do not expect reply rows in the create response.

Cursor checkpoint

Store page_cursor, next_cursor, and has_more for JSON page loops, then pass nextCursor back as after.

Export checkpoint

Store the chosen CSV, JSON, or XLSX export_paths and the normalized reply fields sent downstream.

Step 1: Estimate replies and credits

Call POST /extractions/estimate before scraping. reply_extractor requires targetTweetId. The estimate uses the tweet’s current replyCount, even when you plan to cap the created job.

curl -X POST https://xquik.com/api/v1/extractions/estimate \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "toolType": "reply_extractor",
    "targetTweetId": "1893704267862470862"
  }' | jq

The estimate returns allowed, estimatedResults, creditsRequired, creditsAvailable, and source. A successful tweet count lookup sets source to replyCount. Set resultsLimit on the create request when you want a smaller sample or hard run cap; final rows and credits can be lower than the estimate.

Step 2: Run the reply extraction

Create the job with the same toolType, targetTweetId, and optional resultsLimit.

curl -X POST https://xquik.com/api/v1/extractions \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "toolType": "reply_extractor",
    "targetTweetId": "1893704267862470862",
    "resultsLimit": 500
  }' | jq

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "toolType": "reply_extractor",
  "status": "running"
}

Store the creation response as a local handoff before polling:

{
  "job": "reply_extraction",
  "reply_extraction_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "target_tweet_id": "1893704267862470862",
  "results_limit": 500,
  "status": "running",
  "handoff_created_at": "2026-05-16T03:07:00.000Z"
}

Poll by reply_extraction_id; keep target_tweet_id and results_limit with the audit record. Do not wait for totalResults or createdAt in the create response; those fields arrive from GET /extractions/{id}.

Step 3: Poll job status

Poll GET /extractions/{id} until the job is completed or failed.

curl https://xquik.com/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890 \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

Use the paginated response when your app wants JSON rows instead of a file download. Use limit up to 1,000 and pass nextCursor as after until hasMore is false.

Step 4: Export CSV, JSON, or XLSX

File exports do not charge credits after job creation. Save xquik-replies.jsonl for queue replay or warehouse loads, xquik-replies.json for app ingestion, xquik-replies.csv for CRM import, and xquik-replies.xlsx for analyst handoff.

curl -X GET "https://xquik.com/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=csv" \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -o xquik-replies.csv

curl -X GET "https://xquik.com/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=xlsx" \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -o xquik-replies.xlsx

curl -X GET "https://xquik.com/api/v1/extractions/a1b2c3d4-e5f6-7890-abcd-ef1234567890/export?format=json" \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -o xquik-replies.json

Saved export JSON Lines handoff

Use this after format=json when a warehouse, queue, CRM, or AI agent needs one reply per line with stable field names.

jq -c --arg extraction_id "a1b2c3d4-e5f6-7890-abcd-ef1234567890" \
  '.[] | {
    job: "reply_export",
    extraction_id: $extraction_id,
    reply_tweet_id: .tweetId,
    reply_text: .tweetText,
    reply_author_id: .xUserId,
    reply_author_username: .xUsername,
    created_at: .tweetCreatedAt,
    conversation_id: .conversationId,
    like_count: .likeCount,
    reply_count: .replyCount,
    quote_count: .quoteCount,
    view_count: .viewCount,
    handoff_format: "jsonl"
  }' xquik-replies.json > xquik-replies.jsonl

Direct replies API

Use GET /x/tweets/{id}/replies when you need a paginated API response instead of a stored extraction job.

curl "https://xquik.com/api/v1/x/tweets/1893704267862470862/replies" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

The direct replies API returns tweets, has_next_page, and next_cursor. Pass next_cursor back as cursor to fetch the next page. It costs 1 credit per tweet returned. Use sinceTime and untilTime as Unix timestamps in seconds when a moderation queue, CRM sync, or agent only needs replies from a specific window.

curl -G https://xquik.com/api/v1/x/tweets/1893704267862470862/replies \
  --data-urlencode "sinceTime=1777392000" \
  --data-urlencode "untilTime=1777478400" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

Copy-ready workflow: replies to moderation queue

Use this direct API workflow when you need the latest reply pages as JSON Lines before deciding what to store, hide, label, or route. Each row maps the API response into stable downstream fields: handoff_source, parent_tweet_id, reply_tweet_id, reply_text, reply_author_id, reply_author_username, reply_author_name, reply_author_followers, reply_author_verified, reply_author_profile_picture, created_at, in_reply_to_id, conversation_id, engagement counts, bookmark_count, is_note_tweet, tweet_source, media_urls, and cursor fields.

const apiKey = process.env.XQUIK_API_KEY;
const tweetId = "1893704267862470862";
let cursor;
let pageIndex = 0;

do {
  const url = new URL(
    `https://xquik.com/api/v1/x/tweets/${tweetId}/replies`,
  );
  if (cursor) {
    url.searchParams.set("cursor", cursor);
  }

  const response = await fetch(url, {
    headers: { "x-api-key": apiKey },
  });

  if (response.status === 429) {
    throw new Error("Rate limited. Retry after the response header delay.");
  }
  if (!response.ok) {
    const body = await response.json();
    throw new Error(`${response.status} ${body.error}`);
  }

  const page = await response.json();
  for (const tweet of page.tweets ?? []) {
    const row = {
      handoff_source: "xquik.replies.direct",
      parent_tweet_id: tweetId,
      reply_tweet_id: tweet.id,
      reply_text: tweet.text,
      reply_author_id: tweet.author?.id ?? null,
      reply_author_username: tweet.author?.username ?? null,
      reply_author_name: tweet.author?.name ?? null,
      reply_author_followers: tweet.author?.followers ?? null,
      reply_author_verified: tweet.author?.verified ?? null,
      reply_author_profile_picture: tweet.author?.profilePicture ?? null,
      created_at: tweet.createdAt ?? null,
      in_reply_to_id: tweet.inReplyToId ?? null,
      conversation_id: tweet.conversationId ?? null,
      like_count: tweet.likeCount ?? 0,
      reply_count: tweet.replyCount ?? 0,
      retweet_count: tweet.retweetCount ?? 0,
      quote_count: tweet.quoteCount ?? 0,
      view_count: tweet.viewCount ?? 0,
      bookmark_count: tweet.bookmarkCount ?? 0,
      is_note_tweet: tweet.isNoteTweet ?? false,
      tweet_source: tweet.source ?? null,
      media_urls: (tweet.media ?? [])
        .map((item) => item.mediaUrl)
        .filter(Boolean),
      page_index: pageIndex,
      page_cursor: cursor ?? "",
      next_cursor: page.next_cursor,
      has_next_page: page.has_next_page,
    };
    process.stdout.write(JSON.stringify(row) + "\n");
  }

  cursor = page.has_next_page ? page.next_cursor : undefined;
  pageIndex += 1;
} while (cursor);

Use extraction jobs for saved files, credit estimates, or fixed resultsLimit caps.

Choose the right reply output

These frequently asked questions explain how to export replies. Preserve the original tweet, author, cursor, and engagement context.

How do replies differ from quote tweets?

Replies stay within conversation threads beneath the original tweet. Quote tweets create separate posts with added commentary. Store the original tweet ID with every reply row. Use the Quote Tweets API for quote tweets. Never merge both result sets without a field that identifies their relationship type.

Why can public replies be missing?

X can rank replies instead of showing them chronologically. It can also place probable spam behind an extra control. Protected, deleted, and hidden replies have separate visibility rules. Review the official X reply guidance. For API exports, follow every cursor and store each confirmed page. Treat a 424 replies_incomplete response as evidence against complete coverage.

How should a support team moderate reply rows?

Keep reply text, author ID, username, creation time, and engagement counts. Route uncertain rows to a human review queue. Add sentiment or spam labels with your own classifier. Xquik does not return a sentiment verdict. CSV keeps spreadsheet review user friendly. JSON preserves nested media and author fields.

When should I use the live replies API?

Use the Twitter reply API when an application needs the latest cursor page. It returns reply tweets, authors, engagement counts, media, and the next cursor. Continue until has_next_page is false. New replies can arrive during pagination. Store each reply tweet ID and remove duplicate IDs downstream.

When should I run a saved reply extraction?

Choose reply_extractor for stored files and reviewable jobs. Estimate the parent tweet first. Then create one capped or uncapped extraction. Poll the returned job ID until completion. File conversion adds no credit charge.

Which file format should I choose?

Choose CSV for CRM imports and spreadsheet filters. Choose XLSX for analyst handoffs that require workbook tools. Choose JSON for applications that preserve nested reply fields. Convert JSON to JSON Lines when queues or warehouses need one reply per record.

How do I resume an interrupted reply export?

Persist the target tweet ID, extraction ID, current cursor, next cursor, and page index. Resume a saved job through GET /extractions/{id}. Resume live pagination with the last confirmed next_cursor. Never advance the checkpoint before storing its reply rows.

How should I validate exported replies?

Each reply contributes to the conversation under the parent tweet. Check that every row has a reply tweet ID and parent tweet ID. Preserve author IDs separately from usernames because usernames can change. Keep tweet creation times in UTC. Compare the returned rows with the estimate only for planning. The parent replyCount can change and does not guarantee the final export size.

Cost and failure handling

Estimate is free. A reply_extractor job costs 1 credit per result. Direct GET /x/tweets/{id}/replies calls cost 1 credit per returned tweet. Available credits can reduce the returned page size. File exports do not charge credits after job creation. Respect the read rate limit on live Twitter API pages. Use the parent reply count only for estimates. Treat returned reply rows as the source of truth. Handle common errors before retrying:

400 invalid tweet ID

Status 400. Error invalid_tweet_id. Use a numeric tweet ID.

401 unauthenticated

Status 401. Error unauthenticated. Send a valid x-api-key.

402 billing or credits

Status 402. Errors no_subscription, subscription_inactive, no_credits, or insufficient_credits. Subscribe, add credits, or lower resultsLimit.

429 rate limit

Status 429. Error rate_limit_exceeded. Wait for retryAfter or the Retry-After header.

424 or 502 upstream unavailable

Status 424 or 502. Error x_api_unavailable. Retry with exponential backoff.

Handoff checklist

Spreadsheet

Export format=csv to xquik-replies.csv or format=xlsx to xquik-replies.xlsx.

App ingestion

Export format=json to xquik-replies.json, convert it to xquik-replies.jsonl, or paginate GET /extractions/{id}.

Cost control

Set resultsLimit on create calls when you need a smaller run.

New reply alerts

Create an account or keyword monitor with tweet.reply events.

​When to use this workflow

Spreadsheet export

App ingestion

Moderation queue

Latest page

Cost control

​Data you get

Reply author

Reply tweet

Engagement

Metadata

​End-to-end reply export handoff

Estimate checkpoint

Job checkpoint

Cursor checkpoint

Export checkpoint

​Step 1: Estimate replies and credits

​Step 2: Run the reply extraction

​Step 3: Poll job status

​Step 4: Export CSV, JSON, or XLSX

​Saved export JSON Lines handoff

​Direct replies API

​Copy-ready workflow: replies to moderation queue

​Choose the right reply output

​How do replies differ from quote tweets?

​Why can public replies be missing?

​How should a support team moderate reply rows?

​When should I use the live replies API?

​When should I run a saved reply extraction?

​Which file format should I choose?

​How do I resume an interrupted reply export?

​How should I validate exported replies?

​Cost and failure handling

400 invalid tweet ID

401 unauthenticated

402 billing or credits

429 rate limit

424 or 502 upstream unavailable

​Handoff checklist

Spreadsheet

App ingestion

Cost control

New reply alerts

​Related reply APIs

When to use this workflow

Data you get

End-to-end reply export handoff

Step 1: Estimate replies and credits

Step 2: Run the reply extraction

Step 3: Poll job status

Step 4: Export CSV, JSON, or XLSX

Saved export JSON Lines handoff

Direct replies API

Copy-ready workflow: replies to moderation queue

Choose the right reply output

How do replies differ from quote tweets?

Why can public replies be missing?

How should a support team moderate reply rows?

When should I use the live replies API?

When should I run a saved reply extraction?

Which file format should I choose?

How do I resume an interrupted reply export?

How should I validate exported replies?

Cost and failure handling

Handoff checklist

Related reply APIs