# X / Twitter Post Scraper (`clappi/x-twitter-post-scraper`) Actor

Instantly scrape X (Twitter) posts - no login, no API keys. Get full engagement metrics (likes, retweets, replies, quotes, bookmarks, views) plus complete author profile data. Fast, reliable, and ready to scale.

- **URL**: https://apify.com/clappi/x-twitter-post-scraper.md
- **Developed by:** [Clappi](https://apify.com/clappi) (community)
- **Categories:** Lead generation, Social media, Automation
- **Features:** Limited permissions
- **Stats:** 156 total users, 30 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.30 / 1,000 posts

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## X (Twitter) Post Scraper

Scrape public X (Twitter) post metrics and author data. Get likes, retweets, replies, quotes, bookmarks, views, and full author profile details.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `postUrls` | array | X post URLs to scrape |

#### Supported URL formats

- `https://x.com/username/status/ID` — Standard post URL
- `https://twitter.com/username/status/ID` — Old twitter.com URLs
- `https://x.com/i/status/ID` — Short format (no username)

#### Example Input

```json
{
  "postUrls": [
    "https://x.com/HardwareSteam/status/2050983784879722845",
    "https://x.com/GymBr_o/status/2050688856861630710",
    "https://x.com/JasonDeJesuz/status/2050885797029499224"
  ]
}
```

### Output

Each post returns a JSON object with the following fields:

```json
{
  "tweet_id": "1234567890123456789",
  "url": "https://x.com/username/status/1234567890123456789",
  "text": "Post content here...",
  "created_at": "Sun May 03 17:00:14 +0000 2026",
  "lang": "en",
  "likes": 1200,
  "retweets": 85,
  "replies": 43,
  "quotes": 12,
  "bookmarks": 97,
  "views": 45000,
  "possibly_sensitive": false,
  "hashtags": ["example", "hashtag"],
  "media": [
    { "type": "photo", "url": "https://pbs.twimg.com/media/..." }
  ],
  "author": {
    "id": "987654321",
    "username": "username",
    "name": "Display Name",
    "created_at": "Mon Jan 01 00:00:00 +0000 2022",
    "avatar_url": "https://pbs.twimg.com/profile_images/...",
    "banner_url": "https://pbs.twimg.com/profile_banners/...",
    "bio": "Account bio text here",
    "location": "New York, NY",
    "followers": 15000,
    "following": 500,
    "tweets_count": 2400,
    "media_count": 310,
    "likes_given": 8500,
    "listed_count": 75,
    "is_blue_verified": false,
    "is_verified": false,
    "is_protected": false
  },
  "status": "available",
  "scrapedAt": "2026-05-03T17:00:00.000Z"
}
```

#### Output fields

| Field | Description |
|-------|-------------|
| `tweet_id` | Post ID |
| `url` | Canonical post URL |
| `text` | Full post text |
| `created_at` | Post publish timestamp |
| `lang` | Detected language |
| `likes` | Like count |
| `retweets` | Retweet count |
| `replies` | Reply count |
| `quotes` | Quote tweet count |
| `bookmarks` | Bookmark count |
| `views` | View count |
| `hashtags` | List of hashtags used |
| `media` | Attached media (photos/videos) |
| `author.username` | Author handle |
| `author.followers` | Follower count |
| `author.is_blue_verified` | X Premium (blue checkmark) |
| `author.is_verified` | Legacy verified status |
| `status` | `available` or `unavailable` |
| `scrapedAt` | Scrape timestamp (ISO 8601) |

### Use Cases

- **Content Analysis** — Track post performance metrics
- **Competitor Research** — Monitor competitor content engagement
- **Influencer Vetting** — Verify engagement rates and follower quality
- **Social Listening** — Collect post data for reporting and analysis
- **Audience Research** — Analyse author profiles and reach

# Actor input Schema

## `postUrls` (type: `array`):

List of X (Twitter) post URLs to scrape.

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

Optional proxy settings.

## Actor input object example

```json
{
  "postUrls": [
    "https://x.com/HardwareSteam/status/2050983784879722845",
    "https://x.com/GymBr_o/status/2050688856861630710",
    "https://x.com/JasonDeJesuz/status/2050885797029499224"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "postUrls": [
        "https://x.com/HardwareSteam/status/2050983784879722845",
        "https://x.com/GymBr_o/status/2050688856861630710",
        "https://x.com/JasonDeJesuz/status/2050885797029499224"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("clappi/x-twitter-post-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 = { "postUrls": [
        "https://x.com/HardwareSteam/status/2050983784879722845",
        "https://x.com/GymBr_o/status/2050688856861630710",
        "https://x.com/JasonDeJesuz/status/2050885797029499224",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("clappi/x-twitter-post-scraper").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 '{
  "postUrls": [
    "https://x.com/HardwareSteam/status/2050983784879722845",
    "https://x.com/GymBr_o/status/2050688856861630710",
    "https://x.com/JasonDeJesuz/status/2050885797029499224"
  ]
}' |
apify call clappi/x-twitter-post-scraper --silent --output-dataset

```

## MCP server setup

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

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/WWb3T5rnggNCWBFIt/builds/fKSBejg1PssDxZ6sF/openapi.json