Douyin trend-index creator core metrics
Douyin trend-index creator core metrics: inspect inputs, creator index metrics fields, pagination and limits, then run a local simulated request.
Copy the agent prompt manually
What this capability does
Douyin trend-index creator core metrics uses /v1/douyin/index/creators/metrics; GET returns data.item with creator index metrics objects.
This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.
- Capability: douyin.index.creators.metrics
- 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.
- Only send fields defined for this method; unknown fields are rejected before execution.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Required | 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 | 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 | — |
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.index.creators.metrics",
"method": "GET",
"params": {
"id": "66598046050"
}
}Output fields and interpretation
The index_creator_metrics 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 |
|---|---|---|---|
| creator_id | string | null | The account's numeric ID (Douyin's uid): the one the request gave | Douyin |
| average_7d | object | null | Daily averages over the last week | Douyin |
| average_7d.likes | number | null | New likes a day, on average over the last week | Douyin |
| average_7d.follows | number | null | Follows a day, on average over the last week, as the platform counts them: not the net gain in followers: the same platform's like figure comes to 2 to 10 times the net daily gain, and is above 0 for an account that lost followers. The platform does not say how it is counted: use it for trends and to compare accounts, not as a net gain | Douyin |
| average_7d.shares | number | null | New shares a day, on average over the last week | Douyin |
| average_7d.comments | number | null | New comments a day, on average over the last week | Douyin |
| average_30d | object | null | Daily averages over the last month | Douyin |
| average_30d.likes | number | null | New likes a day, on average over the last month | Douyin |
| average_30d.follows | number | null | Follows a day, on average over the last month, as the platform counts them; as above, not the net gain in followers | Douyin |
| average_30d.shares | number | null | New shares a day, on average over the last month | Douyin |
| average_30d.comments | number | null | New comments a day, on average over the last month | Douyin |
| change_7d | object | null | The last week's daily averages against the week before, as a ratio: 0.3 is 30% more, -0.5 is half as much | Douyin |
| change_7d.likes | number | null | Change in new likes a day | Douyin |
| change_7d.follows | number | null | Change in follows a day (as the platform counts them, not the net gain) | Douyin |
| change_7d.shares | number | null | Change in new shares a day | Douyin |
| change_7d.comments | number | null | Change in new comments a day | Douyin |
| change_30d | object | null | The last month's daily averages against the month before, written the same way | Douyin |
| change_30d.likes | number | null | Change in new likes a day | Douyin |
| change_30d.follows | number | null | Change in follows a day (as the platform counts them, not the net gain) | Douyin |
| change_30d.shares | number | null | Change in new shares a day | Douyin |
| change_30d.comments | number | null | Change in new comments a day | 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 ↗