TikTok API for creator and account data
Look up any public TikTok creator by username and read followers, total likes, video count and engagement, plus a bio-code check that proves account ownership. No sandbox review, no application, no waiting.
- Endpoints for TikTok
- 46
- Free to start
- 500 requests
- Paid from
- $69/ 30 days
One request, no application
Send a key, get an answer. Every endpoint on this page uses the same header, the same envelope and the same error codes as the other six platforms.
curl "https://api.playersells.com/v2/accounts/tiktok/khaby.lame" \
-H "Authorization: Bearer $PLAYERSELLS_API_KEY"What the TikTok API returns
- username, nickname and signature (bio)
- follower and following counts
- total likes across the account
- video count
- verified flag
- avatar URL
- follower history for accounts in the catalog
Where the data comes from
Our own TikTok crawler, reading the public profile payload. Counts come from the statsV2 fields specifically, because TikTok's older stats block overflows a 32-bit integer on large accounts and silently reports the wrong number of likes.
What this API cannot do
- Like totals recorded before 24 August 2026 were quantised to the nearest 100,000 by the source we then used, so growth measured across that date is unreliable. Readings after it are exact.
- Account creation date is not exposed by TikTok anywhere we can read it, and is returned as null.
- Per-video comment threads and audience demographics are not available.
TikTok endpoints
18 built specifically for TikTok, plus 28 that cover every platform.
Specific to TikTok
| Endpoint | What it does | Scope |
|---|---|---|
GET/accounts/{platform}/{handle} | Check one account against our catalog | directory:read |
GET/accounts/{platform}/{handle}/livelive | Check one account live, at the source | scrape:live |
GET/accounts/resolve | Find one handle on every platform at once | directory:read |
GET/directory/{platform} | List and filter a catalog | directory:read |
GET/directory/{platform}/{id} | One account or channel | directory:read |
GET/directory/{platform}/{id}/growth | Daily audience history | directory:read |
GET/directory/{platform}/{id}/followers | Inbound graph edges | directory:read |
GET/directory/{platform}/{id}/following | Outbound graph edges | directory:read |
POST/directory/{platform}/bulk | Resolve up to 100 records at once | directory:read |
GET/directory/{platform}/facets | Distribution of the catalog | directory:read |
GET/directory/search | Search every platform at once | directory:read |
GET/people/lookup | Find one handle across every catalog | directory:read |
GET/people/search | Find accounts matching audience and engagement criteria | directory:read |
GET/scrape/tiktok/verifylive | Prove ownership of a TikTok account | scrape:live |
GET/marketplace/listings | Browse active marketplace listings | marketplace:read |
GET/tools/audience-finder | Search the Telegram, TikTok and X catalog | tools:use |
POST/tools/tiktok/engagementlive | Measure a TikTok account's engagement | tools:use |
POST/tools/tiktok/moneylive | Estimate TikTok brand-deal earnings | tools:use |
Across all platforms
| Endpoint | What it does | Scope |
|---|---|---|
GET/accounts/platforms | What a check can answer, per platform | directory:read |
POST/accounts/check | Check up to 50 accounts at once | directory:read |
GET/directory | Catalog capability map | directory:read |
GET/scrape/status | Live backend health and capacity | scrape:live |
GET/insights/audience | Who follows an account, and what they have in common | insights:read |
GET/research/findings | Findings the research engine is willing to state | research:read |
GET/research/findings/{id} | One finding with its full test history | research:read |
GET/research/runs | Research pass history | research:read |
GET/research/events | The research changelog | research:read |
GET/engines | Operational health of every insight engine | engines:read |
GET/engines/{key} | One engine in detail | engines:read |
GET/marketplace/listings/{id} | Get one public listing | marketplace:read |
GET/marketplace/stats | Platform totals | marketplace:read |
GET/marketplace/leaderboard | Best-selling sellers | marketplace:read |
GET/marketplace/pricing | Live fee schedule and boost packages | marketplace:read |
GET/tools | List every analysis tool | tools:use |
POST/tools/valuationlive | Value an X account | tools:use |
POST/tools/shadowban-checklive | Check an X account for visibility filtering | tools:use |
POST/tools/follower-auditlive | Audit an X account's followers for fakes | tools:use |
POST/tools/engagement-calculatorlive | Measure an X account's engagement rate | tools:use |
POST/tools/best-posting-timelive | Find when an X account should post | tools:use |
POST/tools/algorithm-scorelive | Score an X account against the ranking signals | tools:use |
POST/tools/bio-optimizerlive | Score and rewrite an X bio (AI) | tools:use |
POST/tools/profile-roastlive | Roast and fix an X profile (AI) | tools:use |
POST/tools/tweet-analyzerlive | Analyze a single X post | tools:use |
POST/tools/mention-checkerlive | See who is mentioning an X account | tools:use |
POST/tools/growth-simulator | Project how long a follower target takes | tools:use |
GET/tools/profile-piclive | Fetch an X profile picture URL | tools:use |
TikTok API questions
Do I need TikTok Developer approval for this?
No. TikTok's own API puts new applications through a sandbox audit before they can touch production data. This API reads public profile pages, so an API key is the only thing you need.
Are the like counts accurate on very large accounts?
Yes, and this is worth stating because it is a common failure. TikTok exposes stats in two blocks; the older one stores like totals in a 32-bit field that overflows past roughly 2.1 billion, reporting a wrapped negative number. We read statsV2, which does not, so a creator with three billion likes reports three billion.
Can I verify a TikTok account owner?
Yes. The owner adds a short code to their bio and you call the verification endpoint with the username and the code. It reads the signature field live and returns a plain true or false, plus the exact text it matched.
What happens if TikTok serves a bot challenge?
You get a 502 with an upstream_error code, which is retryable, never a 404. That distinction matters: recording a not-found against a healthy handle would poison your own database, so a challenge is always reported as a temporary source failure rather than as an answer about the account.
The same API, on six other platforms
One key, one envelope, one bill. Reading a second platform is a different path, not a different integration.