TikTok User Scraper - Profiles, Followers & Stats (No Login)

⚡ TikTok User Scraper — Profiles, Followers & Stats (No Login, No API Key, No Proxy)

Get full TikTok profile data without a login, API key, or proxy. Feed it usernames and get back followers, following, total likes (hearts), video count, bio, verified status, avatar and secUid — ideal for influencer discovery, creator vetting, lead lists and audience research. Export to JSON, CSV or Excel, call the API, or deliver to Notion. $0.35 per 1,000 profiles plus a $0.001 run-start fee, flat on every Apify plan — the cheapest TikTok profile scraper on the market.

> No account. No proxy. Paste handles and run.

Why this scraper wins

• 🔓 Keyless & proxy-free — no login, no API key, no cookies to paste, and no proxy to buy. Paste handles, press Start.
• 🛡️ Real numbers, not degraded ones — TikTok serves rounded or decoy stats to clients it has flagged. This Actor is built so the follower, like and video counts match what you see on the profile page while logged in.
• 💸 One flat rate — $0.35 / 1,000 profiles plus $0.001 per run start. No volume tiers, no plan gates, and the cheapest rate on the market for this job.
• 🧾 Only successful look-ups are billed — misses, blocks, duplicates and empty runs cost nothing beyond the start fee.
• 🧹 Clean, flat records — one tidy object per profile, no nesting to unpack, ready for a spreadsheet or a CRM import.
• 📬 Built-in Notion delivery — push results straight into Notion via Apify connectors, zero code.

Input

Mix profiles and startUrls freely in one run; duplicates are looked up once. Input field names follow the conventions used across similar Actors, so switching over is usually a drop-in change — point your existing input at this Actor and it will normally run as-is.

Input example

{
  "profiles": ["tiktok", "@nba", "khaby.lame"],
  "startUrls": ["https://www.tiktok.com/@zachking"]
}

That run looks up four creators (the URL is reduced to the handle zachking) and returns four rows.

Throughput and your own cookie

Runs work out of the box: every handle is looked up keyless first, which is how it has always worked and needs nothing from you. When a look-up comes back empty, the run retries it through a built-in session before giving up — so you get a row instead of a gap.

That built-in session is shared across everyone using the Actor, so under heavy concurrent load it can be rate-limited. If you are pulling large lists and want throughput that nobody else can affect, paste your own TikTok sessionid into sessionCookies (Chrome: F12 → Application → Cookies → sessionid, one per line). It is entirely optional, it is used instead of the built-in session rather than on top of it, and a run with an expired or missing cookie simply falls back to the keyless path rather than failing.

Output (one record per profile)

{
  "ok": true,
  "type": "profile",
  "id": "107955",
  "uniqueId": "tiktok",
  "secUid": "MS4wLjAB...",
  "nickname": "TikTok",
  "signature": "Make every second count.",
  "verified": true,
  "avatar": "https://p16-sign-va.tiktokcdn.com/....jpeg",
  "followerCount": 94514481,
  "followingCount": 6,
  "heartCount": 460588561,
  "videoCount": 1536,
  "diggCount": 0,
  "url": "https://www.tiktok.com/@tiktok"
}

Field reference

Every field above comes from TikTok's own profile payload, so followerCount and heartCount are the real totals rather than rounded or degraded figures.

When a handle doesn't resolve

You get an explicit diagnostic row instead of a silent gap. Diagnostic rows carry ok: false, an errorCode, a human-readable error, and the profile that caused it:

{
  "ok": false,
  "errorCode": "NOT_FOUND",
  "error": "The requested resource was not found (404) or is private/suspended.",
  "profile": "handle_that_no_longer_exists"
}

None of these are charged, so feeding in a stale handle list costs you nothing for the misses — you only ever pay for rows that came back with real data.

Pricing

$0.35 per 1,000 profiles ($0.00035 each), plus $0.001 each time a run starts — flat on every Apify plan, including the free one. No volume tiers, no plan gates, and only successful look-ups are charged. This is the cheapest rate on the market for TikTok profile data.

Because the start fee is charged once per run, batching handles into one run is materially cheaper than looping one-handle runs: 100 handles in a single run costs $0.036, where 100 separate runs would cost $0.135.

Billing mechanics

Two events exist and nothing else bills:

1. Actor start — $0.001, charged once when a run begins (per GB of memory; this Actor runs at 1 GB). 2. Profile returned — $0.00035, charged the moment a real profile row is written to the dataset.

Diagnostics, duplicates, blocked look-ups and no-result runs never trigger the per-profile fee. A run that returns nothing costs only the $0.001 start fee.

Limitations — read before you scale

Stated plainly, because you should know them before you build on this:

• Look-ups are paced. The Actor deliberately spaces requests roughly one per second to stay well

inside the source's limits. Expect around 45–50 profiles per minute; a 3,000-handle run takes about an hour. The default run timeout is 60 minutes, so split very large lists across runs (or raise the timeout in the run options).

• No videos here. This Actor returns profile records only. It does not return a creator's video list,

comments, hashtags or search results — use the companion TikTok Scraper for those.

• No follower or following lists. This Actor returns the counts only, never the actual list of

accounts behind followerCount / followingCount. That is not a setting you can turn on here — use a dedicated follower-list Actor if you need the names.

• No emails or phone numbers. Only what a logged-out visitor can see on the profile: bio text,

counts, avatar, verified badge. If a creator writes their email into their bio it lands in signature, but there is no separate contact field.

• diggCount is usually 0. Most accounts hide their liked-videos count; the field is reported as TikTok

reports it rather than guessed.

• Private and region-blocked accounts return NOT_FOUND or BLOCKED rather than partial data. That is

deliberate — a diagnostic row you can act on beats a half-populated row you might trust.

• Counts are point-in-time. Follower numbers move constantly; re-run on a schedule if you need a

trend rather than a snapshot.

• Empty input stops the run. If you supply neither profiles nor startUrls, the run stops

immediately with a BAD_INPUT message and no per-profile fee is charged.

FAQ

Do I need a TikTok account, cookies, or a proxy? No. Look-ups go out keyless and the Actor runs proxy-free by default. The sessionCookies and proxyConfiguration inputs exist only for high-volume users who want a rate limit of their own — both are optional and both are empty by default.

Why are the follower counts different from what other tools return? TikTok serves degraded or decoy stats to clients it has flagged. This Actor is built to avoid that, so the numbers match what you see on the profile page.

How many handles can I pass in one run? As many as you like — there is no cap in the input. Practical limits come from pacing and the run timeout (see Limitations). The start fee is charged once per run, so batching is always cheaper.

Can I schedule it? Yes. Apify schedules work normally — a daily run over the same handle list gives you a clean follower-growth time series in the dataset.

How do I get the data out? Download the dataset as JSON, CSV, Excel or XML from the run page, hit the Dataset API from your own code, or set notionConnector to push each profile into Notion automatically.

What happens to duplicates? They are de-duplicated by handle before the look-up and again by uniqueId after it, so you are never charged twice for the same creator in one run.

Want the videos too? Use the companion TikTok Scraper for videos, hashtags, comments and search.