# 🐦 Twitter/X Profile & Followers Scraper (`khadinakbar/twitter-profile-followers-scraper`) Actor Scrape Twitter/X user profiles, followers, and following lists in one run. Returns username, bio, follower count, verified status, location, website, and more. No API key needed. - **URL**: https://apify.com/khadinakbar/twitter-profile-followers-scraper.md - **Developed by:** [Khadin Akbar](https://apify.com/khadinakbar) (community) - **Categories:** Social media, Marketing - **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, NaN bookmarks - **User rating**: No ratings yet ## Pricing from $5.00 / 1,000 x (twitter) user records This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## 🐦 Twitter/X Profile & Followers Scraper — No Login **The only Twitter/X scraper that extracts full user profiles, follower lists, and following lists in a single run — no API key, no login required.** Collect structured data from any public Twitter/X account: bio, follower counts, verification status, location, website, and complete follower/following networks. Built for marketers, growth teams, sales researchers, and AI pipelines. > Export scraped data, run the scraper via API, schedule and monitor runs, or integrate with other tools using Apify's platform. --- ### 🔥 Why This Scraper? Most Twitter scrapers make you choose — either get profile data OR followers. Then you run a second actor and pay twice. This actor does it all in one run: - ✅ **All-in-one**: profile + followers + following in a single execution - ✅ **No login or API key**: works entirely from public data - ✅ **Bulk input**: scrape dozens of accounts simultaneously - ✅ **MCP-ready**: AI agents like Claude can call this actor directly - ✅ **Clean output**: semantic field names, null for missing values, timestamps on every record - ✅ **Paginated**: automatically fetches all pages of followers, not just the first 20 --- ### 📊 What Data Does It Extract? Every record — whether a profile, follower, or following entry — contains the same rich fields: | Field | Description | Example | |-------|-------------|---------| | `record_type` | `profile`, `follower`, or `following` | `"follower"` | | `user_id` | Stable numeric Twitter ID | `"44196397"` | | `username` | @handle (without @) | `"elonmusk"` | | `display_name` | Full display name | `"Elon Musk"` | | `bio` | Profile bio text | `"CEO of Tesla and SpaceX"` | | `follower_count` | Total followers | `185000000` | | `following_count` | Total accounts following | `639` | | `tweet_count` | Total tweets posted | `42000` | | `verified` | Legacy blue checkmark | `false` | | `is_blue_verified` | X Premium (paid) checkmark | `true` | | `verified_type` | `blue`, `business`, `government`, or null | `"blue"` | | `location` | Self-reported location | `"Austin, TX"` | | `website` | Linked website URL | `"https://x.com"` | | `created_at` | Account creation date (ISO) | `"2009-06-02T20:12:29.000Z"` | | `profile_image_url` | Full-resolution profile picture URL | `"https://pbs.twimg.com/..."` | | `banner_url` | Header/banner image URL | `"https://pbs.twimg.com/..."` | | `pinned_tweet_id` | ID of their pinned tweet | `"1234567890123456789"` | | `source_username` | Which account was being scraped | `"elonmusk"` | | `scraped_at` | Timestamp of collection (ISO) | `"2026-03-31T12:00:00.000Z"` | | `source_url` | URL that produced this record | `"https://x.com/elonmusk/followers"` | --- ### 🚀 How to Use #### Option 1: Enter Usernames The simplest approach. Enter a list of Twitter @handles (without the @): ```json { "usernames": ["elonmusk", "sama", "naval", "paulg"], "mode": "all", "maxFollowersPerUser": 500, "maxResults": 5000 } ```` #### Option 2: Enter Direct URLs Paste profile, followers, or following URLs directly: ```json { "startUrls": [ { "url": "https://x.com/elonmusk/followers" }, { "url": "https://x.com/sama/following" } ], "maxResults": 1000 } ``` #### Option 3: Profiles Only (Fast & Cheap) Just want account stats and bios without pulling follower lists? ```json { "usernames": ["hubspot", "salesforce", "monday"], "mode": "profiles", "maxResults": 50 } ``` *** ### ⚙️ Input Parameters | Parameter | Type | Default | Description | |-----------|------|---------|-------------| | `usernames` | Array of strings | `["elonmusk"]` | Twitter @handles to scrape (without @) | | `startUrls` | Array of URL objects | `[]` | Direct profile/followers/following URLs | | `mode` | string | `"profiles"` | What to collect: `profiles`, `followers`, `following`, or `all` | | `maxFollowersPerUser` | integer | `200` | Max followers per account (0 = unlimited) | | `maxFollowingPerUser` | integer | `200` | Max following per account (0 = unlimited) | | `maxResults` | integer | `1000` | Hard cap on total records across all accounts | | `proxyConfiguration` | object | Residential | Proxy settings (residential recommended for Twitter/X) | *** ### 💡 Use Cases **🎯 Lead Generation** Pull the follower list of your competitor's Twitter account. Every follower is a pre-qualified prospect who's already interested in what you sell. Filter by bio keywords like "founder", "VP Sales", or "Head of Marketing" to build targeted outreach lists. **📊 Influencer Research** Scrape the profile data for 100+ accounts in your niche. Compare follower counts, engagement ratios (tweet count vs followers), verified status, and account age to rank influencers by actual reach and authenticity. **🔍 Competitor Analysis** Track who follows your top 5 competitors. Find accounts that follow multiple competitors — those are your warmest prospects. Run monthly to detect follower growth trends. **🤖 AI & Data Pipelines** This actor is fully compatible with the Apify MCP server (`mcp.apify.com`). Claude, ChatGPT, and other AI agents can call it directly with instructions like: *"Scrape the followers of @hubspot and filter for accounts with more than 5,000 followers in the SaaS space."* **📈 Audience Intelligence** Analyze a thought leader's following list to understand what accounts they trust. Great for discovering new voices, newsletters, and communities in a niche. **🏢 B2B Prospecting** Find all Twitter accounts following industry conferences or associations. Filter by bio for job titles like "CTO", "Founder", or "Director" to build high-quality B2B prospect lists. *** ### 💰 Pricing This actor uses **pay-per-result** pricing — you only pay for what you get. | Event | Price | |-------|-------| | Per profile, follower, or following record | **$0.0002** | | Actor start | **$0.005** | **Example costs:** - 1,000 profile records = **$0.20** - 10,000 follower records = **$2.00** - 100 profiles + 10,000 followers = **$2.025** Compare: the closest competitor charges $0.00025/record for followers-only. We charge $0.0002 for profiles AND followers in the same run. *** ### 🔌 API & Automation Run this scraper programmatically using the Apify API: ```bash curl -X POST \ "https://api.apify.com/v2/acts/USERNAME~twitter-profile-followers-scraper/runs" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -d '{ "usernames": ["hubspot", "salesforce"], "mode": "followers", "maxFollowersPerUser": 1000, "maxResults": 5000 }' ``` Or use the JavaScript SDK: ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: 'YOUR_API_TOKEN' }); const run = await client.actor('USERNAME/twitter-profile-followers-scraper').call({ usernames: ['hubspot', 'salesforce'], mode: 'all', maxFollowersPerUser: 500, maxResults: 2000, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` *** ### 🤖 Using with AI Agents (MCP) This actor is optimized for the [Apify MCP Server](https://apify.com/apify/actors-mcp-server). Claude and other AI agents can discover and call it automatically. Example prompt to Claude: > *"Use the Twitter scraper to collect the followers of @semrush and filter for anyone with 'SEO' or 'content' in their bio."* Claude will find this actor, run it with appropriate parameters, and return the filtered results — all without manual configuration. *** ### ❓ FAQ **Does this require a Twitter/X account or API key?** No. This scraper works entirely from public Twitter/X data using their internal GraphQL API. No authentication needed. **Does it respect rate limits?** Yes. The actor uses residential proxies and session management to stay within acceptable request rates. It will not hammer Twitter's servers. **Can I scrape private accounts?** No. This scraper only collects publicly visible profile data. Private accounts will return no data. **What if an account has millions of followers?** Use `maxFollowersPerUser` to cap the collection. Setting it to `10000` will collect the most recent 10,000 followers. Setting it to `0` attempts to collect all followers (expensive for large accounts). **How fresh is the data?** Data is collected in real-time — every `scraped_at` timestamp reflects the exact moment of collection. **Can I schedule this to run automatically?** Yes. Use Apify's built-in [scheduler](https://docs.apify.com/platform/schedules) to run this actor daily, weekly, or on any cron schedule. Great for tracking follower growth over time. *** ### 🛠️ Technical Notes - **Crawler**: `HttpCrawler` — uses Twitter's internal GraphQL API directly (no browser overhead) - **Proxy**: Residential proxies required (Twitter blocks datacenter IPs aggressively) - **Pagination**: Automatically follows cursor-based pagination for complete follower/following lists - **Error handling**: Failed requests are logged but do not pollute the output dataset - **Output consistency**: Every record has the same field structure — no missing fields, `null` for unavailable values *** ### 📬 Support & Feedback Found a bug or want a feature? Open an issue in the Issues tab. Response time: within 48 hours. If this actor saved you time, please ⭐ leave a review — it helps other users discover it. # Actor input Schema ## `usernames` (type: `array`): Use this when the user provides @handles or usernames (without @). E.g. \['elonmusk', 'sama', 'naval']. Do NOT use this when the user provides full URLs — use startUrls instead. ## `startUrls` (type: `array`): Use this when the user provides full Twitter/X URLs. Supports profile URLs (x.com/username), followers URLs (x.com/username/followers), or following URLs (x.com/username/following). Overrides 'usernames' input. ## `mode` (type: `string`): Choose what to scrape. 'profiles' = profile metadata only. 'followers' = follower list only. 'following' = following list only. 'all' = profile + followers + following in one run. ## `maxFollowersPerUser` (type: `integer`): Maximum number of followers to collect per account. Use this to control cost. Default: 200. Set to 0 for unlimited (warning: large accounts have millions). ## `maxFollowingPerUser` (type: `integer`): Maximum number of following accounts to collect per user. Default: 200. Set to 0 for unlimited. ## `maxResults` (type: `integer`): Hard cap on total records returned across all users and modes. Use to control costs. Default: 1000. Set to 0 for no limit. ## `authToken` (type: `string`): Pre-configured — leave blank. Credentials are baked into the actor as environment variables so you never need to enter them. Only fill this in if you want to use a different Twitter account's cookies. ## `csrfToken` (type: `string`): Pre-configured — leave blank. Credentials are baked into the actor as environment variables so you never need to enter them. Only fill this in if you want to use a different Twitter account's cookies. ## `proxyConfiguration` (type: `object`): Proxy settings for scraping. Residential proxies recommended for Twitter/X. Leave as default unless you have specific proxy requirements. ## Actor input object example ```json { "usernames": [ "elonmusk" ], "startUrls": [], "mode": "profiles", "maxFollowersPerUser": 200, "maxFollowingPerUser": 200, "maxResults": 1000, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `results` (type: `string`): Dataset of Twitter/X user profile objects — profiles, followers, and following records. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "usernames": [ "elonmusk" ], "startUrls": [], "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }; // Run the Actor and wait for it to finish const run = await client.actor("khadinakbar/twitter-profile-followers-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "usernames": ["elonmusk"], "startUrls": [], "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], }, } # Run the Actor and wait for it to finish run = client.actor("khadinakbar/twitter-profile-followers-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "usernames": [ "elonmusk" ], "startUrls": [], "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }' | apify call khadinakbar/twitter-profile-followers-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=khadinakbar/twitter-profile-followers-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "🐦 Twitter/X Profile & Followers Scraper", "description": "Scrape Twitter/X user profiles, followers, and following lists in one run. Returns username, bio, follower count, verified status, location, website, and more. No API key needed.", "version": "0.1", "x-build-id": "TholbbMSNA27vBs0w" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/khadinakbar~twitter-profile-followers-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-khadinakbar-twitter-profile-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/khadinakbar~twitter-profile-followers-scraper/runs": { "post": { "operationId": "runs-sync-khadinakbar-twitter-profile-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/khadinakbar~twitter-profile-followers-scraper/run-sync": { "post": { "operationId": "run-sync-khadinakbar-twitter-profile-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "usernames": { "title": "Twitter/X Usernames", "type": "array", "description": "Use this when the user provides @handles or usernames (without @). E.g. ['elonmusk', 'sama', 'naval']. Do NOT use this when the user provides full URLs — use startUrls instead.", "items": { "type": "string" } }, "startUrls": { "title": "Start URLs", "type": "array", "description": "Use this when the user provides full Twitter/X URLs. Supports profile URLs (x.com/username), followers URLs (x.com/username/followers), or following URLs (x.com/username/following). Overrides 'usernames' input.", "items": { "type": "object" } }, "mode": { "title": "Scrape Mode", "enum": [ "profiles", "followers", "following", "all" ], "type": "string", "description": "Choose what to scrape. 'profiles' = profile metadata only. 'followers' = follower list only. 'following' = following list only. 'all' = profile + followers + following in one run.", "default": "profiles" }, "maxFollowersPerUser": { "title": "Max Followers per User", "minimum": 0, "type": "integer", "description": "Maximum number of followers to collect per account. Use this to control cost. Default: 200. Set to 0 for unlimited (warning: large accounts have millions).", "default": 200 }, "maxFollowingPerUser": { "title": "Max Following per User", "minimum": 0, "type": "integer", "description": "Maximum number of following accounts to collect per user. Default: 200. Set to 0 for unlimited.", "default": 200 }, "maxResults": { "title": "Max Total Results", "minimum": 0, "type": "integer", "description": "Hard cap on total records returned across all users and modes. Use to control costs. Default: 1000. Set to 0 for no limit.", "default": 1000 }, "authToken": { "title": "Twitter Auth Token (auth_token cookie) — Optional Override", "type": "string", "description": "Pre-configured — leave blank. Credentials are baked into the actor as environment variables so you never need to enter them. Only fill this in if you want to use a different Twitter account's cookies." }, "csrfToken": { "title": "Twitter CSRF Token (ct0 cookie) — Optional Override", "type": "string", "description": "Pre-configured — leave blank. Credentials are baked into the actor as environment variables so you never need to enter them. Only fill this in if you want to use a different Twitter account's cookies." }, "proxyConfiguration": { "title": "Proxy Configuration", "type": "object", "description": "Proxy settings for scraping. Residential proxies recommended for Twitter/X. Leave as default unless you have specific proxy requirements." } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```