TikTok Creator Search Scraper

Find and enrich TikTok creators at scale — by keyword or by direct profile — and get every result as a clean, structured dataset row. One creator = one row, with their latest videos attached inside that same row. Built for speed, stability, and easy automation.

Why this actor

• One row per creator. Full profile + recent videos live in a single clean record. No noisy per-video rows to clean up later.
• Two ways to find creators. Look up known handles/links, or discover new creators by topic (e.g. cooking, gym tips).
• Full enrichment, on by default. Followers, following, hearts, video count, verified status, bio, region, and bio link — plus plays/likes/comments on each recent video.
• Streams to the dataset. Results are written as they are found, so long runs stay fast and memory-stable.
• Real-time webhook. Push every creator to your CRM, Slack, Zapier, Make, or custom API the moment it's collected.
• Parallel by design. Work runs concurrently to finish jobs quickly.

Use cases

• Influencer & creator discovery — build targeted lists by niche, then enrich them.
• Outreach & talent sourcing — pull verified creators with real follower counts and bio links for outreach.
• Competitor & market research — map who's active in a category and what they're posting.
• Agency pipelines — feed clean creator rows straight into a CRM or report.
• LLM / AI agents — structured JSON output is ideal for agents that need reliable, field-level creator data (see below).

LLM & MCP support

The actor is designed to be called programmatically:

• Structured output. Every record uses stable, human-readable field names (uniqueId, followerCount, heartCount, recentVideos, …), so LLMs and automation can parse results without custom glue.
• Apify MCP. Run this actor directly from an LLM agent through the Apify MCP server — pass the input fields as normal parameters and read the dataset back as JSON.
• Webhook-friendly. Point webhookUrl at your agent's ingest endpoint to receive each creator the instant it's found.

Input

All inputs are optional to prefill — the actor ships with example values so you can click Start immediately.

Two sections appear in the UI — Discover by keyword is enabled by default (fill keywords to run). You can also enable the username/URL section.

🔎 Discover by keyword (enabled by default)
kwEnable	Toggle this section on/off	true
accountKeywords	Topics to discover creators for (e.g. cooking)	cooking
accountsPerKeyword	Max creators kept per discovery keyword (1–50)	15
kwIncludeRecentVideos	Attach each discovered creator’s videos inside their row	true
kwRecentVideosMax	How many recent videos per creator	12
kwVideoEngagement	Add plays/likes/comments to each recent video	true
kwVideoAccountDetails	Add creator stats onto each video	false
kwVideoMinPlays	Keep only videos above this play count (0 = off)	0
kwVideoPublishedWithin	Time window (any / 7d / 30d / 90d)	any

👤 Discover by username / URL (off by default)
urlEnable	Toggle this section on/off	false
---	---	---
accountUsernames	TikTok usernames without @ (e.g. charlidamelio)	tiktok
accountUrls	Full profile links (https://www.tiktok.com/@username)	(empty)
urlIncludeRecentVideos	Attach each creator’s latest videos inside their row	true
urlRecentVideosMax	How many recent videos per creator	12
urlVideoEngagement	Add plays/likes/comments to each recent video	true
urlVideoAccountDetails	Add creator stats onto each video	false
urlVideoMinPlays	Keep only videos above this play count (0 = off)	0
urlVideoPublishedWithin	Time window (any / 7d / 30d / 90d)	any

Output & delivery
webhookUrl	Optional real-time push URL (JSON or Slack)	(empty)
webhookFormat	json (full record) or slack (short message)	json
includeRaw	Attach extended source fragments (advanced)	false

Quick starts

Look up specific creators

{
  "enableAccounts": true,
  "accountMode": "url",
  "accountUsernames": ["tiktok", "charlidamelio"]
}

Discover creators by topic (with their videos)

{
  "enableAccounts": true,
  "accountMode": "keyword",
  "accountKeywords": ["cooking", "gym tips"],
  "accountsPerKeyword": 20,
  "accountFetchRecentVideos": true
}

Output

One dataset row per creator, streaming in as results arrive. Recent videos (when enabled) are embedded in a recentVideos array on that same row — no extra rows.

Creator row

{
  "featureType": "account",
  "url": "https://www.tiktok.com/@cookingwithlynja",
  "uniqueId": "cookingwithlynja",
  "nickname": "Lynja",
  "verified": true,
  "followerCount": 22300000,
  "heartCount": 461800000,
  "videoCount": 428,
  "bioLink": "linktr.ee/cookingwithlynja",
  "discoveryQuery": "cooking",
  "recentVideos": [
    {
      "videoId": "7124377958592138539",
      "description": "Gender Reveal Ravioli #tiktoktaughtme",
      "playCount": 6100000,
      "diggCount": 699300,
      "commentCount": 5120,
      "shareCount": 980
    }
  ]
}

Field reference

Creator (account) uniqueId · nickname · signature · verified · followerCount · followingCount · heartCount · videoCount · avatarUrl · bioLink · profileRegion · createTime · discoveryQuery

Recent video (inside recentVideos) videoId · description · author · playCount · diggCount · commentCount · shareCount · musicTitle · musicAuthor · hashtags · durationSec · coverUrl · url

Output & delivery

• Dataset (streaming). Every creator is saved the moment it's found — the run never buffers the whole result set, so it stays fast and stable on large jobs.
• Webhook (optional). Set webhookUrl to POST each creator in real time, in json (full record) or slack (short message) format. Webhook failures never stop the run or the dataset writes.
• Pay-per-event ready. In Apify Console → your actor → Monetization, add a pricing event named result (this is what the actor charges per saved creator). If you prefer per-feature pricing, set the TIKTOK_PPE_PER_FEATURE=1 environment variable and instead name the event account — every row this actor emits is a creator row, so that's the only event used. (Optional: override the event name with TIKTOK_PPE_EVENT_NAME.) See the Pay-per-event docs.

Local testing

1. Copy .env.example → .env and add your proxy credentials.
2. Edit local.creators.input.json (already prefilled with example creators).
3. Run:

   npm install
   npm run start:local
   

Results are written to output/local_creators_results.json.

---

Custom work? Let's build it.

Need something tailor-made? I build custom scraping actors for any platform and web apps of any kind — dashboards, APIs, automation, and full data pipelines.

• Email: dubem115@gmail.com
• GitHub: https://github.com/DrunkCodes

Reach out and let's ship your project.