X (Twitter) Follower Scraper | $0.15/1K | Pay-Per Result

Scrape X (Twitter) followers, following, verified followers, list members, list subscribers and community members at scale for just $0.15 per 1,000 profiles. No X API key needed, no rate limits, no login required. Built by Xquik.

What does X Follower Scraper do?

X Follower Scraper extracts complete profile data for the followers, following, list members, list subscribers and community members of any public X (formerly Twitter) account. It returns structured JSON ready for audience analysis, lead generation, competitor research, or integration into your pipeline.

What can this scraper do?

• Scrape X followers - paste a profile URL like https://x.com/nasa/followers and export every follower profile
• Scrape X following - paste https://x.com/nasa/following to export every account a user follows
• Scrape X verified followers only - paste https://x.com/nasa/verified_followers to target only Premium / verified accounts
• Scrape X list members - paste a list URL like https://x.com/i/lists/1748648376080666720/members to export everyone on the list
• Scrape X list subscribers - export users who follow a list via https://x.com/i/lists/<id>/followers
• Scrape X community members - export members of any public X Community via https://x.com/i/communities/<id>/members
• Bulk X profile follower scraper - pass an array of handles like ["elonmusk", "nasa"] and scrape many targets in one run
• Server-side filters - apply minFollowers, verifiedOnly, bioContains, locationContains filters on our side so you only pay for profiles that match
• Dedup across targets - for overlap analysis between competitors or lists
• Per-target attribution - every row carries sourceTarget, sourceRelation and sourceUrl so you always know where a profile came from

What data can X Follower Scraper extract?

Field	Description
id	Numeric X user ID
username	Handle (without @)
name	Display name
description	Bio text
followers	Follower count
following	Following count
statusesCount	Total tweets posted
mediaCount	Total media uploaded
favouritesCount	Total likes given
verified	Verified (Premium) flag
verifiedType	blue, business, government, or none
location	Self-reported location
url	Website URL from profile
profilePicture	Avatar URL (full-size)
coverPicture	Banner URL
createdAt	Account creation timestamp (ISO 8601)
canDm	Whether the account accepts DMs
sourceTarget	Handle / ID you scraped this profile from
sourceRelation	Relation: followers, following, list_members, ...
sourceUrl	Exact URL the profile was discovered on

Set outputMode: "full" to also get every raw field from the profile payload (entities, pinned tweet, professional info, affiliates, etc.) alongside the compact fields above.

Why scrape X followers?

• Lead generation - pull the followers of a competitor or niche influencer and build a targeted outreach list
• Audience analysis - understand who follows you vs a competitor, spot overlap, find lookalike prospects
• Influencer discovery - filter followers by minFollowers and verifiedOnly to surface the most influential people in any community
• Competitor research - export a rival brand's follower base, segment by bio keyword, location, or engagement proxies
• Community research - export the members of any X Community for academic, market, or product research
• List auditing - verify who is on a curated X list and how the list has grown
• Retargeting seeds - build follower-based audiences for downstream ad, email, or outreach campaigns
• Academic research - build social-network datasets for trend analysis, NLP training, or sociological study

All runs on Apify's platform with built-in scheduling, webhooks, API access, integrations (Make, n8n, Zapier), proxy rotation, and dataset export in JSON, CSV, Excel, or HTML.

How much does it cost to scrape X followers?

Profiles	Cost
1,000	$0.15
10,000	$1.50
100,000	$15.00
1,000,000	$150

You pay for rows written to your dataset at $0.15 per 1,000 rows. No subscriptions, no hidden fees, no start fee. Platform usage is included.

• Never charged for filtered-out profiles. Server-side filters (minFollowers, verifiedOnly, bioContains, locationContains, minAccountAgeDays, hasWebsite, hasLocation) run before a profile enters your dataset.
• Never charged for duplicates. When dedupeAcrossTargets: true, repeats are dropped before the dataset write.
• Never charged for data not delivered. On timeout or hard failure, already-fetched profiles are flushed and the run exits cleanly; anything the Actor never pushed, you never pay for.
• One diagnostic row per empty run. When a run produces no profiles (no input, invalid handles, or zero matches after filters), the actor writes a single structured row that explains why, so you always know what happened. This costs $0.00015 per empty run on paid plans (one-fifteen-thousandth of a cent). Diagnostic rows carry a status field (no-input, invalid-input, or zero-output) and are easy to filter out with dataset.filter(r => !r.status).

Set ACTOR_MAX_TOTAL_CHARGE_USD in Apify run options to hard-cap spend. The Actor respects it strictly.

How do I use X Follower Scraper to scrape follower data?

1. Paste profile or list URLs

Paste any mix of profile, list, or community URLs and the scraper routes each to the correct endpoint automatically:

{
  "startUrls": [
    "https://x.com/nasa/followers",
    "https://x.com/spacex/verified_followers",
    "https://x.com/elonmusk/following",
    "https://x.com/i/lists/1748648376080666720/members",
    "https://x.com/i/communities/1493446837214187523/members"
  ],
  "maxItems": 5000
}

2. Bulk handles

Shorthand for many /<handle>/followers targets. Usernames accept @ or no prefix:

{
  "twitterHandles": ["elonmusk", "nasa", "openai"],
  "relation": "followers",
  "maxItems": 1000
}

Set relation to followers, following, or verified_followers to switch what is scraped for every handle.

3. Scrape by numeric user, list, or community IDs

{
  "userIds": ["44196397"],
  "listIds": ["1748648376080666720"],
  "communityIds": ["1493446837214187523"],
  "relation": "followers",
  "maxItems": 2000
}

4. Filter before you pay

Apply server-side filters so only matching profiles enter your dataset:

{
  "twitterHandles": ["openai"],
  "relation": "followers",
  "minFollowers": 1000,
  "verifiedOnly": true,
  "bioContains": "founder",
  "locationContains": "San Francisco",
  "maxItems": 500
}

Raw profiles fetched may be 10-100x more than rows billed - you only pay for the rows that pass every filter.

Accepted URL shapes

URL	Relation
https://x.com/<handle>/followers	followers
https://x.com/<handle>/verified_followers	verified_followers
https://x.com/<handle>/following	following
https://x.com/<handle>	default relation (followers if unset)
https://x.com/i/lists/<id>/members	list_members
https://x.com/i/lists/<id>/followers	list_followers
https://x.com/i/lists/<id>	list_members
https://x.com/i/communities/<id>/members	community_members
https://x.com/i/communities/<id>	community_members

twitter.com and mobile.twitter.com are also accepted everywhere.

Input

See the Input tab for the complete list of options. All fields are optional except at least one of: startUrls, twitterHandles, userIds, listIds, or communityIds.

Common patterns:

• Competitor follower export - add the competitor handle to twitterHandles with relation: "followers"
• Verified-only lead list - paste https://x.com/<handle>/verified_followers into Start URLs
• List audit - paste the list URL into Start URLs
• Multi-account overlap - add 2+ handles, set dedupeAcrossTargets: true to keep only shared followers

Output

Each profile is a JSON object. Compact mode (default) returns 17 normalized fields:

{
  "schemaVersion": 1,
  "_schema_version": 1,
  "id": "44196397",
  "username": "elonmusk",
  "name": "Elon Musk",
  "description": "...",
  "followers": 180000000,
  "following": 500,
  "statusesCount": 42000,
  "mediaCount": 3200,
  "favouritesCount": 120000,
  "verified": true,
  "verifiedType": "blue",
  "location": "...",
  "url": "https://...",
  "profilePicture": "https://...",
  "coverPicture": "https://...",
  "createdAt": "2009-06-02T20:12:29Z",
  "canDm": true,
  "sourceTarget": "nasa",
  "sourceRelation": "followers",
  "sourceUrl": "https://x.com/nasa/followers"
}

Export as JSON, CSV, Excel, or HTML from the Apify dataset.

Tips & advanced options

• Cut costs - set maxItems and maxItemsPerTarget to the exact number you need. Extra profiles cost extra.
• Filter before you pay - combine minFollowers, verifiedOnly, bioContains, locationContains to narrow the billed dataset.
• Dedup - set dedupeAcrossTargets: true when scraping multiple competitor handles to get only unique profiles across all targets.
• Overlap analysis - run two competitor handles with dedupeAcrossTargets: false to analyze shared vs unique audience in post-processing.
• Full profile payload - set outputMode: "full" to get every raw field including pinned tweet, entities, professional, and affiliates.
• Real-time monitoring - for ongoing monitoring of new followers, use the Xquik API webhooks. They cost less than repeated Actor runs for watch-style workloads.

Use cases

• Lead generation - export competitor followers and build targeted lists
• Audience research - analyze who follows you, a competitor, or an influencer
• Influencer discovery - filter by follower count and verification to find the most influential people in any niche
• Community growth - export members of relevant X Communities for outreach
• Academic research - build large-scale social-network datasets
• Marketing intelligence - segment follower bases by bio keyword, location, or profile type

Why X Follower Scraper vs other follower scrapers?

Feature	X Follower Scraper	Other top scrapers
Price per 1,000 profiles	$0.15	$0.10 to $5.00
Followers / following	Yes	Yes
Verified followers (Premium-only)	Yes	Rare
List members & list subscribers	Yes	Rare
Community members	Yes	Rare
Server-side filters	Yes (7 filters)	No
Diagnostic row on empty runs	Yes	No (silent empty)
Mix URLs, handles, IDs in one run	Yes	No
Per-target attribution on rows	Yes	No
Dedup across targets	Yes	No
No X API key required	Yes	Yes
Export JSON, CSV, Excel, HTML	Yes	Yes
Part of full X automation suite	Yes (Xquik)	No

Is it legal to scrape X (Twitter) followers?

Our Actors are ethical and do not extract any private user data, such as email addresses, gender, or location beyond what the user has chosen to publish. They only extract what the user has chosen to share publicly on X. We therefore believe that our Actors, when used for ethical purposes by Apify users, are safe. However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

Related Actors

• X Tweet Scraper - scrape tweets, engagement metrics, author profiles, and media with 40+ advanced search filters at $0.15 per 1,000 tweets

---

If this scraper saves you time, a short review on the Apify Store helps other users find it. Thanks!

---

Need more than scraping?

Xquik is a full X automation platform with 40+ tools, a REST API, webhooks, and an MCP server for AI agents.

• API Documentation - full REST API with 70+ endpoints
• Followers API - the endpoint powering this Actor
• Following API - get who a user follows
• List Members API - export any X list
• MCP Server - connect X data to AI agents (Claude, GPT, etc.)
• Webhooks - real-time event delivery for new followers / unfollows
• GitHub - source code and issue tracker

FAQ

Do I need a Twitter/X API key? No. This scraper uses its own infrastructure. No login or credentials required.

Is there a rate limit? No. Scrape as many profiles as you need.

How fast is it? Typically 20-50 profiles per second depending on account size and filter settings.

Why is my run returning fewer rows than maxItems? Because server-side filters (minFollowers, verifiedOnly, bioContains, etc.) are applied before counting. Raw profiles fetched may be 10-100x more than rows pushed. Relax filters if you want more results.

How many followers can I scrape from a single account? Large accounts (millions of followers) can be scraped, but X paginates in batches. Use maxItemsPerTarget to chunk very large targets across multiple runs.

Does the Actor retry on 429 / Cloudflare / timeout? Yes. 3 attempts per page with exponential backoff. Partial results are preserved on hard failures.

What happens if the run hits the Apify timeout? The Actor detects it 15 seconds early, flushes everything already fetched, and exits cleanly with a Partial: ... status message. You are never billed for data not delivered.

Can I resume where I left off? Not yet. Coming in a future version via sinceCursor. For now, use maxItemsPerTarget to chunk large runs.

Can I use the Apify API to run this? Yes. See the API tab for integration examples in Python, JavaScript, cURL, and more.

Can I schedule recurring scrapes? Yes. Use Apify's built-in scheduling to run this Actor on a cron and watch for new followers over time.

Where do I report issues? Open an issue on GitHub or use the Issues tab on this Actor's page. Most issues are answered within 4 hours.

Can I get a custom solution? Yes. Visit xquik.com or check the API docs for direct API access with more endpoints and features.