Douyin creator engagement and follower trends
Douyin creator engagement and follower trends: inspect inputs, account history fields, pagination and limits, then run a local simulated request.
Copy the agent prompt manually
What this capability does
Douyin creator engagement and follower trends uses /v1/douyin/users/history; GET returns data.item; POST returns data.items with account history objects.
This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.
- Capability: douyin.users.history
- Pagination: no cursor pagination; do not repeatedly request another page.
Input contract
Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.
- GET: supply exactly one of id.
- POST: supply exactly one of ids.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Optional / conditional | The account's numeric Douyin ID (uid), a string of digits; not the token starting with MS4w that the profile endpoint takes. Nor is it the Douyin handle (username, often digits too): the uid is ext.uid in what douyin.users.get returns with view=full. Accounts with very few followers have no such data (a few hundred followers failed, over thirty thousand worked when tried), and retrying does not help | — | "66598046050" |
| GET | window | string | Optional / conditional | How many of the most recent days to count: 7 or 30 | ["7d","30d"] | — |
| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |
| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |
| POST | ids | array | Required | Up to five numeric Douyin account IDs (uid), each a string of digits. If one of them does not exist, the whole batch fails. The uid is ext.uid in what douyin.users.get returns with view=full, not the Douyin handle (username); an account with very few followers counts as failing too, and asking one at a time shows which | maxItems: 5 | ["66598046050","104255897823"] |
| POST | window | string | Optional / conditional | How many of the most recent days to count: 7 or 30 | ["7d","30d"] | — |
| POST | view | string | Optional / conditional | How much of each item to return | ["compact","standard","full"] | — |
| POST | fields | array | Optional / conditional | Return only these fields | maxItems: 64 | — |
Try it locally
Use demo to inspect the fields, then explicitly select simulated with a customer test key to exercise settlement. Never put a customer key in a URL.
{
"capability": "douyin.users.history",
"method": "GET",
"params": {
"id": "66598046050"
}
}Output fields and interpretation
The account_history object permits missing or null values; do not replace missing measurements with zero. This table shows the main structure; the object reference covers nested fields.
| Field | Type | Meaning | Source scope |
|---|---|---|---|
| id | string | null | The account's numeric ID (Douyin's uid): the one the request gave | Douyin |
| name | string | null | Display name | Douyin |
| url | string | null | Link to the profile; pass it unchanged to the account endpoint | Douyin |
| avatar_url | string | null | Avatar (standard view and up) | Douyin |
| days | integer | null | How many of the most recent days the figures cover | Douyin |
| gained | object | null | What was gained over the period | Douyin |
| gained.followers | integer | null | Net new followers; negative when followers were lost | Douyin |
| gained.likes | integer | null | New likes | Douyin |
| gained.comments | integer | null | New comments | Douyin |
| gained.shares | integer | null | New shares | Douyin |
| gained.posts | integer | null | Posts published | Douyin |
| change | object | null | Change against the period of the same length before it, as a ratio: 0.3 is 30% more, -0.5 is half as much | Douyin |
| change.followers | number | null | Change in net new followers | Douyin |
| change.likes | number | null | Change in new likes | Douyin |
| change.comments | number | null | Change in new comments | Douyin |
| change.shares | number | null | Change in new shares | Douyin |
| change.posts | number | null | Change in posts published | Douyin |
| totals | object | null | The account's totals as of now (standard view and up) | Douyin |
| totals.followers | integer | null | Followers (standard view and up) | Douyin |
| totals.likes | integer | null | Likes received in all (standard view and up) | Douyin |
| totals.posts | integer | null | Posts (standard view and up) | Douyin |
| approximate | array | null | Which numbers of this item are approximate or lower bounds; absent when all are exact | Douyin |
| approximate[].field | string | null | Path of the field, such as metrics.views | Douyin |
| approximate[].kind | string | null | Approximate, or a lower bound | Douyin |
| ext | object | The platform's own fields (full view). | Douyin |
Limits and checks
A successful request does not establish full coverage. Preserve the request ID, observation time, parameters and cursor, and inspect the returned items before analysis.
Local simulation uses TEST credits only. Real provider calls, real payments and external email are disabled. Historical reference-site prices are not DataNavoAPI prices.
- Verify media URLs, counts and optional fields individually.
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗