KeywordHistory object

A keyword's index on a platform's trend tool, day by day. The same fields on every platform. A field a platform does not show is null, and meta.unavailable names it with the reason.

Field	Type	From view	Description
`keyword`	string	compact	The keyword.
`points`	KeywordPoint[]	compact	One entry a day, oldest first.
`ext`	object	full	Platform-specific extras. Only returned with view=full. · only with view=full

KeywordPoint

Field	Type	Description
`date`	string	The day: a calendar day in China time (UTC+8), written as 00:00 UTC of that date.
`search_index`	integer \| null	That day's search index: the platform's measure of search interest, not a count of searches.
`composite_index`	integer \| null	That day's composite index: the platform's measure of attention to content about the keyword, not a count.
`notes`	integer \| null	Posts about the keyword that day.
`impressions`	integer \| null	Times those posts were shown that day.
`views`	integer \| null	Times those posts were read that day.
`engagements`	integer \| null	Interactions with those posts that day.

Example · douyin

{
  "keyword": null,
  "points": [
    {
      "date": null,
      "search_index": null,
      "composite_index": null,
      "notes": null,
      "impressions": null,
      "views": null,
      "engagements": null
    }
  ]
}

Endpoints that return a KeywordHistory

Connect once, then just ask.

Every new key comes with $0.10 to try it. One sentence connects your agent.

Start free

Connect your AI

Paste this into your agent

Read https://okdata.online/agents.md and set up okdata for me; my key is in the OKDATA_API_KEY environment variable.

Step-by-step for each app

Claude Code, Cursor, Codex and other agents that can open a link set themselves up from it.

MCP serverhttps://api.okdata.online/mcp