# Twitter (X) List Scraper - Full Tweets, Views & Authors (`dami_studio/twitter-list-scraper`) Actor

Turn any curated X list into a clean data feed. Scrapes every tweet in a list timeline with full untruncated text, likes, retweets, replies, quotes, bookmarks and view counts, plus hashtags, mentions, links, media URLs and the complete author profile. Export JSON/CSV/Excel or deliver to Notion.

- **URL**: https://apify.com/dami\_studio/twitter-list-scraper.md
- **Developed by:** [Dami's Studio](https://apify.com/dami_studio) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## ⚡ Twitter (X) List Scraper — Tweets from Any X List

**Pull every tweet from any X (Twitter) List timeline — at a fraction of the price of the big providers.** Point it at a list id or URL and get back the full tweet text plus every engagement metric — likes, retweets, replies, quotes, bookmarks and **views** — with author, media, hashtags and mentions. Export to **JSON, CSV or Excel**, call it from the **API**, or have results delivered straight to **Notion**. **Just $0.30 per 1,000 tweets** — pay only for tweets actually returned.

> X gates List timelines behind a login — there is no keyless path. This actor scrapes them the same way every paid provider does: with a rotating pool of logged-in account cookies. You bring throwaway-account cookies; the actor handles rotation, back-off and delivery.

### Why this scraper wins

- 💸 **Cheaper** — **$0.30 / 1,000 tweets**, billed per tweet actually returned. Empty or failed runs cost nothing.
- 🔁 **Account-pool rotation** — paste several throwaway-account cookies; the actor rotates them automatically on rate-limit (`429`) or bad-account errors, exactly like the paid services.
- 🧹 **Clean, flat output** — one tidy record per tweet, ready for spreadsheets, dashboards or LLM pipelines. No raw nested GraphQL soup.
- 🔂 **Auto-dedupe** — the same tweet is never returned (or charged) twice in a run, even across multiple lists.
- 🛡️ **Residential by default** — ships with Apify residential proxy preset to protect your accounts and keep success rates high.
- 📬 **Built-in delivery** — optionally push every run straight into **Notion** via Apify connectors, with zero extra code.
- 🚦 **Honest errors** — if X blocks, rate-limits or a list is inaccessible, you get a clear diagnostic row (`BLOCKED`, `NO_RESULTS`, …) instead of silent emptiness.

### What you can scrape

| Mode | Input | Notes |
|---|---|---|
| **List by id** | `listIds` (the number in `x.com/i/lists/<id>`) | Scrape one or many lists in a single run |
| **List by URL** | `startUrls` (`https://x.com/i/lists/<id>`) | List id is parsed out of the URL automatically |

### ⚠️ Requires a logged-in account cookie for real data (no keyless way exists)

X requires a logged-in session for Lists — **every** provider scrapes these with pools of logged-in accounts. This actor does the same with **your** cookies.

> **Keyless demo mode:** run it without any cookies and it returns **one clearly-labeled `_sample` tweet** (free, never charged) so you can preview the exact output shape before adding accounts. Add your `sessionCookies` to scrape the real tweets in a list.

**How to get the cookie (1 minute):**

1. Log in to **x.com** in your browser (use a throwaway account you don't mind risking).
2. Press **F12** → **Application** tab → **Cookies** → `https://x.com`.
3. Copy the values of **`auth_token`** and **`ct0`**.
4. Paste into `sessionCookies` as `auth_token=XXXX; ct0=YYYY` — add several accounts (one per line) for more throughput; the actor rotates them.

> Throwaway accounts get rate-limited/flagged over time — add a few and top them up occasionally (same as the paid services do).

### Input

- **`listIds`** — X list ids (e.g. `34179516`). One or many.
- **`startUrls`** — or paste full list URLs (`https://x.com/i/lists/34179516`); the id is extracted for you.
- **`sessionCookies`** *(required for real data)* — one or more logged-in account cookies, format `auth_token=XXXX; ct0=YYYY`, one per line. The actor rotates across them on rate-limit. Leave empty to get a labeled sample tweet (demo mode).
- **`maxItems`** — cap the number of tweets (default `100`, max `5000`). You pay per tweet.
- **`proxyConfiguration`** — Residential strongly recommended (and the default) to protect accounts; datacenter IPs hit X's limits faster.
- **`notionConnector`** / **`notionParentId`** — optional, deliver results to a Notion data source.

### Output (one record per tweet)

```json
{
  "id": "1789000000000000000",
  "url": "https://x.com/nasa/status/1789000000000000000",
  "text": "We're going back to the Moon. 🌙",
  "createdAt": "Mon May 13 14:02:11 +0000 2024",
  "lang": "en",
  "replyCount": 312,
  "retweetCount": 1840,
  "likeCount": 21500,
  "quoteCount": 96,
  "bookmarkCount": 410,
  "viewCount": 1230000,
  "isReply": false,
  "isRetweet": false,
  "isQuote": false,
  "conversationId": "1789000000000000000",
  "hashtags": ["Artemis"],
  "mentions": [],
  "urls": [],
  "media": [{ "type": "photo", "url": "https://pbs.twimg.com/media/xxx.jpg" }],
  "author": {
    "id": "11348282",
    "userName": "NASA",
    "name": "NASA",
    "verified": true
  }
}
```

### Pricing

**$0.30 per 1,000 tweets** (pay-per-result). You are only charged for tweets actually returned — failed or empty runs cost nothing.

### FAQ

**Why do I need account cookies?** X requires a logged-in session to view List timelines — there is no keyless route. Every paid List scraper does the same; this actor just lets you bring (and rotate) your own throwaway accounts.

**How many accounts should I add?** One works for small runs. For sustained volume add 3–5 throwaway accounts so the pool can rotate when X rate-limits an account.

**Where do I find the list id?** It's the number in the list URL: `x.com/i/lists/34179516` → `34179516`. You can also just paste the full URL in `startUrls`.

**Why residential proxy?** X rate-limits datacenter IP ranges quickly and is harsher on accounts behind them. Residential keeps success rates high and protects your cookies.

**It returned a diagnostic row — why?** That's the actor telling you exactly what happened (e.g. `BLOCKED`, `NO_RESULTS`) instead of failing silently. Check your cookies are valid and the list is accessible, then retry.

# Actor input Schema

## `listIds` (type: `array`):

X list ids (the number in x.com/i/lists/<id>).

## `startUrls` (type: `array`):

Or paste list URLs (https://x.com/i/lists/34179516).

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

Charged per tweet.

## `sessionCookies` (type: `array`):

X requires a logged-in session for search/lists — this is how every paid service does it. WITHOUT cookies the actor returns one clearly-labeled SAMPLE tweet (free demo mode) so you can preview the output shape. For real results add one or more throwaway-account cookies; the actor rotates them on rate-limit. From a logged-in x.com: F12 → Application → Cookies → copy auth\_token and ct0. Paste each account as 'auth\_token=XXXX; ct0=YYYY' (one per line).

## `proxyConfiguration` (type: `object`):

Residential proxy strongly recommended (paid services use residential to protect the accounts).

## `notionConnector` (type: `string`):

Optional Notion delivery.

## `notionParentId` (type: `string`):

Optional Notion data-source id.

## Actor input object example

```json
{
  "listIds": [
    "34179516"
  ],
  "startUrls": [
    "https://x.com/i/lists/34179516"
  ],
  "maxItems": 100,
  "sessionCookies": [
    "auth_token=abcd1234...; ct0=ef567890..."
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `results` (type: `string`):

Tweets in the default dataset.

# 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 = {
    "listIds": [
        "34179516"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("dami_studio/twitter-list-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 = { "listIds": ["34179516"] }

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

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/Sk5DHexHNrZgnRfyZ/builds/KqZtMJWJVRCJt1tje/openapi.json