How do official Douyin APIs differ from research data interfaces?
How do official Douyin APIs differ from research data interfaces? Follow concrete contracts, examples and reviewable steps using Douyin.
Copy the agent prompt manually
Answer
Start by inspecting the contracts and local samples for Douyin user profile, Douyin video search. Establish the input for douyin.users.get, then check whether its account 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.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| douyin.users.get | Account | item | No cursor |
| douyin.videos.search | Post | items | Explicit cursor |
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 / url.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Optional / conditional | Account ID (the sec_uid, the string that starts with MS4w). With only a profile link or a share text, give it as url | — | "MS4wLjABAAAAZ0aPDJzFhBrs0q3wVsp2a9WWrBuAUMsVyygoaO0bCw8" |
| GET | url | string | Optional / conditional | Link to the profile, pasted as it is: the https://www.douyin.com/user/… web link, the page a share opens on a phone, the v.douyin.com short link the app copies, or a whole share text with one of these in it. A short link is opened once to see which account it leads to | — | — |
| 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 | — |
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.
{
"capability": "douyin.users.get",
"method": "GET",
"params": {
"id": "MS4wLjABAAAAZ0aPDJzFhBrs0q3wVsp2a9WWrBuAUMsVyygoaO0bCw8"
}
}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 ↗