TikTok
Every TikTok endpoint, with real request/response examples.
Base path: /v1/tiktok. Served by LamaTok (primary) falling back to
scraptik — see Introduction for how that fallback works.
All example responses on this page are real, live data captured against these endpoints, not fabricated samples.
Profile
GET /v1/tiktok/profile| Parameter | Required | Description |
|---|---|---|
username | Yes | TikTok handle, no @ |
curl 'https://api.fluxcrawl.dev/v1/tiktok/profile?username=tiktok' \
-H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": {
"username": "tiktok",
"display_name": "TikTok",
"followers": 95800000,
"verified": true
},
"meta": { "credits_used": 1 }
}Posts
GET /v1/tiktok/posts| Parameter | Required | Description |
|---|---|---|
username | Yes | TikTok handle, no @ |
count | No | Requested page size — see caveat below |
curl 'https://api.fluxcrawl.dev/v1/tiktok/posts?username=tiktok&count=3' \
-H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": [
{
"id": "7680721699171601694",
"text": "this summer was all about the classic hits. here's to the ones that never got away 💿 #SongsofTheSummer2026",
"likes": 14200,
"comments": 2458
}
],
"meta": { "credits_used": 1 }
}count is only approximate
This endpoint's actual page size depends on which provider answers.
LamaTok's count is roughly respected (asking for 10 reliably returns 10;
small values like 1 or 3 can return slightly more). scraptik, the
fallback, ignores page-size parameters entirely and returns its own fixed
small batch regardless of count. Don't rely on count for exact
pagination today.
Post
GET /v1/tiktok/post| Parameter | Required | Description |
|---|---|---|
id | Yes | The post/video ID |
curl 'https://api.fluxcrawl.dev/v1/tiktok/post?id=7680721699171601694' \
-H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": {
"id": "7680721699171601694",
"text": "this summer was all about the classic hits. here's to the ones that never got away 💿 #SongsofTheSummer2026",
"likes": 14200,
"comments": 2458
},
"meta": { "credits_used": 1 }
}Comments
GET /v1/tiktok/comments| Parameter | Required | Description |
|---|---|---|
id | Yes | The post/video ID to fetch comments for |
count | No | Page size — confirmed exact on both providers |
curl 'https://api.fluxcrawl.dev/v1/tiktok/comments?id=7680721699171601694&count=1' \
-H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": [
{
"id": "7680727229790126861",
"text": "yoo tiktok has tiktok",
"likes": 665
}
],
"meta": { "credits_used": 1 }
}Search
GET /v1/tiktok/search| Parameter | Required | Description |
|---|---|---|
query | Yes | Keyword to search users by |
curl 'https://api.fluxcrawl.dev/v1/tiktok/search?query=tiktok' \
-H 'X-API-Key: YOUR_KEY'{
"success": true,
"platform": "tiktok",
"data": [
{
"username": "tiktokcreators",
"display_name": "tiktok creators",
"followers": 8826760,
"verified": true
}
],
"meta": { "credits_used": 1 }
}Why this one always comes from scraptik
LamaTok has no user-search endpoint — its /v2/search returns TikTok
video results, not creators, which doesn't match the shape above. Fluxcrawl
detects that and falls straight through to scraptik for this endpoint
specifically. You don't need to do anything differently; it's mentioned
here so a slower or differently-shaped response on this one endpoint
doesn't come as a surprise.