# X (Twitter) Profile Data Scraper — Bio, Followers, Verified (`nick.cheng/x-profile-data`) Actor

Get X (Twitter) profile data by handle, URL or user ID — bio, location, website, follower and following counts, join date, verification type and date. Bulk profile lookup, no tweets fetched, no login, no cookies, no API key. Charged only for profiles actually returned.

- **URL**: https://apify.com/nick.cheng/x-profile-data.md
- **Developed by:** [Nicholas Cheng](https://apify.com/nick.cheng) (community)
- **Categories:** Social media, Developer tools, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 1,000 tweet scrapeds

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?

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 (Twitter) Profile Data Scraper

**Give it a list of handles, get one clean profile record per account.** No tweets, no timelines — just the account data: bio, location, website, follower and following counts, join date, verification type and when it was verified. No login, no cookies, no API key, no proxy configuration.

**You are charged only for profiles that actually came back.** A suspended, deleted, or misspelled handle produces an explanatory row and costs nothing.

| | |
|---|---|
| **Input** | X / Twitter handles, profile URLs, or numeric user IDs |
| **Output** | One profile row per account, 40+ fields |
| **Price** | **$0.005 per profile — the same on every Apify plan** |
| **Tweets** | **Not fetched.** This Actor is the profiles-only mode of the [X (Twitter) Profile & Tweets Scraper](https://apify.com/nick.cheng/x-twitter-profile-tweets-scraper); use that one when you also want timelines |

***

### What you get

```json
{
  "itemType": "profile",
  "userId": "11348282",
  "userName": "NASA",
  "url": "https://x.com/NASA",
  "name": "NASA",
  "description": "There's space for everybody. ✨",
  "website": "https://www.nasa.gov",
  "location": "Pale Blue Dot",
  "createdAt": "2007-12-19T20:20:32.000Z",
  "followers": 92359333,
  "following": 63,
  "tweetsCount": 76410,
  "mediaCount": 22581,
  "isVerified": true,
  "isBlueVerified": true,
  "verifiedType": "Government",
  "verifiedSince": "2023-04-01T18:22:05.000Z",
  "parodyCommentaryFanLabel": null,
  "affiliatesCount": 74,
  "isProfessional": false,
  "isProtected": false,
  "profilePicture": "https://pbs.twimg.com/profile_images/….jpg"
}
```

The fields that usually decide whether an account is what it claims to be come straight from X's own account metadata — nothing here is guessed or generated:

| Field | Why it matters |
|---|---|
| `verifiedType` | `Government`, `Business`, or blank — separates official accounts from paid blue checks |
| `verifiedSince` | Exact timestamp the account was verified |
| `parodyCommentaryFanLabel` | X's mandatory label for parody / commentary / fan accounts |
| `affiliatesCount` | How many sub-accounts a business account has under it |
| `createdAt` | Account age, the cheapest signal against a freshly minted account with bought followers |
| `tipjar` | Bitcoin, Ethereum, PayPal, Venmo, Cash App, Patreon handles the account has published |

Plus the standard set: `description`, `descriptionUrls` (expanded, not `t.co`), `website`, `location`, `followers`, `following`, `tweetsCount`, `mediaCount`, `favouritesCount`, `professionalCategory`, `birthdate`, `isProtected`, `profilePicture` (full resolution), `coverPicture`.

***

### Input

```json
{
  "twitterHandles": ["nasa", "openai", "nytimes"],
  "startUrls": [{ "url": "https://x.com/elonmusk" }],
  "userIds": ["11348282"]
}
```

| Option | Notes |
|---|---|
| `twitterHandles` | With or without `@`. Pass as many as you like — they are all resolved in one run |
| `startUrls` | Any `x.com/<handle>` or `twitter.com/<handle>` URL, as copied from a browser |
| `userIds` | Numeric IDs, immune to username changes |
| `maxItems` | Hard cap on rows for the run, to bound spend on a large list |

Handles, URLs and IDs are merged and de-duplicated, so a messy list pasted from a spreadsheet is fine.

***

### Pricing

**$0.005 per profile, on every Apify plan** — Free, Bronze, Silver, Gold, Platinum, Diamond. Check the Pricing tab: all six columns are identical. That is worth checking on any Actor you compare, including this one, because the price a listing advertises in its title is not always the price a free-plan run pays.

One thousand profiles cost $5. There is no per-run minimum; a run that returns one profile costs $0.005.

#### What you are not charged for

| | What happens here |
|---|---|
| **Accounts that do not exist** | Suspended, deleted, or misspelled handles produce one row marked `chargedForThis: false`. Nothing is billed. |
| **Empty or placeholder rows** | If the profile did not come back, no profile row is written. There are no filler rows. |
| **The free plan** | Same code path, same fields, same limits. No demo mode, no row cap, no nulls in place of data. |

***

### What this Actor cannot do

- **No tweets.** This is the profiles-only mode. For tweets, filters, incremental runs and single-tweet lookup use the [X (Twitter) Profile & Tweets Scraper](https://apify.com/nick.cheng/x-twitter-profile-tweets-scraper) — same code, same prices, one more event.
- **No followers or following lists.** X does not expose them to logged-out clients.
- **No keyword search.** Same restriction.
- **Protected accounts** return their profile (marked `isProtected: true`) — that part is public.

***

### How it stays working

X rotates the internal query identifiers its own web app uses. This Actor reads them from X's live frontend at runtime and caches them for six hours; if a call is rejected it re-reads them and retries once. No login is used anywhere, which is why it is not exposed to the account-ban failures that take login-based scrapers offline.

***

### Integrating

```bash
curl -X POST "https://api.apify.com/v2/acts/nick.cheng~x-profile-data/run-sync-get-dataset-items?token=<TOKEN>" \
  -H 'Content-Type: application/json' \
  -d '{"twitterHandles":["nasa","openai"]}'
```

Official clients exist for JavaScript and Python, and results export as JSON, CSV, or Excel.

# Actor input Schema

## `twitterHandles` (type: `array`):

Usernames to scrape, with or without the @ (e.g. "nasa", "@openai"). This is the fastest way to target accounts. Defaults to a single well-known account so a run with no input still returns data.

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

Profile URLs such as https://x.com/nasa. Handy when your source system already stores links rather than handles.

## `userIds` (type: `array`):

Numeric X user IDs (e.g. "11348282"). Use these when you need results that survive a username change.

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

Hard cap across the whole run, counting every profile and tweet pushed. 0 means no cap. Use it to bound spend on large input lists.

## Actor input object example

```json
{
  "twitterHandles": [
    "nasa",
    "openai",
    "nytimes"
  ],
  "maxItems": 0
}
```

# Actor output Schema

## `profiles` (type: `string`):

One row per account, including deterministic fields most scrapers omit: verification type and date, parody/commentary/fan label, affiliate count, published tipjar handles.

## `runSummary` (type: `string`):

What was scraped, what could not be scraped and why, and exactly how many billable events were charged.

# 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 = {
    "twitterHandles": [
        "nasa",
        "openai",
        "nytimes"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nick.cheng/x-profile-data").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 = { "twitterHandles": [
        "nasa",
        "openai",
        "nytimes",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nick.cheng/x-profile-data").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 '{
  "twitterHandles": [
    "nasa",
    "openai",
    "nytimes"
  ]
}' |
apify call nick.cheng/x-profile-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nick.cheng/x-profile-data"
        }
    }
}

```

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/WUYhJ00NbjonNhF9U/builds/gCRptFf6j1c34wbu9/openapi.json