DataNavoAPI / APIS / DOUYIN

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.

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

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

  • GET: supply exactly one of id.
  • POST: supply exactly one of ids.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringOptional / conditionalThe 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"
GETwindowstringOptional / conditionalHow many of the most recent days to count: 7 or 30["7d","30d"]—
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—
POSTidsarrayRequiredUp 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 whichmaxItems: 5["66598046050","104255897823"]
POSTwindowstringOptional / conditionalHow many of the most recent days to count: 7 or 30["7d","30d"]—
POSTviewstringOptional / conditionalHow much of each item to return["compact","standard","full"]—
POSTfieldsarrayOptional / conditionalReturn only these fieldsmaxItems: 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.users.history",
  "method": "GET",
  "params": {
    "id": "66598046050"
  }
}
04

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.

FieldTypeMeaningSource scope
idstring | nullThe account's numeric ID (Douyin's uid): the one the request gaveDouyin
namestring | nullDisplay nameDouyin
urlstring | nullLink to the profile; pass it unchanged to the account endpointDouyin
avatar_urlstring | nullAvatar (standard view and up)Douyin
daysinteger | nullHow many of the most recent days the figures coverDouyin
gainedobject | nullWhat was gained over the periodDouyin
gained.followersinteger | nullNet new followers; negative when followers were lostDouyin
gained.likesinteger | nullNew likesDouyin
gained.commentsinteger | nullNew commentsDouyin
gained.sharesinteger | nullNew sharesDouyin
gained.postsinteger | nullPosts publishedDouyin
changeobject | nullChange against the period of the same length before it, as a ratio: 0.3 is 30% more, -0.5 is half as muchDouyin
change.followersnumber | nullChange in net new followersDouyin
change.likesnumber | nullChange in new likesDouyin
change.commentsnumber | nullChange in new commentsDouyin
change.sharesnumber | nullChange in new sharesDouyin
change.postsnumber | nullChange in posts publishedDouyin
totalsobject | nullThe account's totals as of now (standard view and up)Douyin
totals.followersinteger | nullFollowers (standard view and up)Douyin
totals.likesinteger | nullLikes received in all (standard view and up)Douyin
totals.postsinteger | nullPosts (standard view and up)Douyin
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 ↗