# X Twitter Latest Tweets Scraper - Tweet View Count, Bookmarks (`snow_leo_data/twitter-profile-scraper`) Actor

One account with its 10 latest tweets costs $0.0031 here against $0.038 and $0.070 at the niche leader's profile scrapers: no per-request fee, no start fee, no minimum charge. Profile card plus latest tweets of any public X account, with likes, retweets, replies, quotes, bookmarks and views.

- **URL**: https://apify.com/snow_leo_data/twitter-profile-scraper.md
- **Developed by:** [Snow Leo Data](https://apify.com/snow_leo_data) (community)
- **Categories:** Social media, For creators, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.24 / 1,000 result rows

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) Profile & Tweets Scraper

Profile card plus the latest tweets of any public X account, with the full
engagement set: **likes, retweets, replies, quotes, bookmarks and views**.

One flat price per row. **No per-request fee, no start fee, no minimum charge.**

### Why this one

The niche prices small runs badly. Reading one account with its 10 latest
tweets costs, by the published pricing of each Actor on 18 Sep 2026:

| Actor | What you pay for one account + 10 tweets |
|---|---|
| **This Actor** | **$0.0031** |
| `apidojo/twitter-profile-scraper` | $0.0380 |
| `apidojo/twitter-scraper-lite` | $0.0700 |

The difference is not the per-row rate, it is the overhead: those Actors add
$0.016 per profile, $0.016 per request, $0.05 for a single tweet by URL, or a
$0.02–$0.10 minimum per run. On a small watch run **82% of that bill is not
data**. Here there is no such fee, so a run that reads five accounts every hour
stays in cents.

### What one run returns

Measured on 10 accounts of very different sizes on 18 Sep 2026
(`tools/measurements.json`):

- **10 of 10 accounts returned data, 0 failures.**
- **56 tweets, median 5.5 per account** (minimum 5, maximum 7).
- **Views present on 56 of 56 tweets.**
- Profile row: 15 of 18 fields filled (median). Tweet row: 15 of 18 (median).

Account size does not change this: NASA (92.3M followers) returned 5 tweets,
`apify` (15.8K followers) returned 6.

#### Honest limits

- X serves **the latest 5–10 tweets** on a public profile page. There is no
  pagination for a signed-out reader, so this Actor **cannot** export tweet
  history. If you need thousands of old tweets, use a full-timeline scraper.
- Search and hashtag pages return **zero** tweets to a signed-out reader
  (checked both from a laptop and from the Apify cloud), so **there is no
  keyword search here**.
- Protected accounts and accounts that do not exist return no data, and the run
  says so by name instead of finishing green and empty.

This is a **watch** tool: point it at the accounts you care about and run it on
a schedule.

### Fields

**Profile row** — `handle`, `name`, `url`, `user_id`, `description`,
`location`, `followers_count`, `following_count`, `tweets_count`,
`is_blue_verified`, `verified_type`, `is_protected`, `avatar_url`,
`banner_url`, `affiliates_count`, `highlighted_tweets`, `created_at_ms`.

**Tweet row** — `tweet_id`, `url`, `handle`, `text`, `created_at_ms`, `lang`,
`favorite_count`, `retweet_count`, `reply_count`, `quote_count`,
`bookmark_count`, `view_count`, `possibly_sensitive`, `mentions`, `links`,
`media`, `place`.

### Watch mode

Turn on **Only changed** and the run returns only what is new or changed since
its previous run, labelled `NEW` or `UPDATED` with the changed fields listed.

Likes, retweets and views are deliberately **not** part of the change
fingerprint: they move every minute on a live tweet, so watching them would
mark every tweet as changed on every run and a watch run would quietly bill
like a full one.

### Input

| Field | What it does |
|---|---|
| Accounts | Handles, @handles or profile links |
| Tweet URLs | Links to single tweets |
| Include profile / Include tweets | Pick what you pay for |
| Max tweets per account | Upper bound; the source gives 5–10 |
| Min likes / retweets / views, Languages, Text contains | Keep only what matters |
| Only changed | Watch mode |
| Compact rows | Drop the columns you are not using |
| Input dataset ID | Take the accounts from another Actor's output |

### Empty runs

A run that collects nothing **charges nothing** and says why by name in the
run log and in the `REPORT` record: no account given, every value invalid,
both outputs switched off, a tweet filter with tweets switched off, every
account unreachable, everything removed by filters, or nothing changed since
the last run.

### No login

No cookies, no token, no account of yours is used or asked for.

# Actor input Schema

## `handles` (type: `array`):

X accounts to read: a handle (nasa), an @handle (@nasa) or a profile link (https://x.com/nasa). Each account returns its profile card and its latest tweets.

## `tweetUrls` (type: `array`):

Links to single tweets, for example https://x.com/nasa/status/2100294890068271339. Charged as one row each, with no extra per-request fee.

## `includeProfile` (type: `boolean`):

Return one profile row per account: name, bio, followers, following, tweet count, location, avatar, banner, verification.

## `includeTweets` (type: `boolean`):

Return the latest tweets of each account with the full engagement set: likes, retweets, replies, quotes, bookmarks and views.

## `maxTweetsPerAccount` (type: `integer`):

Upper bound per account. X serves 5 to 10 latest tweets on a public profile page (measured on 10 accounts: 56 tweets, median 5.5), so a higher number cannot add more.

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

Hard stop on billed rows. 0 means no limit.

## `minFavorites` (type: `integer`):

Keep tweets with at least this many likes.

## `minRetweets` (type: `integer`):

Keep tweets with at least this many retweets.

## `minViews` (type: `integer`):

Keep tweets with at least this many views.

## `languages` (type: `array`):

Keep tweets in these language codes only, for example en, es, ru.

## `textContains` (type: `string`):

Keep tweets whose text contains this, case-insensitive.

## `onlyChanged` (type: `boolean`):

For watch runs: return only what is new or changed since the previous run of this Actor. Likes and views are deliberately not watched, otherwise every tweet would count as changed every hour.

## `compact` (type: `boolean`):

Keep only the core columns, so the CSV has no empty ones.

## `inputDatasetId` (type: `string`):

Read the accounts from another Actor's dataset instead of typing them.

## `urlField` (type: `string`):

Which field of that dataset holds the handle or profile link.

## `concurrency` (type: `integer`):

How many accounts are read at once.

## `timeoutSeconds` (type: `integer`):

How long one request to X may take before it is retried.

## Actor input object example

```json
{
  "handles": [
    "nasa"
  ],
  "includeProfile": true,
  "includeTweets": true,
  "maxTweetsPerAccount": 20,
  "maxItems": 100,
  "minFavorites": 0,
  "minRetweets": 0,
  "minViews": 0,
  "onlyChanged": false,
  "compact": false,
  "urlField": "handle",
  "concurrency": 4,
  "timeoutSeconds": 30
}
```

# Actor output Schema

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

All collected rows

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

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

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,snow_leo_data/twitter-profile-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/sEwl9nbvRpMRW8aXC/builds/4tJeAd1uxq4hzvVS2/openapi.json