TikTok Profile Scraper — exact follower, like and video counts

This Actor collects public TikTok profiles by handle. It returns exact follower, following, like and video counts — 95200000, not the rounded "95.2M" the profile page displays — plus bio, nickname, verification status and avatar.

No TikTok account, login or cookies are used — this reads what a logged-out visitor sees on the public profile.

What it returns

Field	Type	Notes
username	string	The @handle without the @
nickname	string	Display name
biography	string	Bio text
followerCount	number	Exact, e.g. 95200000 — the page shows "95.2M"
followingCount	number	Accounts the profile follows
likeCount	number	Total hearts across the account
videoCount	number	Videos posted
isVerified	boolean	Whether TikTok shows the blue check
profileImageUrl	string	Full-size avatar
handle, sourceUrl, collectedAt	string	Provenance for every row

Input

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

Field	Description
profiles	Handles, @handles or tiktok.com profile URLs. Required, 1–500.
maxItems	Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below.
concurrency	Profiles fetched in parallel. Default 5.

All three spellings of the same account collapse to one fetch, so a mixed list is never billed twice.

How it reads exact counts

The TikTok profile page ships its own rehydration state as an embedded JSON blob, and this Actor reads the counts straight out of it rather than parsing the rendered page. That blob carries followerCount, followingCount, heartCount and videoCount as integers, which is why this Actor returns 95200000 where the visible page rounds to "95.2M".

Because that blob is part of the logged-out page, no TikTok account, session cookie or msToken is involved at any point.

Use cases

• Influencer vetting and audience-size verification before a paid collaboration
• Tracking creator growth over time by re-running on a schedule
• Brand and competitor monitoring across a set of TikTok accounts
• Ranking a creator shortlist by exact follower and like volume
• Enriching a partner, talent or affiliate database

Reliability

Measured across 30 well-known accounts in one run: 30/30 collected at roughly a quarter-second each, every schema field populated by real values.

Counts come from the page's own embedded state, so they are exact integers rather than the rounded display text. An account that returns no readable identity or counts is recorded under failures rather than emitted as an all-null row counted as a success, and a run in which every handle failed exits with an error.

Frequently asked questions

How do I scrape TikTok profiles without logging in? Put the handles, @handles or tiktok.com profile URLs in the profiles input and run this Actor. It reads the public, logged-out profile page, so no TikTok account, cookie or session token is required.

Is the follower count exact or rounded? Exact. The TikTok Profile Scraper returns followerCount as 95200000 where the page renders "95.2M", and likeCount, followingCount and videoCount are exact integers too.

What identifier format does the input take? Any of three, and they are treated as the same account: a bare handle (nba), an @handle (@khaby.lame) or a full profile URL (https://www.tiktok.com/@nba).

How many profiles can one run collect? Up to 500 per run, which is the ceiling on the profiles input, and this Actor returns one row per profile.

Does it return videos, comments, hashtags or sounds? No. This Actor returns profile-level fields only — the ten columns listed above.

What happens with a handle that does not exist? It is recorded under failures in the run's SUMMARY and the rest of the batch still returns.

Can I search TikTok by keyword or hashtag? No. You supply the handles — the TikTok Profile Scraper does not do discovery.

Limitations

Profile-level data only: no videos, comments, hashtag or keyword search, no sounds, and no follower lists. Private accounts expose only what TikTok publishes on the public profile. Only tiktok.com URLs are accepted.

Free plan limit

Runs started from an Apify free plan stop at 250 requests and 250 results, and the run reports that it reached the limit. Any paid plan runs the full input and maxItems you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not cover for free-plan runs. It binds on requests as well as results so that a large input list cannot spend those fetches for rows the run will not return.