# Douyin trend-index keyword trends

Douyin trend-index keyword trends: inspect inputs, keyword history fields, pagination and limits, then run a local simulated request.

Canonical page: https://datanavoapi.com/en/apis/douyin/index/keywords/history/

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

## What this capability does

Douyin trend-index keyword trends uses /v1/douyin/index/keywords/history; GET returns data.items; POST returns data.items with keyword history objects.

This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.

- Capability: douyin.index.keywords.history
- Pagination: no cursor pagination; do not repeatedly request another page.

## 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 | — |

## 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.keywords.history",
  "method": "GET",
  "params": {
    "since": "2026-09-01T00:00:00Z",
    "until": "2026-09-30T00:00:00Z",
    "keyword": "咖啡"
  }
}
```

- [Open this capability in the console](https://datanavoapi.com/console/?mode=demo&capability=douyin.index.keywords.history&method=GET&params=%7B%22keyword%22%3A%22%E5%92%96%E5%95%A1%22%2C%22since%22%3A%222026-09-01T00%3A00%3A00Z%22%2C%22until%22%3A%222026-09-30T00%3A00%3A00Z%22%7D)

## Output fields and interpretation

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

| Field | Type | Meaning | Source scope |

| --- | --- | --- | --- |

| keyword | string \| null | The keyword | Douyin |

| points | array \| null | The figures day by day, one entry a day, oldest first | Douyin |

| points[].date | string \| null | The day: a calendar day in China time (UTC+8), written as midnight UTC of its date (8 a.m. that day in China); passed back as since or until it asks for that same day | Douyin |

| points[].search_index | integer \| null | Search index of the day: the platform's index of how much the keyword was searched, not a count of searches | Douyin |

| points[].composite_index | integer \| null | Composite index of the day: the platform's index of how much attention content about the keyword drew, not a count | Douyin |

| points[].notes | integer \| null | Posts about the keyword that day (standard view and up) | Douyin |

| points[].impressions | integer \| null | Times those posts were shown that day (standard view and up) | Douyin |

| points[].views | integer \| null | Times those posts were read that day (standard view and up) | Douyin |

| points[].engagements | integer \| null | Engagements with those posts that day (standard view and up) | Douyin |

| approximate | array \| null | Which numbers of this item are approximate or lower bounds; absent when all are exact | Douyin |

| approximate[].field | string \| null | Path of the field, such as metrics.views | Douyin |

| approximate[].kind | string \| null | Approximate, or a lower bound | Douyin |

| ext | object | — | Douyin |

| ext.composite_average | integer \| null | Daily average of the composite index over the period asked for (full view) | Douyin |

| ext.search_average | integer \| null | Daily average of the search index over the period asked for (full view) | Douyin |

| ext.previous_composite_average | integer \| null | Daily average of the composite index over the period of the same length before it (full view) | Douyin |

| ext.previous_search_average | integer \| null | Daily average of the search index over the period of the same length before it (full view) | Douyin |

| ext.year_ago_composite_average | integer \| null | Daily average of the composite index over the same period a year earlier (full view) | Douyin |

| ext.year_ago_search_average | integer \| null | Daily average of the search index over the same period a year earlier (full view) | Douyin |

- [Complete object reference](https://datanavoapi.com/en/docs/objects/keyword_history/)

## Unavailable fields

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

| Field | Reason |

| --- | --- |

| points.notes | platform |

| points.impressions | platform |

| points.views | platform |

| points.engagements | platform |

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

## Related pages

- [Douyin APIs](https://datanavoapi.com/en/apis/douyin/)
- [Douyin MCP](https://datanavoapi.com/en/mcp/douyin/)
- [Keyword history fields](https://datanavoapi.com/en/docs/objects/keyword_history/)
- [Is a Douyin search index the same as a search count?](https://datanavoapi.com/en/answers/douyin-search-index-vs-search-count/)
- [Can I directly compare Douyin and RedNote keyword indices?](https://datanavoapi.com/en/answers/douyin-xiaohongshu-keyword-heat/)
- [How should I interpret the Douyin keyword index?](https://datanavoapi.com/en/answers/what-is-douyin-keyword-index-ocean-engine/)
- [Analyze Douyin keyword indices and related terms](https://datanavoapi.com/en/guides/douyin-keyword-trends/)

[中文](https://datanavoapi.com/apis/douyin/index/keywords/history/)
