DataNavoAPI / APIS / DOUYIN

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.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

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.
02

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.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringRequiredThe 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"
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
03

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.

json
{
  "capability": "douyin.index.creators.metrics",
  "method": "GET",
  "params": {
    "id": "66598046050"
  }
}
04

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.

FieldTypeMeaningSource scope
creator_idstring | nullThe account's numeric ID (Douyin's uid): the one the request gaveDouyin
average_7dobject | nullDaily averages over the last weekDouyin
average_7d.likesnumber | nullNew likes a day, on average over the last weekDouyin
average_7d.followsnumber | nullFollows 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 gainDouyin
average_7d.sharesnumber | nullNew shares a day, on average over the last weekDouyin
average_7d.commentsnumber | nullNew comments a day, on average over the last weekDouyin
average_30dobject | nullDaily averages over the last monthDouyin
average_30d.likesnumber | nullNew likes a day, on average over the last monthDouyin
average_30d.followsnumber | nullFollows a day, on average over the last month, as the platform counts them; as above, not the net gain in followersDouyin
average_30d.sharesnumber | nullNew shares a day, on average over the last monthDouyin
average_30d.commentsnumber | nullNew comments a day, on average over the last monthDouyin
change_7dobject | nullThe last week's daily averages against the week before, as a ratio: 0.3 is 30% more, -0.5 is half as muchDouyin
change_7d.likesnumber | nullChange in new likes a dayDouyin
change_7d.followsnumber | nullChange in follows a day (as the platform counts them, not the net gain)Douyin
change_7d.sharesnumber | nullChange in new shares a dayDouyin
change_7d.commentsnumber | nullChange in new comments a dayDouyin
change_30dobject | nullThe last month's daily averages against the month before, written the same wayDouyin
change_30d.likesnumber | nullChange in new likes a dayDouyin
change_30d.followsnumber | nullChange in follows a day (as the platform counts them, not the net gain)Douyin
change_30d.sharesnumber | nullChange in new shares a dayDouyin
change_30d.commentsnumber | nullChange in new comments a dayDouyin
approximatearray | nullWhich numbers of this item are approximate or lower bounds; absent when all are exactDouyin
approximate[].fieldstring | nullPath of the field, such as metrics.viewsDouyin
approximate[].kindstring | nullApproximate, or a lower boundDouyin
extobjectThe platform's own fields (full view).Douyin
05

Unavailable fields

These published contract notes describe the capability boundary; fixtures do not establish live availability.

FieldReason
06

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.
TRY THE CONTRACT

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 ↗