DataNavoAPI / ANSWERS / DOUYIN

What role does Xingtu data play in creator research?

What role does Xingtu data play in creator research? Follow concrete contracts, examples and reviewable steps using Douyin.

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

Answer

Start by inspecting the contracts and local samples for Douyin Xingtu creator profile, Douyin Xingtu creator rate card. Establish the input for douyin.xingtu.creators.get, then check whether its creator object contains the fields your task needs.

Document the input scope, sampling rule and intended use, and preserve request IDs and missing-field markers. An API supplies the contracted sample; interpretation still requires checks of context and representativeness.

02

Relevant contracts

CapabilityObjectShapePagination
douyin.xingtu.creators.getCreatoritemNo cursor
douyin.xingtu.creators.rates.getCreator ratesitemNo cursor
03

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 / conditionalXingtu creator ID, a string of digits; not the Douyin account ID: take it from the Xingtu creator search—"6763236383382306828"
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—
POSTidsarrayRequiredSeveral Xingtu creator IDs, each a string of digitsmaxItems: 50["6763236383382306828","6816144920949030920"]
POSTviewstringOptional / conditionalHow much of each item to return["compact","standard","full"]—
POSTfieldsarrayOptional / conditionalReturn only these fieldsmaxItems: 64—
04

Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

json
{
  "capability": "douyin.xingtu.creators.get",
  "method": "GET",
  "params": {
    "id": "6763236383382306828"
  }
}
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 ↗