Twitter Follower Scraper: Export Twitter Followers

Download a Twitter follower list as CSV, XLSX, or JSON. Keep each Twitter profile ID, username, bio, verification status, image, and audience count. Import the follower rows into a CRM, spreadsheet, queue, or warehouse.

Twitter Follower Export Questions

Download Follower List Twitter

Run follower_explorer when you need a saved follower export. Use it as a Twitter follower tracker for repeatable account snapshots. Estimate credits before starting. Keep the source username and resolved user ID while polling the job to completion.

File Formats & Follower Fields

Download CSV for CRM lists or spreadsheet imports. Choose XLSX for analyst review and JSON for queues. Use the user ID as each stored profile’s deduplication key. Keep follower counts, following counts, verification, collection time, and the applied result limit. Mark any interrupted export as bounded.

Export Twitter Followers API

Use POST /api/v1/extractions for a saved follower export. Supply the public username and follower_explorer. A defined resultsLimit bounds each large export. Use GET /api/v1/x/users/{id}/followers for current profile pages. That route returns users, has_next_page, and next_cursor.

Cursor, API Key & Rate-Limit Rules

Treat next_cursor as opaque. Persist every follower page before saving its cursor. Scope API access to the worker that owns each cursor. Keep the API key outside exported lists. Handle each documented rate limit and error status. Use the user ID to deduplicate retries. Store a timestamp for each collected follower page in its UTC collection record.

What API Can I Use to Get Someone’s Twitter Followers?

Resolve the public profile’s stable ID before calling the live Followers API contract. Use follower_explorer for a saved export or list.

Public Profile Boundaries

A private account does not make its followers public. Confirm the Twitter profile is public before requesting follower pages. A missing page does not prove that a profile is private. Save each username, stable ID, and cursor. Record when each page was collected. Request another page only after the current profiles become durable. Respect API key scope, credits, and every returned rate limit.

How Do I Export All Followers of a Twitter Account?

Estimate the public profile first. Confirm credits and set resultsLimit before creating the follower export. Poll the job until completion or failure. Save each returned list page before its cursor.

Completeness & Reconciliation

Deduplicate profiles by stable user ID after retries. Call the result a full list only when pagination ends normally. Label exports with fewer profiles as bounded. Record the source username, first cursor, final cursor, unique row count, and completion time. Follower totals may change during collection.

Twitter Followers Scraper

Choose the saved Twitter followers scraper for estimates and reusable files. Use it as a Twitter follower tracker for repeatable account snapshots. Choose the live follower API for low-latency profile pages.

Returned Profile Fields

Each Twitter profile includes a user ID and username. It may include a bio and verification. It may also include follower counts, following counts, location, and profile images. Keep every API key scoped. Respect the read rate limit. Store cursors with their source profile. Never restart pagination under another username.

How Can I Scrape Twitter Followers for a Specific Account?

Supply one public username to follower_explorer. Estimate credits, create one job, and poll its returned ID. Export completed follower rows as CSV, JSON, or XLSX.

Specific Account Checkpoints

Use the live API for current profile pages. Persist each list before its opaque cursor. Use numeric user IDs to deduplicate retries. Store the mutable username, bio, follower count, following count, and verification. Stop at a documented limit. Never infer private followers from an incomplete page. The final checkpoint records when the export completed.

Export List of Twitter Followers to CSV or Excel

Use follower_explorer when exporting a Twitter follower list. Choose CSV for CRM imports and Excel-compatible XLSX for analyst review. Choose JSON for queue, warehouse, or application ingestion.

CSV, Excel & CRM Mapping

Map User ID to the CRM’s unique profile field. Keep username, follower count, following count, verification, and bio as mutable values. Store the source account and extraction ID. Record every row cap in the file’s import record. Save rejected import rows. Paginated JSON supports custom jobs that process large follower lists.

Can I Export Twitter Followers to a Spreadsheet Automatically?

Schedule estimate, create, poll, and export steps with an SDK or CLI. A no-code workflow must store the extraction ID. Use the n8n workflow guide for scheduled follower exports.

Spreadsheet Automation Safety

Download CSV or XLSX for review. Keep each API key outside spreadsheet cells. Handle every returned rate limit. Never duplicate an uncertain create request. Store the source username, user ID, cursor, row cap, output path, and import result. Never assume a free tier.

Can I Scrape Twitter Followers With Python Scripts?

Use Python requests with documented Xquik follower endpoints. Call the live API when the script can persist every opaque cursor. Call extraction routes for saved CSV, JSON, or XLSX exports.

Python Error & Output Handling

Browser web scrapers may need cookies. Xquik operates independently from every official API documented by X. The official Twitter API and Xquik use separate contracts. Keep the API key outside source files. Check 402, 424, 429, and 502 before retrying. Normalize each profile by its stable numeric ID. Write one follower per JSON Lines record. Store the username, list source, and UTC collection value.

What Are the Risks of Twitter Follower Scraping Tools?

Risks include partial follower pages, duplicate profiles, and exposed API keys. A repeated cursor can leave the follower list incomplete. Scraped data represents public follower profiles within the requested page boundaries.

Follower Scraper Risk Controls

Never infer consent from a bio. Private accounts do not expose follower lists. Do not infer inactive accounts from missing pages or unchanged follower counts. Store each user ID beside its mutable username. Mark rate-limit, credit, or result boundaries. Review export columns before every CRM import.

How Do I Get Public Follower Lists Responsibly?

Public data includes documented profile fields from the requested public accounts. Keep only fields needed by the export’s social media workflow. Review the X Terms of Service at https://x.com.

Responsible Export Checklist

Follow applicable laws, retention rules, and deletion requests. Restrict API access and every follower export to its intended reviewers. Store the source profile, user ID, username, cursor, collection time, and documented boundary. This technical guide is not legal advice. Xquik is an independent third-party service. Not affiliated with X Corp. “Twitter” and “X” are trademarks of X Corp.

Can I Download My Own X Archive Instead?

X calls its signed-in setting Download an archive of your data. Follow the official X archive instructions to create your account backup.

X Archive vs. Follower Export

The ZIP can include profile details, posts, media, followers, following, and Lists. It contains HTML and JSON, not a cursor-based API or CRM-ready CSV export. Use Xquik for repeatable public follower exports with defined row limits. Keep the source user ID and username. Private archives remain available only to their account owners. Record each downstream file’s source.

Outcome

1. Estimate

Call POST /extractions/estimate with follower_explorer to check credits and projected row count.

2. Extract

Call POST /extractions with targetUsername and optional resultsLimit to start the async job.

3. Retrieve

Call GET /extractions/{id} when a custom pipeline needs paginated JSON rows.

4. Export

Call GET /extractions/{id}/export?format=csv, format=json, or format=xlsx for CRM files; md, md-document, pdf, and txt are also supported. Exports are free and capped at 100,000 rows per extraction. PDF supports up to 10,000 rows.

5. Import

Map User ID to a CRM unique field for imports, upserts, segments, or warehouse loads.

Choose the right path

Saved follower export

Use POST /extractions/estimate, then POST /extractions with follower_explorer when you need a reusable job ID, cost preview, and CSV/JSON/XLSX files.

Paginated saved rows

Use GET /extractions/{id}?limit=1000&after={nextCursor} when a CRM sync, warehouse load, queue, or agent needs saved JSON pages.

Live follower page

Use GET /x/users/{id}/followers?pageSize=200&cursor={next_cursor} when you need the current follower page without creating an extraction job. Use it for a CRM enrichment job, queue worker, audience sync, or agent.

Shell or SDK handoff

Use CLI, TypeScript, Python, or Go SDK when scheduled imports need code-owned JSON Lines, CSV, or XLSX files.

End-to-end follower export handoff

{
  "workflow": "follower_export_crm",
  "request": {
    "toolType": "follower_explorer",
    "targetUsername": "elonmusk",
    "resultsLimit": 10000
  },
  "estimate": {
    "estimatedResults": 10000,
    "creditsRequired": "10000",
    "creditsAvailable": "77000",
    "allowed": true,
    "source": "resultsLimit",
    "resolvedXUserId": "44196397"
  },
  "create_receipt": {
    "id": "77777",
    "toolType": "follower_explorer",
    "status": "running",
    "poll_path": "/api/v1/extractions/77777"
  },
  "json_pages": {
    "limit": 1000,
    "page_cursor": null,
    "next_cursor": "1001",
    "has_more": true
  },
  "export_paths": {
    "csv": "/api/v1/extractions/77777/export?format=csv",
    "json": "/api/v1/extractions/77777/export?format=json",
    "xlsx": "/api/v1/extractions/77777/export?format=xlsx"
  },
  "normalized_row": {
    "x_user_id": "44196397",
    "x_username": "username",
    "display_name": "Xquik",
    "followers_count": 2400,
    "verified": true,
    "profile_image_url": "https://pbs.twimg.com/profile_images/xquik.jpg",
    "bio": "X automation platform",
    "location": "San Francisco",
    "account_created_at": "2021-03-01T12:00:00.000Z"
  },
  "crm_import": {
    "unique_field": "x_user_id",
    "upsert_mode": "external_id",
    "file_format": "csv",
    "file_path": "x-followers-elonmusk.csv"
  },
  "handoff_state": "poll_until_completed_then_export"
}

Estimate checkpoint

Keep estimatedResults, creditsRequired, creditsAvailable, allowed, source, and resolvedXUserId; source is followers unless resultsLimit is lower than the follower count. When the account has fewer followers than resultsLimit, the estimate keeps source: "followers" and uses the smaller follower count.

Job checkpoint

Store the returned job id, status, and poll_path; do not expect follower rows in the create response. Store extractionHandoff in your job table. Poll by extraction_id. Keep source_username and results_limit for audit.

Cursor checkpoint

Every result guarantees id and xUserId. The API omits optional profile and enrichment fields when absent. Use limit up to 1000. Pass nextCursor as after until hasMore becomes false.

CRM checkpoint

Map xUserId to x_user_id. Store CSV, JSON, or XLSX export_paths and the CRM unique_field. Use the local -o path, exportFilePath, or export_file_path as the durable handoff value.

Live follower page handoff

cURL

curl "https://xquik.com/api/v1/x/users/44196397/followers?pageSize=200&cursor=DAACCgACGRElMJcAAA" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

Page checkpoint

The response returns users, has_next_page, and next_cursor. Treat next_cursor as opaque. Never treat cursor as a stable follower ID.

Identity

Map users[].id to x_user_id, users[].username to x_username, and users[].name to display_name.

Audience fields

Map optional followers, following, statusesCount, verified, and verifiedType for scoring or segments.

Profile context

Map optional description, location, url, profilePicture, and coverPicture. Map users[].createdAt to account_created_at when returned.

Credit-aware pages

pageSize accepts 20 to 200, but paid calls can return fewer users when remaining credits are lower than the requested page. If no result can be afforded, the endpoint returns 402 insufficient_credits; lower pageSize or add credits before retrying.

{
  "job": "direct_follower_page",
  "source_x_user_id": "44196397",
  "page_size_requested": 200,
  "rows_returned": 200,
  "cursor_used": "DAACCgACGRElMJcAAA",
  "next_cursor": "DAACCgACGE...",
  "has_next_page": true,
  "fetched_at": "2026-05-16T16:50:00.000Z",
  "page_checkpoint": "44196397:DAACCgACGE..."
}

Step 1: Estimate cost

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": "follower_explorer",
    "targetUsername": "elonmusk",
    "resultsLimit": 10000
  }' | jq

const estimate = await fetch("https://xquik.com/api/v1/extractions/estimate", {
  method: "POST",
  headers: {
    "x-api-key": "xq_YOUR_KEY_HERE",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    toolType: "follower_explorer",
    targetUsername: "elonmusk",
    resultsLimit: 10000,
  }),
}).then((response) => response.json());

if (!estimate.allowed) {
  throw new Error(
    `Need ${estimate.creditsRequired} credits, have ${estimate.creditsAvailable}`,
  );
}

import requests

estimate = requests.post(
    "https://xquik.com/api/v1/extractions/estimate",
    headers={"x-api-key": "xq_YOUR_KEY_HERE"},
    json={
        "toolType": "follower_explorer",
        "targetUsername": "elonmusk",
        "resultsLimit": 10000,
    },
).json()

if not estimate["allowed"]:
    raise RuntimeError(
        f"Need {estimate['creditsRequired']} credits, have {estimate['creditsAvailable']}"
    )

{
  "allowed": true,
  "creditsRequired": "10000",
  "creditsAvailable": "77000",
  "estimatedResults": 10000,
  "source": "resultsLimit",
  "resolvedXUserId": "44196397"
}

Step 2: Start the extraction

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

const job = await fetch("https://xquik.com/api/v1/extractions", {
  method: "POST",
  headers: {
    "x-api-key": "xq_YOUR_KEY_HERE",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    toolType: "follower_explorer",
    targetUsername: "elonmusk",
    resultsLimit: 10000,
  }),
}).then((response) => response.json());

const extractionHandoff = {
  extraction_id: job.id,
  status: job.status,
  source_username: "elonmusk",
  results_limit: 10000,
  handoff_created_at: new Date().toISOString(),
};

{
  "id": "77777",
  "toolType": "follower_explorer",
  "status": "running"
}

Step 3: Poll until complete

cURL

curl -s "https://xquik.com/api/v1/extractions/77777?limit=1000" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

Paginated JSON handoff

{
  "job": {
    "id": "77777",
    "toolType": "follower_explorer",
    "status": "completed",
    "totalResults": 10000,
    "targetUsername": "elonmusk",
    "createdAt": "2026-05-08T13:46:00.000Z",
    "completedAt": "2026-05-08T13:51:00.000Z"
  },
  "results": [
    {
      "id": "1001",
      "xUserId": "44196397",
      "xUsername": "username",
      "xDisplayName": "Xquik",
      "xFollowersCount": 2400,
      "xVerified": true,
      "xProfileImageUrl": "https://pbs.twimg.com/profile_images/xquik.jpg",
      "enrichmentData": {
        "user": {
          "followingCount": 120,
          "statusesCount": 830,
          "description": "X automation platform",
          "location": "San Francisco",
          "coverPicture": "https://pbs.twimg.com/profile_banners/xquik"
        },
        "tweet": {}
      },
      "createdAt": "2026-05-08T13:51:00.000Z"
    }
  ],
  "hasMore": true,
  "nextCursor": "1001"
}

Normalize each follower row before sending it downstream:

{
  "job": "follower_export",
  "source_username": "elonmusk",
  "result_id": "1001",
  "x_user_id": "44196397",
  "x_username": "username",
  "display_name": "Xquik",
  "followers_count": 2400,
  "verified": true,
  "profile_image_url": "https://pbs.twimg.com/profile_images/xquik.jpg",
  "bio": "X automation platform",
  "location": "San Francisco",
  "handoff_format": "json"
}

Step 4: Export Twitter Follower List in CSV Format

curl -s "https://xquik.com/api/v1/extractions/77777/export?format=csv" \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -o x-followers-elonmusk.csv

import { writeFile } from "node:fs/promises";

const extractionId = "77777";
const exportFilePath = "x-followers-elonmusk.csv";
const response = await fetch(
  `https://xquik.com/api/v1/extractions/${extractionId}/export?format=csv`,
  { headers: { "x-api-key": "xq_YOUR_KEY_HERE" } },
);

if (!response.ok) {
  throw new Error(`Export failed with ${response.status}`);
}

const bytes = Buffer.from(await response.arrayBuffer());
await writeFile(exportFilePath, bytes);

const exportHandoff = {
  extraction_id: extractionId,
  source_username: "elonmusk",
  export_format: "csv",
  export_file_path: exportFilePath,
  content_disposition: response.headers.get("Content-Disposition") ?? "",
  handoff_created_at: new Date().toISOString(),
};

extraction_id = "77777"
export_file_path = "x-followers-elonmusk.csv"
response = requests.get(
    f"https://xquik.com/api/v1/extractions/{extraction_id}/export",
    headers={"x-api-key": "xq_YOUR_KEY_HERE"},
    params={"format": "csv"},
)
response.raise_for_status()

with open(export_file_path, "wb") as file:
    file.write(response.content)

{
  "job": "follower_export_file",
  "extraction_id": "77777",
  "source_username": "elonmusk",
  "export_format": "csv",
  "export_file_path": "x-followers-elonmusk.csv",
  "handoff_format": "file"
}

CRM field mapping

Stable account key

Map export column User ID to x_user_id as the custom unique field. Use it for CRM upserts because it is the stable X account identifier.

Handle and display name

Map Username to x_username or a social profile field, and map Display Name to display_name for triage and human review.

Audience metrics

Map Followers to followers_count, Following to following_count, and Posts to posts_count for segmentation, scoring, and reporting.

Verification flag

Map Verified to verified so lead scoring, audience filters, and reviewer queues can separate verified accounts.

Profile context

Map Description to a bio or notes field, and map Location to a regional field. Treat both as mutable enrichment, not identity.

Profile media

Map Profile Image to an avatar URL field and Cover Picture to a banner URL field for internal views that show account context.

Import and upsert rules

HubSpot import docs

Check file requirements, unique identifier rules, and supported spreadsheet formats before importing.

Salesforce Bulk API 2.0

Use CSV upserts with an external ID field when loading large contact or lead datasets.

Automation handoff

Use this handoff when the export runs on a schedule:

Store the Xquik extraction ID and source username in your job table.
Poll GET /extractions/{id} until the API returns completed.
Download format=json for code pipelines or format=csv for CRM import tools.
Upsert by x_user_id, not by display name or username.
Save the Xquik job ID, export format, export file path, row count, and import result for audit.
For JSON Lines, write one normalized follower object per line to xquik-follower-export.jsonl.

Extraction workflow

Estimate costs, run jobs, paginate results, and export files.

Followers API

Fetch one live follower page with users, has_next_page, and next_cursor.

n8n guide

Send extraction rows into Sheets, Slack, and downstream automation.

Rate limits

Apply read rate limits to direct follower pages and retry 429 responses.

​Twitter Follower Export Questions

​Download Follower List Twitter

​Export Twitter Followers API

​What API Can I Use to Get Someone’s Twitter Followers?

​How Do I Export All Followers of a Twitter Account?

​Twitter Followers Scraper

​How Can I Scrape Twitter Followers for a Specific Account?

​Export List of Twitter Followers to CSV or Excel

​Can I Export Twitter Followers to a Spreadsheet Automatically?

​Can I Scrape Twitter Followers With Python Scripts?

​What Are the Risks of Twitter Follower Scraping Tools?

​How Do I Get Public Follower Lists Responsibly?

​Can I Download My Own X Archive Instead?

​Outcome

1. Estimate

2. Extract

3. Retrieve

4. Export

5. Import

​Choose the right path

Saved follower export

Paginated saved rows

Live follower page

Shell or SDK handoff

​End-to-end follower export handoff

Estimate checkpoint

Job checkpoint

Cursor checkpoint

CRM checkpoint

​Live follower page handoff

Page checkpoint

Identity

Audience fields

Profile context

Credit-aware pages

​Step 1: Estimate cost

​Step 2: Start the extraction

​Step 3: Poll until complete

​Paginated JSON handoff

​Step 4: Export Twitter Follower List in CSV Format

​CRM field mapping

Stable account key

Handle and display name

Audience metrics

Verification flag

Profile context

Profile media

​Import and upsert rules

HubSpot import docs

Salesforce Bulk API 2.0

​Automation handoff

​Related

Extraction workflow

Followers API

n8n guide

Rate limits

Twitter Follower Export Questions

Download Follower List Twitter

Export Twitter Followers API

What API Can I Use to Get Someone’s Twitter Followers?

How Do I Export All Followers of a Twitter Account?

Twitter Followers Scraper

How Can I Scrape Twitter Followers for a Specific Account?

Export List of Twitter Followers to CSV or Excel

Can I Export Twitter Followers to a Spreadsheet Automatically?

Can I Scrape Twitter Followers With Python Scripts?

What Are the Risks of Twitter Follower Scraping Tools?

How Do I Get Public Follower Lists Responsibly?

Can I Download My Own X Archive Instead?

Outcome

Choose the right path

End-to-end follower export handoff

Live follower page handoff

Step 1: Estimate cost

Step 2: Start the extraction

Step 3: Poll until complete

Paginated JSON handoff

Step 4: Export Twitter Follower List in CSV Format

CRM field mapping

Import and upsert rules

Automation handoff

Related