Twitter (X) Follower Scraper | $0.1 / 1K + Usage | Followers & Following | Up to 5,000,000

Need a high-scale Twitter/X follower scraper that can collect both followers and following fast, stream results in real time, and stay cost-efficient for large runs? This actor is built for exactly that.

It supports scraping by:

• Twitter/X username list
• Twitter/X user ID list

And lets you collect:

• Followers
• Following (friends)
• Usernames or numeric user IDs as output

Why this Twitter follower scraper

• Low cost: $0.1 per 1,000 users (plus Apify platform usage)
• High-volume support: up to 5,000,000 followers and 5,000,000 following per request
• Live streamed output: results appear in dataset progressively, not only after run completion
• Scalable backend architecture: queue + token rotation + multi-worker execution
• Flexible targeting: usernames and/or user IDs in the same run
• Built for growth teams: outreach, market intelligence, social graph analytics

Best use cases

This X/Twitter scraper is ideal for:

• Lead generation pipelines
• Influencer discovery and vetting
• Competitor audience analysis
• Account expansion and lookalike discovery
• Social graph enrichment for CRM/data warehouse
• Marketing audience research and segmentation

Input fields (Apify form)

Core fields:

• Twitter Usernames (without @): array of usernames
• Twitter User IDs (optional): array of numeric user IDs
• Max Followers To Collect: per-target limit
• Max Following To Collect: per-target limit
• Include Followers: enable followers collection
• Include Following: enable following collection
• Result Format: usernames or ids

Plan limits

• Free users: up to 1,000 total results per run
• Paying users: up to 5,000,000 per relation per target

Example input (JSON)

{
  "userNameList": ["elonmusk", "nasa"],
  "userIdList": ["44196397"],
  "maxFollowers": 250000,
  "maxFollowing": 250000,
  "getFollowers": true,
  "getFollowing": true,
  "outputMode": "usernames"
}

Output format

Each scraped user is pushed as a separate dataset item (streaming):

{
  "status": "item",
  "job_id": "...",
  "query_type": "username",
  "query_value": "elonmusk",
  "relation": "followers",
  "mode": "usernames",
  "value": "some_follower_username"
}

Where:

• relation is followers or following
• mode is usernames or ids
• value is the scraped username or user ID

Run summary

After run completion, summary is stored in key-value store record SUMMARY. It includes:

• total jobs
• completed jobs
• failed jobs
• emitted item count
• estimated price
• failed job details (failed_jobs)

Note: failed jobs are stored in SUMMARY, not as dataset result items.

Pricing

Pricing model is configured as pay-per-event:

• apify-default-dataset-item = 0.0001 USD
• equivalent to $0.1 / 1,000 scraped users

Additional Apify platform usage charges (compute/storage/etc.) apply.

Performance notes

• Results are streamed in batches from backend and pushed continuously.
• Large requests (hundreds of thousands to millions) are supported by worker queue and token rotation.
• Throughput depends on token quality, target account size, and current X API/rate-limit behavior.

Troubleshooting

1. No items returned

Check:

• input usernames/IDs are valid
• target accounts are public/accessible
• backend URL and API key are correct

2. Job failures in SUMMARY.failed_jobs

Usually caused by temporary network/rate-limit issues or invalid tokens on backend.

3. Slow completion on very large runs

Expected for high limits. Keep streaming enabled and consume dataset progressively.

Related actor: Twitter/X Email Scraper

If you also need email extraction from Twitter profiles, use your email actor:

• Twitter/X Email Scraper (mSaHt2tt3Z7Fcwf0o)

SEO keywords

twitter follower scraper, twitter following scraper, x follower scraper, x.com follower scraper, scrape twitter followers, scrape twitter following, twitter audience scraper, social graph scraper, twitter lead generation, x influencer scraper, twitter usernames scraper, twitter user id scraper, twitter data extraction, twitter followers api alternative