# X Scraper Studio (`social_developer/x-scraper-studio`) Actor

Paste mixed X / Twitter targets — handles, tweet links, hashtags, communities, lists — and collect tweets, people, replies, followers, or trends as clean JSON. No login, no cookies, no proxy.

- **URL**: https://apify.com/social\_developer/x-scraper-studio.md
- **Developed by:** [Celine](https://apify.com/social_developer) (community)
- **Stats:** 1 total users, 1 monthly users, 88.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.00005 / actor start

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/actors/running/actors-in-store.md#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

## X Scraper Studio

Paste mixed X / Twitter targets and collect **tweets, people, replies, followers, communities, lists, or trends** as clean JSON. No login. No cookies. No proxy.

The first screen is the whole product: paste, pick a job (or leave Auto), set a cap, Start.

### What you paste

One item per line. Mix freely.

| Line | Auto does |
| --- | --- |
| `@NASA` or `https://x.com/NASA` | Profile tweets |
| `https://x.com/NASA/status/123` or a tweet ID | That tweet |
| `#AI` or `climate summit` | Search tweets |
| Community URL | Community posts |
| List URL | List posts |
| `https://x.com/NASA/followers` | Followers of that profile |

Need a different slice from the same paste? Change **What should this run collect?** first.

### Jobs

**Auto — tweets from what you paste** is the default.

Lock a job when every line should mean the same thing:

- Profile · Tweets, replies they posted, media, likes, mentions, about, followers, following, verified followers
- Search · Tweets & hashtags, people, communities
- Tweet · Details, replies, quotes, full thread, who liked, who reposted, long article
- Community · Posts, members, moderators
- List · Posts, members, followers
- Trends (paste can be empty — pick a region)

Wrong-type lines become `itemType: skip` rows. The run continues.

### Input

| Field | Default | Notes |
| --- | --- | --- |
| Paste | — | Required except for Trends |
| Job | Auto | |
| Stop after this many (per line) | 50 | Per pasted line, not the whole run |
| Posted after / before | empty | Tweet jobs |
| Latest or Top | Latest | Search / feeds |
| Replies / Reposts / Media / Language | Include / any | Tweet jobs |
| Minimum likes | empty | People search uses this as min followers |
| Checkmark accounts only | off | |
| Trends region | Worldwide | India, US, UK, and other listed countries |

### Output

Each dataset item has `itemType`:

- `tweet` — text, metrics, author, media, url
- `user` — handle, bio, counts, profile url
- `trend` — name, rank, region, search query
- `skip` — original line + `skipReason`

Filter CSV in Sheets with `itemType=tweet`.

Console views: Tweets, People, Trends, Skipped lines.

### Example

```json
{
  "paste": "@NASA\n#AI\nclimate summit",
  "job": "auto",
  "maxItems": 50
}
```

Followers of several accounts:

```json
{
  "paste": "@NASA\n@ISRO\n@esa",
  "job": "followers",
  "maxItems": 200
}
```

India trends:

```json
{
  "job": "trends",
  "trendRegion": "india",
  "maxItems": 30
}
```

### Notes

- Max results is **per line**. Three handles at 50 = up to 150 tweets.
- Dates apply to tweet / search / timeline jobs, not to follower lists or trends.
- One failed line does not fail the run.
- Built for Apify. Set `DATA_API_KEY` on the actor as a secret (actor owner only). Run users never see it.

# Actor input Schema

## `paste` (type: `string`):

Mix freely — Auto reads each line. <code>@NASA</code> or a profile link → their tweets. A tweet link or ID → that tweet. <code>#AI</code> or <code>climate summit</code> → search. Community and list links work too. Leave empty only for Trends (set region below).

## `job` (type: `string`):

@handles → their tweets · #hashtags / text → search · tweet links → that tweet. Leave Auto unless you need another slice — scan by prefix: Profile, Search, Tweet, Community, List.

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

Cap for each pasted line, not the whole run. Example: 3 lines × 50 = up to 150 rows.

## `fromDate` (type: `string`):

Keep posts on/after this day (YYYY-MM-DD). Ignored for people lists, profile cards, and trends.

## `toDate` (type: `string`):

Keep posts on/before this day (YYYY-MM-DD). Leave empty for no end date.

## `sort` (type: `string`):

Latest = monitoring. Top = research. Used for search and similar feeds.

## `replies` (type: `string`):

Filters tweet results only. Does nothing to followers, likers, profile cards, or trends.

## `reposts` (type: `string`):

Include, hide, or keep only reposts / retweets.

## `media` (type: `string`):

Limit to posts with a certain attachment, or text-only.

## `language` (type: `string`):

Keep posts in one language. Any = no language filter.

## `replyScope` (type: `string`):

Used when collecting replies on a tweet. All = direct + nested. Direct only = top-level replies.

## `minLikes` (type: `integer`):

Drop weaker posts. For people search, this is treated as a minimum follower count.

## `verifiedOnly` (type: `boolean`):

Keep verified authors / profiles only.

## `trendRegion` (type: `string`):

Used only when the job is Trends. Paste can be empty.

## Actor input object example

```json
{
  "paste": "@NASA\n#AI\nclimate summit",
  "job": "auto",
  "maxItems": 50,
  "sort": "latest",
  "replies": "include",
  "reposts": "include",
  "media": "any",
  "language": "any",
  "replyScope": "all",
  "verifiedOnly": false,
  "trendRegion": "worldwide"
}
```

# Actor output Schema

## `tweets` (type: `string`):

Text, engagement, author, link

## `people` (type: `string`):

Handles, bios, follower counts

## `trends` (type: `string`):

Ranked topics by region

## `skipped` (type: `string`):

Wrong-type or failed lines

## `dataset` (type: `string`):

Full export — filter by itemType tweet | user | trend | skip

# 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 = {
    "paste": `@NASA
#AI
climate summit`,
    "job": "auto",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("social_developer/x-scraper-studio").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 = {
    "paste": """@NASA
#AI
climate summit""",
    "job": "auto",
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("social_developer/x-scraper-studio").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "paste": "@NASA\\n#AI\\nclimate summit",
  "job": "auto",
  "maxItems": 50
}' |
apify call social_developer/x-scraper-studio --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,social_developer/x-scraper-studio"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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