X Followers Scraper

Export visible public follower and following relationships for selected X profiles using the configured operator-managed session. Keep source and related-profile identities, relationship type and optional exposed profile context. Visibility limits mean a bounded export is not a complete private membership list, a verified audience identity map or a guarantee of current platform access.

Quick start

Choose one known profile, one relationship and a small per-profile limit, then inspect source provenance and warnings. The existing NASA follower input is:

{
  "handles": ["NASA"],
  "mode": "followers",
  "maxItems": 20,
  "includeProfileDetails": true
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

• Export GitHub following profiles on X
• Export NASA follower profiles on X
• Compare GitHub followers and following on X

What you get

One visible source-to-related-profile relationship per saved row, with edgeType distinguishing followers from following. Optional profile details can include public biography, counts, media and an email only when explicitly present in the bio. Missing values remain null rather than being guessed, and an extracted public address does not establish deliverability or permission to contact it.

Who is it for?

• Creator research teams reviewing visible source-linked audience samples.
• Social-data analysts comparing stable related-profile identifiers in their own tools.
• Brand researchers inspecting public following context without inferring private relationships.
• Data developers retaining provenance and relationship type for separate repeat-export comparisons.

How you can use the data

• Inspect a small NASA follower sample. Use the existing NASA recipe and keep sourceHandle, relatedUserId and edgeType. The observed sample does not establish complete audience demographics or every follower the account has.
• Compare two observed audiences downstream. Use the existing NASA/NatGeo recipe, retaining stable related IDs and each source profile. Compute overlap in your own tools, distinguishing no overlap in a bounded sample from proof that two complete audiences are disjoint.
• Review GitHub's public following context. Use the existing GitHub profile URL in following mode and keep relatedProfileUrl with the requested source. A follow relationship is not evidence of endorsement, employment or an offline relationship.
• Keep your own recurring relationship observations. Store source IDs, related IDs, edgeType and scrapedAt before comparing exports. Optional profile counts and visibility can change, so growth calculations, deduplication across runs and alerts belong to your downstream workflow.

Input settings

Input	Purpose
handles	One or more X handles, with or without @.
profileUrls	One or more public X or Twitter profile URLs.
mode	Choose followers, following, or both.
maxItems	Maximum visible rows per selected profile and relationship, from 1 to 500.
includeProfileDetails	Include visible public biography, counts, and profile metadata.
maxRuntimeSeconds	Processing limit from 60 to 270 seconds, including time reserved to save the summary.

The limit applies per selected profile and relationship rather than as one shared batch cap. Multiple profiles or both relationship types can therefore produce more total rows than the single maxItems value. Provide up to 100 distinct profiles across both input lists. Results are limited by available time and charge budget.

Existing small audience comparison

{
  "handles": ["NASA", "NatGeo"],
  "mode": "followers",
  "maxItems": 50
}

Existing following URL input

{
  "profileUrls": ["https://x.com/github"],
  "mode": "following",
  "maxItems": 100,
  "includeProfileDetails": true
}

Output data

Field	Description
sourceInput, sourceHandle, sourceUserId, sourceProfileUrl	Requested profile and source provenance.
edgeType	Relationship exported: followers or following.
relatedUserId, relatedHandle, relatedName, relatedProfileUrl	Visible related-profile identity and canonical X URL.
bio, location, websiteUrl, email	Public profile text, link, and conservatively extracted bio email.
profileImageUrl, profileBannerUrl	Visible public profile media URLs.
followersCount, followingCount, listedCount, likesCount, postsCount, mediaCount	Visible public account counts.
createdAt, isVerified, isBlueVerified, isProtected	Visible account metadata.
scrapedAt	UTC time at which the row was collected.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A run has a start event, including when it produces no rows, and an item event for each saved profile-edge row. Extraction stops when the remaining result charge budget is exhausted.

The per-profile, per-relationship cap controls each part of the batch, so keep profile counts and both-mode requests bounded as well.

Current rates and plan discounts are shown on the X Followers Scraper Pricing tab. Platform usage can also apply.

Tips for best results

• Start with one source and relationship. Inspect access and provenance before expanding the batch.
• Keep relationship type beside IDs. Followers and following describe opposite directions.
• Account for all selected sources. The cap is per profile and relationship, not one global batch limit.
• Treat optional bio values as public claims. An exposed email, location or badge is not independently verified identity.
• Retain restricted-work diagnostics. Visibility gaps are different from an account having no relationships.

Limits and caveats

• Start with a small maxItems to validate the target and relationship.
• Only data visible through X's public web experience for the configured managed session can be exported.
• Private accounts, DMs, engagement automation, customer-supplied cookies, and paid/private X data are out of scope.
• X may restrict a target or change public visibility. When possible, successful rows for other targets are preserved and the run summary identifies restricted work.

The operator-managed session does not let customers supply cookies or access protected-account membership, DMs or paid/private X data. No applications, messages, follow actions or engagement automation are performed. Public profile context can be absent, stale or visibility-limited.

Unavailable relationships and completed extraction with no usable records succeed with truthful summary reasons. Useful results from accessible targets are preserved. Access alone does not establish that an account is private or deleted. Configuration, execution, storage and billing failures still fail the run. Review the summary and available rows rather than interpreting a partial sample as a complete relationship archive.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The existing Node.js and Python examples wait for completion and print the dataset ID. Use that ID to read saved rows with the Dataset API or client, with pagination for larger exports. The cURL example starts a run and returns its details. Wait for completion before reading its dataset.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~x-followers-scraper/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"handles":["NASA"],"mode":"followers","maxItems":20}'

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/x-followers-scraper').call({
  handles: ['NASA'],
  mode: 'followers',
  maxItems: 20,
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("fetch_cat/x-followers-scraper").call(run_input={
    "handles": ["NASA"], "mode": "followers", "maxItems": 20
})
print(run["defaultDatasetId"])

MCP and AI agents

You can ask your AI assistant to collect data with X Followers Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's X Followers Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/x-followers-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use X Followers Scraper by Fetch Cat, or give it the identifier fetch_cat/x-followers-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s X Followers Scraper to collect up to 5 visible NASA follower relationships with public profile details enabled. Keep source and related IDs without treating the sample as the complete audience or accessing private memberships.”
• “Collect up to 5 visible following relationships from https://x.com/github with profile details enabled. Keep edge direction and public source links without inferring endorsement or contacting accounts.”
• “Retrieve up to 5 visible follower rows each for NASA and NatGeo. Keep the source profile on every row for my own overlap analysis, preserve restriction warnings and do not request customer cookies.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

What data can I export with twitter followers scraper?

You can export visible public followers or following rows with stable identity, profile URLs, public profile text, selected counts, verification state, and source provenance. Optional public fields can be absent on an individual profile and are returned as null rather than guessed.

Can I run X Followers Scraper through an API, schedule, or MCP client?

Yes. Use the Apify API example above, schedule the Actor from Apify, or call it through the configured Apify MCP tool. All three use the same handle/profile-URL inputs and produce the same dataset shape.

How much does it cost to use X Followers Scraper?

The start fee and per-result prices are displayed on the Actor Pricing tab. Your total depends on the number of visible rows exported, so use maxItems to keep each run within your intended budget.

Can I export private followers or bring my own X cookie?

No. The Actor exports only public-web-visible rows using an operator-managed session. It does not accept customer cookies and cannot access private-account membership or DMs.

What happens when one profile is blocked or unavailable?

The Actor preserves successful output from other targets and records unavailable relationships in its run summary. An unavailable target or completed extraction with no usable rows succeeds without fabricated results. Invalid configuration, execution, storage and billing failures still fail.

Related Actors

• X Profile Tweets Scraper — monitor public posts from the profiles found in your follower export.
• X User Profile Scraper — enrich a known public X profile.
• Instagram Mentions Scraper — Collect public posts and Reels tagging known Instagram profiles, with available captions and engagement.
• Reddit Scraper — collect public community conversations for social listening.
• TikTok Profile Scraper — compare public audience signals across social platforms.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥