X (Twitter) Followers & Following Scraper — Export Any Account's Social Graph

Turn any X (Twitter) account's followers and following into a clean, structured contact list. Point it at one or more handles, pick the graphs you want — followers, following, verified followers, or subscriptions — and get one flat JSON row per user, ready for your CRM, spreadsheet, database, or AI pipeline.

No X API keys. No developer account. No login. Just enter usernames and press Start.

⚡ Public data, zero setup • 🎯 Followers + following in one run • 🧩 Flat, predictable JSON • 💸 Pay only for what you export

---

Why this Actor

• Skip the official X API. No $100–$5,000/mo tiers, no OAuth apps, no rate-limit math.
• Both directions at once. Export who follows an account and who that account follows in a single run — each row is tagged so you can tell them apart instantly.
• Built for scale. Results stream straight to the dataset as they arrive. Runs comfortably on 256 MB and can pull the entire follower graph of an account when you set the per-account limit to unlimited.
• Never loses a run to one bad input. A private, suspended, or misspelled account becomes a tidy unavailable row — the rest of your run keeps going.
• Automation-native. Pipe results to Google Sheets, Airtable, a webhook, your database, or an AI agent via the Apify API and MCP.

---

Use cases & outcomes

🎯 Lead generation & prospecting Export the followers of a competitor, a niche influencer, or an industry account, filter for users above a follower threshold, and turn a warm audience into a ready-made prospect list.

🔍 Competitor & audience analysis Pull a competitor's followers and the accounts they follow to understand who they target, who amplifies them, and where their audience overlaps with yours.

🧠 Influencer & creator vetting Check an influencer's verified followers and subscriptions to gauge real reach and audience quality before a partnership.

📊 Community & network mapping Snapshot a founder's or brand's social graph over time to track growth, churn, and notable new followers.

🤖 AI agents & RAG pipelines Feed flat, consistently-named JSON straight into an LLM — no brittle parsing, stable field names, canonical x.com URLs on every row.

---

What you can export

Relationship	Turn on with	You get
Followers (default)	relationships: ["followers"]	Every account that follows the source account
Following (default)	relationships: ["following"]	Every account the source account follows
Verified followers	relationships: ["verified_followers"]	Only the verified accounts that follow them
Subscriptions	relationships: ["subscriptions"]	Paid subscriptions for the source account

Select any combination — each selected relationship is exported for every account you provide.

---

Quick start

1. Open the Actor in Apify Console.
2. Enter one or more usernames (without @).
3. Pick your relationships (defaults to followers + following).
4. Set Max users per account — 100 to sample, or 0 to export the entire graph.
5. Press Start and watch rows stream into the dataset.
6. Export as JSON / CSV / Excel, or pull via the Apify API, integrations, or MCP.

Example — followers + following of one account

{
  "usernames": ["nasa"],
  "relationships": ["followers", "following"],
  "maxUsersPerAccount": 500
}

Example — a lead list of large followers

{
  "usernames": ["openai"],
  "relationships": ["followers"],
  "minFollowers": 1000,
  "maxItems": 5000
}

Example — export the entire following of several accounts

{
  "usernames": ["nasa", "spacex", "esa"],
  "relationships": ["following"],
  "maxUsersPerAccount": 0
}

Example — verified followers only, by user ID

{
  "userIds": ["11348282"],
  "relationships": ["verified_followers"],
  "maxUsersPerAccount": 0
}

---

Input reference

Field	Type	Default	Description
usernames	string[]	[]	X handles to export, without @.
userIds	string[]	[]	Numeric user IDs (skips username resolution).
relationships	string[]	["followers","following"]	Any of followers, following, verified_followers, subscriptions. Each is exported for every account.
maxUsersPerAccount	integer	100	Max users per account per relationship. 0 = unlimited (bounded by maxItems).
minFollowers	integer	0	Keep only exported users with at least this many followers. 0 = off.
maxItems	integer	100000	Global ceiling on total exported users — the main cost lever.
pageSize	integer	1000	Users requested per page. Does not cap totals — the Actor keeps paginating. Higher = fewer requests.
maxRetries	integer	5	Automatic retries on rate limits / temporary errors.
retryBaseDelayMs	integer	2000	Initial retry backoff (grows exponentially).
retryMaxDelayMs	integer	30000	Maximum retry backoff.
includeRaw	boolean	false	Attach the untouched source payload under raw.

Provide at least one username or userId.

---

Output

Every exported user is a flat JSON object. Rows from different graphs live in the same dataset and are distinguished by relationshipType and the source* fields.

Field	Type	Description
featureType / relationshipType	string	Which graph this row came from: followers, following, verified_followers, or subscriptions.
sourceUsername	string | null	The account whose graph this user belongs to (null when the account was given by ID).
sourceUserId	string	The numeric ID of the source account.
inputRef	string	The username or ID you provided.
scrapedAt	string	ISO 8601 UTC timestamp of collection.
id	string | null	The exported user's numeric ID.
username	string | null	The exported user's handle.
displayName	string | null	Display name.
bio	string | null	Profile bio.
url	string | null	Canonical https://x.com/... profile URL.
followersCount	number | null	Follower count.
followingCount	number | null	Following count.
tweetCount	number | null	Total posts.
listedCount / mediaCount	number | null	Lists containing the user / media posts.
verified	boolean | null	Legacy verified flag.
isBlueVerified	boolean | null	X Premium (Blue) verification.
verifiedType	string | null	Verification type when present.
isProtected	boolean | null	Whether the account is protected.
location	string | null	Profile location.
website	string | null	Profile website.
createdAt	string | null	Account creation date.
profileImageUrl / profileBannerUrl	string | null	Avatar / banner image URLs.

Example — a follower row:

{
  "featureType": "followers",
  "relationshipType": "followers",
  "scrapedAt": "2026-07-06T12:00:00.000Z",
  "sourceUrl": "https://x.com/jane_doe",
  "inputRef": "nasa",
  "sourceUserId": "11348282",
  "sourceUsername": "nasa",
  "id": "6000000000000000001",
  "username": "jane_doe",
  "displayName": "Jane Doe",
  "bio": "Space nerd. Coffee. Code.",
  "url": "https://x.com/jane_doe",
  "followersCount": 1200,
  "followingCount": 340,
  "tweetCount": 5820,
  "verified": false,
  "isBlueVerified": true,
  "location": "Austin, TX",
  "profileImageUrl": "https://pbs.twimg.com/profile_images/…"
}

Couldn't be fetched? You get an explicit marker instead of a silent gap:

{
  "featureType": "unavailable",
  "status": "unavailable",
  "reason": "not_found",
  "message": "User @example not found.",
  "inputRef": "example",
  "relationshipType": null,
  "scrapedAt": "2026-07-06T12:00:00.000Z"
}

After every run, the OUTPUT tab shows a summary: the relationships exported, accounts requested/resolved, counts per relationship, unavailable count, and any non-fatal errors.

---

Dataset views

The dataset ships with ready-made tabbed views in the Console — Overview, Followers, Following, and Unavailable — so you can read results without building a single filter. Filter on relationshipType to split "followers of @X" from "accounts @X follows", even when both are in the same dataset.

---

Controlling scope & cost

Field	Effect
maxUsersPerAccount	The per-account throttle. 100 samples; 0 exports the full graph.
maxItems	The global ceiling and main cost lever. Lower it to keep runs lean.
minFollowers	Trims small accounts out of the results before they're stored.

Large accounts have millions of followers — exporting the full graph uses more compute and time. Start with a modest maxUsersPerAccount and raise it once you've confirmed the output looks right.

---

FAQ

Do I need an X/Twitter API key or login? No. This Actor exports public follower/following data with zero credentials.

Can I export followers and following in one run? Yes — select both in relationships. Each row is tagged with relationshipType so you can tell them apart.

Can I get all followers of an account? Yes — set maxUsersPerAccount to 0 (unlimited). The run is then bounded only by maxItems.

What formats can I export? JSON, CSV, Excel, HTML, or RSS — plus the Apify API, webhooks, and integrations.

Will one bad username break my run? No. Failed accounts become unavailable rows and the run continues.

Can I schedule it? Yes — use Apify Schedules to run on any cron you like.

---

Support

Open an issue on the Actor page or contact the publisher with your run ID and your (redacted) input JSON.

---

Contact me

Need something built beyond this Actor? I take on custom projects — from Apify scrapers and data pipelines to full-stack web apps.

Email	dubem115@gmail.com
GitHub	github.com/DrunkCodes

Reach out with a short description of your project and timeline — happy to discuss scope and pricing.