# TikTok Creator & Profile Scraper (`eiv/tiktok-creator-scraper`) Actor

Scrape TikTok creator profiles in bulk: exact follower, like and video counts, verified and business-account flags, TikTok Shop seller status, category, bio link and the contact e-mails creators publish in their bios. Video URLs resolve too. From $10 / 1,000 creators.

- **URL**: https://apify.com/eiv/tiktok-creator-scraper.md
- **Developed by:** [Eimantas V](https://apify.com/eiv) (community)
- **Categories:** Social media, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 creator profile scrapes

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

## TikTok Creator & Profile Scraper

Give it a list of TikTok handles. Get back **exact follower counts, engagement, business and TikTok Shop status, bio links and contact e-mails** — one HTTP request per creator, no browser.

```
@gymshark    6,605,687 followers · mega · 315,606 avg likes/video
             verified · business account · TikTok Shop seller
             Sports, Fitness & Outdoors · gym.sh/shoptiktok
```

***

### What you get per creator

| Group | Fields |
|---|---|
| **Audience** | Exact `followers`, `following`, `likes`, `videos`, `friends`, plus `avgLikesPerVideo` and a `followerTier` (nano → mega) |
| **Status** | `verified`, `isPrivate`, `isOrganization` |
| **Commerce** | `isBusinessAccount`, **`isTikTokShopSeller`**, `businessCategory` |
| **Contact** | `bioLink`, `bioLinkDomain`, **`bioEmails`**, and Instagram / YouTube / X / Snapchat handles named in the bio |
| **Identity** | `handle`, `nickname`, `bio`, `avatarUrl`, `language`, `userId`, `secUid` |
| **Age** | `accountCreatedAt`, `accountAgeDays` |

Pass **video URLs** in the same list and they resolve through TikTok's public oEmbed endpoint to title, author and thumbnail — billed at a fifth of the profile rate, since a video lookup moves 1 KB against a profile's 357 KB.

***

### Why the counts are exact

TikTok's page state carries follower counts twice. The legacy `stats` object stores them as 32-bit integers and rounds them; `statsV2` carries the same numbers as strings.

The difference is not cosmetic. Khaby Lame's 2.66 billion likes come back from the legacy field as **−1,638,295,034** — an overflow in TikTok's own JSON that turns any derived average negative. This Actor reads `statsV2`:

| | Legacy field | This Actor |
|---|---|---|
| `@khaby.lame` followers | 162,600,000 | **162,619,759** |
| `@khaby.lame` likes | −1,638,295,034 | **2,656,672,262** |

***

### Who this is for

- **Influencer marketing** — screen a creator list by tier, engagement and category, then pull the booking e-mail straight out of the bio. `withContactEmailOnly: true` turns a broad list into an outreach list in one pass.
- **Brand and competitor monitoring** — track a set of creators or brand accounts weekly and diff follower counts and video output.
- **E-commerce prospecting** — `isTikTokShopSeller` and `businessCategory` identify accounts actually selling on the platform.
- **Lead enrichment** — `bioLinkDomain` gives the creator's company domain, ready to join against firmographic data.

***

### Input

```json
{
  "profiles": ["@gymshark", "duolingo", "https://www.tiktok.com/@nasa"],
  "minFollowers": 10000,
  "withContactEmailOnly": true
}
```

Handles with or without `@`, profile URLs, video URLs and `vm.tiktok.com` short links all work, and duplicates collapse.

| Option | Default | Notes |
|---|---|---|
| `minFollowers` | `0` | Filtered creators are neither written nor charged — the cheapest way to screen a big list |
| `businessAccountsOnly` | `false` | Only accounts with a commerce category |
| `withContactEmailOnly` | `false` | Only creators with a reachable e-mail in the bio |
| `maxConcurrency` | `10` | TikTok is rate-sensitive; raise gradually and watch for 403s |
| `proxyConfiguration` | residential | See below |

***

### About proxies — read this first

**TikTok blocks datacenter IP ranges aggressively.** The Actor defaults to the Apify **residential** proxy because that is what reliably works. Residential bandwidth is the dominant cost of running this, and it is the reason a creator costs $0.01 rather than a tenth of a cent.

It is worth trying a small run **without** a proxy first: some ranges are served normally, and if yours is one of them the Actor runs far cheaper. If you see `HTTP_403` or `NO_STATE_BLOB` in `errorCode`, that range is blocked — switch residential back on. The run log says so explicitly and counts how many targets were affected.

***

### Output

```json
{
  "handle": "gymshark",
  "nickname": "Gymshark",
  "followers": 6605687, "likes": 138866619, "videos": 440,
  "avgLikesPerVideo": 315606, "followerTier": "mega",
  "verified": true, "isBusinessAccount": true, "isTikTokShopSeller": true,
  "businessCategory": "Sports, Fitness & Outdoors",
  "bioLink": "https://gym.sh/shoptiktok", "bioLinkDomain": "gym.sh",
  "bioEmails": [], "bioHandles": { "instagram": null, "youtube": null },
  "accountCreatedAt": "2018-03-23T09:23:00.000Z", "accountAgeDays": 3064,
  "recordType": "creator"
}
```

Three ready-made dataset views ship with it — **Creators**, **Outreach list** and **Commerce signals**. Set `flattenOutput: true` for CSV.

Failed targets still produce a row with `success: false` and an `errorCode`, so your output stays aligned with your input.

***

### Honest limits

- **Blocking is the main risk**, not parsing. With a residential proxy this is reliable; without one it depends entirely on your IP range.
- **No video lists per creator.** TikTok's profile page state contains the creator, not their posts — those load through a signed API this Actor deliberately does not touch. Pass video URLs explicitly if you need per-video data.
- **No follower demographics or fake-follower scoring.** Those require panel data no public endpoint exposes. `avgLikesPerVideo` is a reach proxy, not an audited engagement rate.
- **`bioEmails` finds what creators publish.** Many put nothing, or an address only shown in-app. Empty is a real answer, not a miss.
- **Private accounts** return their profile fields with `isPrivate: true`; counts may be withheld by TikTok.

***

### Pricing

| Event | Price | When |
|---|---|---|
| Actor start | $0.005 | Once per run |
| Creator profile scraped | $0.01 | Per profile returned, after your filters |
| Video scraped | $0.002 | Per video URL resolved |

**$10 per 1,000 creators.** Filters run before billing, and failures are never charged.

***

### Tips

- **Screen before you enrich.** `minFollowers: 10000` on a 50,000-handle list drops the unusable half without billing you for it.
- **Schedule weekly and diff on `handle`.** Follower deltas and new video counts are the growth signal; a creator's `avgLikesPerVideo` falling while followers rise is the classic fading-account pattern.
- **Chain `bioLinkDomain`** into a company-data Actor to attach firmographics to each creator's business.

# Actor input Schema

## `profiles` (type: `array`):

TikTok handles ('@gymshark' or 'gymshark'), profile URLs, or video URLs — one per line. Video URLs are resolved through TikTok's public oEmbed endpoint and billed at the cheaper video rate.

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

Alternative to Creators, for feeding the output of another Actor straight into this one.

## `sourceDatasetId` (type: `string`):

Read handles from an existing dataset instead of a pasted list.

## `sourceDatasetField` (type: `string`):

Which field on the source dataset holds the handle or profile URL.

## `minFollowers` (type: `integer`):

Drop creators below this follower count. Filtered creators are not written to the dataset and are not charged, so this is the cheapest way to screen a large list. Leave at 0 to keep everyone.

## `businessAccountsOnly` (type: `boolean`):

Keep only accounts registered as business/commerce accounts. These are the ones with a category and, usually, a contactable brand behind them.

## `withContactEmailOnly` (type: `boolean`):

Keep only creators whose bio contains a reachable e-mail address. Turns a broad creator list into an outreach list in one pass.

## `maxConcurrency` (type: `integer`):

Profiles fetched in parallel. TikTok is more rate-sensitive than an open API, so the default is deliberately modest; raise it gradually and watch for HTTP 403.

## `requestTimeoutSecs` (type: `integer`):

Per-request timeout.

## `maxRetries` (type: `integer`):

Retries for connection resets and 5xx responses, on the same IP.

## `blockedRetries` (type: `integer`):

How many times to retry a profile on a fresh proxy IP after TikTok serves a block page. A residential pool contains both clean and flagged addresses, so rotating is what actually fixes a refusal — and a block page costs about 20 KB against a real profile's 357 KB, making retries cheap. Raise this if you still see NO\_STATE\_BLOB errors.

## `flattenOutput` (type: `boolean`):

Emit flat dot-notation columns with arrays joined by ' | '. Use for spreadsheets; leave off for warehouses.

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

Strongly recommended: TikTok blocks datacenter IP ranges aggressively. If you see HTTP 403 or NO\_STATE\_BLOB errors, enable the Apify proxy with the RESIDENTIAL group. Running without a proxy is cheaper and works from some ranges, so it is worth trying first on a small list.

## Actor input object example

```json
{
  "profiles": [
    "@gymshark",
    "@duolingo",
    "@nasa"
  ],
  "sourceDatasetField": "handle",
  "minFollowers": 0,
  "businessAccountsOnly": false,
  "withContactEmailOnly": false,
  "maxConcurrency": 10,
  "requestTimeoutSecs": 30,
  "maxRetries": 2,
  "blockedRetries": 3,
  "flattenOutput": false,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

One dataset item per target. Creator records carry recordType 'creator'; video records carry 'video'.

# 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 = {
    "profiles": [
        "@gymshark",
        "@duolingo",
        "@nasa"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("eiv/tiktok-creator-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 = { "profiles": [
        "@gymshark",
        "@duolingo",
        "@nasa",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("eiv/tiktok-creator-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 '{
  "profiles": [
    "@gymshark",
    "@duolingo",
    "@nasa"
  ]
}' |
apify call eiv/tiktok-creator-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,eiv/tiktok-creator-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/Ci2UdN1Pga1wMqO4d/builds/aORGLV7ZHQ3m8eO43/openapi.json