Is a Douyin search index the same as a search count?
Is a Douyin search index the same as a search count? 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 trend-index keyword trends. Establish the input for douyin.index.keywords.history, then check whether its keyword_history object contains the fields your task needs.
Align the metric name, denominator, observation window and capture time first. Indices, reads, impressions, plays, engagement and cost are different measurements. A missing value means unavailable, not zero; likes cannot substitute for reads.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| douyin.index.keywords.history | Keyword history | items | No 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 keyword.
- POST: supply exactly one of keywords.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | keyword | string | Optional / conditional | One keyword, at most 50 characters and without a comma; letter case does not matter | — | "咖啡" |
| GET | since | string | Required | The first day wanted: the China-time (UTC+8) calendar day this moment falls on; 2026-09-01 means 1 September | — | "2026-09-01T00:00:00Z" |
| GET | until | string | Required | The last day wanted, read the same way. The platform publishes a day or two late: a day it has no figure for yet has a null index | — | "2026-09-30T00:00:00Z" |
| 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 | — |
| POST | keywords | array | Required | One to five keywords, each at most 50 characters and without a comma; letter case does not matter. One item comes back per keyword that has figures; a keyword the index does not cover is not in the answer | maxItems: 5 | ["咖啡","CityWalk"] |
| POST | since | string | Required | The first day wanted: the China-time (UTC+8) calendar day this moment falls on; 2026-09-01 means 1 September | — | "2026-09-01T00:00:00Z" |
| POST | until | string | Required | The last day wanted, read the same way. The platform publishes a day or two late: a day it has no figure for yet has a null index | — | "2026-09-30T00:00:00Z" |
| POST | view | string | Optional / conditional | How much of each item to return | ["compact","standard","full"] | — |
| POST | fields | array | Optional / conditional | Return only these fields | 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.index.keywords.history",
"method": "GET",
"params": {
"since": "2026-09-01T00:00:00Z",
"until": "2026-09-30T00:00:00Z",
"keyword": "咖啡"
}
}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 ↗