Douyin creator engagement and follower trends API
Get how a Douyin account's numbers moved over the last 7 or 30 days, by its numeric ID, from the platform's own index tool: net new followers, new likes, comments, shares and posts, each as a ratio against the period before, and the totals now; up to five accounts in one request. It is one period's sum, not a day-by-day series. One object a call; up to 5 in one request with ids; $0.0020 per call. Errors, timeouts and objects that do not exist are not charged; an empty result is free.
Try it
Change a value and the request on the right follows.Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 50 calls.
Used to call POST /v1/douyin/creators/trends/compare? It is this address now. What changed for old endpoints
curl -G "https://api.dataxapi.com/v1/douyin/users/history" \ --data-urlencode "id=66598046050" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "76f21d2b-218b-47ce-855e-19fb2cc51fdc",
"data": {
"item": {
"id": "65485320678",
"name": "阿杰爱折腾",
"url": "https://www.douyin.com/user/65485320678",
"avatar_url": "https://p3-pc.douyinpic.com/aweme/100x100/aweme-avatar/tos-cn-avt-0015_2ed168d1dc1b7e7b888e.jpeg",
"days": 30,
"gained": {
"followers": 661489,
"likes": 255080710,
"comments": 48099,
"shares": 38207194,
"posts": 437
},
"change": {
"followers": 0.7285514941831903,
"likes": 0.2256968601585644,
"comments": -0.12905153369789593,
"shares": 0.04085150466802108,
"posts": -0.126
},
"totals": {
"followers": 203357430,
"likes": 19128275335,
"posts": 12381
}
}
},
"warnings": [],
"meta": {
"capability": "douyin.users.history",
"result_status": "complete",
"fetched_at": "2026-10-12T21:54:08.000Z",
"cached": false,
"replayed": false,
"unavailable": {},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a response recorded 2026-10-12 21:54 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.
Size as sent: 911 B in the standard view (705 B compact, 911 B full).
{
"code": "ok",
"request_id": "539ac011-d5c1-4213-986f-51a7d85ef2a8",
"data": {
"items": [],
"missing": [
{ "id": "63447420393", "reason": "not_found" },
{ "id": "62668992497", "reason": "not_found" }
]
},
"warnings": [],
"meta": {
"capability": "douyin.users.history",
"result_status": "empty",
"fetched_at": "2026-10-12T21:53:26.000Z",
"cached": false,
"replayed": false,
"unavailable": {},
"billing": { "amount": "0", "currency": "USD", "balance_after": "10" }
}
}The answer to a request with ids.
From a recording of 2026-10-12 21:53 UTC, edited by hand to show this case. The request ID and balance are made up.
Size as sent: 417 B in the standard view (417 B compact, 417 B full).
curl -G "https://api.dataxapi.com/v1/douyin/users/history" \ --data-urlencode "id=66598046050" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.douyin.users.history(id="66598046050") print(result["data"]["item"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.douyin.users.history({ id: "66598046050" });
console.log(result.data.item);dataxapi call douyin.users.history id=66598046050
{
"mcpServers": {
"dataxapi": {
"type": "http",
"url": "https://api.dataxapi.com/mcp",
"headers": {
"Authorization": "Bearer ${DATAXAPI_API_KEY}"
}
}
}
}Add this to your MCP client, then ask your agent to call douyin.users.history.
Parameters
id, idsThe account's numeric Douyin ID (uid), a string of digits; not the token starting with MS4w that the profile endpoint takes. Example: 66598046050.
id, idsUp to five numeric Douyin account IDs (uid), each a string of digits. If one of them does not exist, the whole batch fails. Example: ["66598046050","104255897823"]. At most 5 in one request.
How many of the most recent days to count: 7 or 30. Values: 7d (default), 30d. Example: 7d.
How much of each item to return. All three cost the same. Values: compact, standard (default), full.
Return only these fields. Each by its path, such as author.name.
A request with ids is a POST with a JSON body; every other request is a GET.
Known limits
- One object per call: there is nothing to page.
- Up to 5 objects come back in one call with
ids; there is no next page.
Returned fields
data.item is one account recent change object. Preview: the structure may change, announced beforehand. With ids the answer is data.items, and what was not found is listed in data.missing.
The account's numeric ID (Douyin's uid): the one the request gave
Display name
Link to the profile; pass it unchanged to the account endpoint
Avatar
How many of the most recent days the figures cover
What was gained over the period
Show all 24 fields →
Net new followers; negative when followers were lost
New likes
New comments
New shares
Posts published
Change against the period of the same length before it, as a ratio: 0.3 is 30% more, -0.5 is half as much
Change in net new followers
Change in new likes
Change in new comments
Change in new shares
Change in posts published
The account's totals as of now
Followers
Likes received in all
Posts
Which numbers of this item are approximate or lower bounds; absent when all are exact
Path of the field, such as metrics.views
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 387 B, standard 593 B, full 593 B (measured on the response recorded 2026-10-12 21:54 UTC).
When you are charged
X-Max-Price to refuse anything above your own limit)Prices as read 2026-10-21 09:10 UTC, under price book 2, in effect since 2026-10-17 11:00 UTC; the Playground reads the price in force before a run.
If the object does not exist
The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted.
With ids, each ID that was not found is listed in data.missing with the reason, and the rest come back; when none is found the result is empty and nothing is charged.
Errors
What this endpoint can answer with; codes all endpoints share are on the full list.
invalid_paramsA parameter is invalidRetry: After a fixNoinsufficient_balanceThe balance is too lowRetry: After a fixNonot_foundThe object does not exist, is private or was deletedRetry: NoNouncharged_cost_limitToo many of this account's calls today returned nothing and were not charged; endpoints of this kind can be called again tomorrow (UTC)Retry: YesNoupstream_failedThe data source failedRetry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the Douyin creator engagement and follower trends API cost?
$0.0020 per call. The most one call can cost is $0.0020.
When am I not charged?
Errors, timeouts and objects that do not exist are not charged; an empty result is free.
Can I fetch several in one request?
Up to 5 objects come back in one call with ids; there is no next page.
What happens if the object does not exist?
The answer is 404 not_found and nothing is charged. reason says which: not_found (it does not exist) or private_or_deleted. With ids, each ID that was not found is listed in data.missing with the reason, and the rest come back; when none is found the result is empty and nothing is charged.
All 34 Douyin endpoints
Use it in your AI
Copy this prompt
Your API key is built in, so there is nothing to configure.
No account yet? Sign-up takes an email and no card, and a failed call is never charged.
Paste it into your agent
It reads the page the prompt points to and connects itself.
Now ask something
Use one of these, or your own words.
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call douyin.users.history.Other clients →Show the text
Use the DataXAPI endpoint douyin.users.history (Douyin creator engagement and follower trends). Get how a Douyin account's numbers moved over the last 7 or 30 days, by its numeric ID, from the platform's own index tool: net new followers, new likes, comments, shares and posts, each as a ratio against the period before, and the totals now; up to five accounts in one request. It is one period's sum, not a day-by-day series. Call GET https://api.dataxapi.com/v1/douyin/users/history with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - id: The account's numeric Douyin ID (uid), a string of digits; not the token starting with MS4w that the profile endpoint takes. Example: 66598046050. - ids: Up to five numeric Douyin account IDs (uid), each a string of digits. If one of them does not exist, the whole batch fails. Example: ["66598046050","104255897823"]. At most 5 in one request. - window: How many of the most recent days to count: 7 or 30. Values: 7d (default), 30d. Example: 7d. - view: How much of each item to return. All three cost the same. Values: compact, standard (default), full. - fields: Return only these fields. Each by its path, such as author.name. Price: $0.0020 per call. Errors, timeouts and objects that do not exist are not charged; an empty result is free. The answer is JSON: data.item holds account recent change; meta.billing.amount is what this call was charged. Example: curl -G "https://api.dataxapi.com/v1/douyin/users/history" \ --data-urlencode "id=66598046050" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/douyin/users/history.md
Names and identifiers
- In Chinese
- 抖音达人互动与粉丝趋势 API
- Endpoint ID
douyin.users.history- Endpoint
GET / POST /v1/douyin/users/history
Start with one key.
207 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.