# Twitter (X) Followers Scraper | $0.10/1K | Followers/Following (`ecomdate/x-followers-scraper`) Actor

Export any X (Twitter) account's followers or following list in bulk — no login, just $0.10 per 1,000 users. One row per user: handle, name, bio, followers, verification & more.

- **URL**: https://apify.com/ecomdate/x-followers-scraper.md
- **Developed by:** [Ecomdate Tech](https://apify.com/ecomdate) (community)
- **Categories:** Developer tools, Social media, Lead generation
- **Stats:** 6 total users, 5 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.10 / 1,000 user scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — 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

Export the **followers** or **following** list of any X (Twitter) account in **bulk**. Paste one or more handles and get a clean row per user — handle, name, bio, follower/following counts, verification, location and more. Perfect for lead lists, audience research, and influencer discovery. **No Twitter login or API key needed on your end.**

### Features

- 👥 **Followers or Following** — pick which list to export per run
- 📄 **One row per user** — flat output that drops straight into CSV, Excel, or a CRM
- 📊 **Rich fields** — username, name, bio, followers, following, tweets, verification, location, website, join date, avatar
- 🔢 **Spend controls** — cap per account (`maxItemsPerUser`) and per run (`maxItems`)
- 🧵 **Handles huge lists** — automatic cursor pagination under the hood
- 🔗 **Flexible input** — `@handle`, `handle`, or `https://x.com/handle`
- 🚫 **Clear on empty** — accounts with no results return a `status` row instead of vanishing

### How it works

1. Provide the source accounts and choose **Followers** or **Following**.
2. The Actor pages through each account's list and streams one record per user into the dataset.
3. Set **Max users per account** / **Max users total** to control size and cost.
4. Export to JSON, CSV, Excel, or pull via API.

### Input

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `usernames` | Array\<String> | Yes | – | Source accounts. Accepts `@handle`, `handle`, or profile URL. |
| `listType` | String | No | `followers` | `followers` or `following`. |
| `maxItemsPerUser` | Integer | No | `200` | Max users to scrape per source account (`0` = no limit). |
| `maxItems` | Integer | No | `0` | Max users across all accounts (`0` = no limit). |

#### Example input

```json
{
  "usernames": ["apify", "@github"],
  "listType": "followers",
  "maxItemsPerUser": 500,
  "maxItems": 0
}
```

### Output

One record per follower / following user:

```json
{
  "sourceUsername": "apify",
  "listType": "followers",
  "status": "ok",
  "userId": "1596171553557254144",
  "username": "Remote_Crypto",
  "name": "Remote Crypto Jobs",
  "description": "Find your next crypto job",
  "followers": 1820,
  "following": 430,
  "tweetsCount": 5123,
  "mediaCount": 210,
  "verified": false,
  "location": "Remote",
  "website": "https://example.com",
  "createdAt": "2022-11-25T10:00:00+00:00",
  "profileImage": "https://pbs.twimg.com/profile_images/...",
  "profileUrl": "https://x.com/Remote_Crypto",
  "scrapedAt": "2026-07-09T12:00:00+00:00"
}
```

### Use cases

- **Lead generation** — build a targeted list from a competitor's or community's followers
- **Influencer discovery** — see who a key account follows
- **Audience research** — analyze the makeup of an account's followers (verified share, bios, locations)
- **CRM enrichment** — expand your prospect list with real X profiles

### Pricing

Simple pay-per-result:

- **User Scraped** — **$0.0001 per user** ($0.10 per 1,000 followers/following)

Example: scraping 10,000 followers ≈ **$1.00**. With Apify's Free plan ($5 monthly credits) you can export **~50,000 users for free** each month — with **no separate compute or platform fees**, the per-user price is all you pay.

### FAQ

**Followers or following — can I get both?**
Pick one per run with `listType`. Run twice (or add both accounts) to get both lists.

**How many followers can I scrape per account?**
As many as the account has — use `maxItemsPerUser` to cap it. Very large accounts (millions of followers) can be expensive and slow, so start with a limit.

**What if an account is private, suspended, or has no results?**
You get a single row for it with `status: "no_results"`, so nothing silently disappears.

**Are the fields the same for followers and following?**
Mostly. For `following` lists, X exposes fewer details, so `verified` and `location` may be empty for some users.

**Do I need a Twitter/X login or API key?**
No. Just paste the source handles.

**Is scraping X legal?**
This Actor collects only publicly available data. You are responsible for complying with X's Terms and applicable laws (e.g. GDPR).

### Support

Need another field, `both` mode, or hit a bug? Open an issue on the Actor's **Issues** tab.

***

**Need more?** Looking for full profile data or keyword/hashtag tweet search? Check out the other X (Twitter) scrapers from this developer.

# Actor input Schema

## `usernames` (type: `array`):

X/Twitter accounts whose followers or following you want to export. Accepts '@handle', 'handle', or 'https://x.com/handle'.

## `listType` (type: `string`):

Whether to scrape the accounts' followers or the accounts they follow.

## `maxItemsPerUser` (type: `integer`):

Maximum followers/following to scrape per source account (0 = no limit). Large accounts can have millions — set a limit to control spend.

## `maxItems` (type: `integer`):

Maximum number of users across all source accounts (0 = no limit).

## Actor input object example

```json
{
  "usernames": [
    "apify"
  ],
  "listType": "followers",
  "maxItemsPerUser": 200,
  "maxItems": 0
}
```

# Actor output Schema

## `users` (type: `string`):

No description

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "usernames": [
        "apify"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ecomdate/x-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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "usernames": ["apify"] }

# Run the Actor and wait for it to finish
run = client.actor("ecomdate/x-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": [
    "apify"
  ]
}' |
apify call ecomdate/x-followers-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ecomdate/x-followers-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/UgrrbT8oMh9smaRDk/builds/IgucfvCWGlDeFXOgn/openapi.json