Zhihu hot list API
Get Zhihu's hot list: the questions on it, their rank, heat (approximate) and answer count; an entry's ID is its question's. About 30 items a call, 50 at most; $0.0020 per call. Errors and timeouts are not charged; an empty result is charged $0.0020.
Try it
Change a value and the request on the right follows.Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 50 calls.
Used to call POST /v1/zhihu/trends/hot? It is this address now. What changed for old endpoints
curl "https://api.dataxapi.com/v1/zhihu/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "1d302908-ce47-449f-bf93-d107f03ef650",
"data": {
"items": [
{
"id": "3975139299",
"name": "周末露营装备推荐",
"rank": 1,
"heat": 6030000,
"approximate": [
{ "field": "heat", "kind": "approximate" }
]
},
// … 29 more
]
},
"page": {
"next_cursor": null,
"cursor_expires_at": null,
"has_more": false,
"returned": 30
},
"warnings": [],
"meta": {
"capability": "zhihu.trends.list",
"result_status": "complete",
"fetched_at": "2026-10-12T18:53:48.000Z",
"cached": false,
"replayed": false,
"unavailable": {},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a response recorded 2026-10-12 18:53 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.
Size as sent: 6.4 KB in the standard view (6.4 KB compact, 7.1 KB full).
{
"code": "ok",
"request_id": "b9f5ef12-74d3-424a-b753-b1d388b50f0c",
"data": { "items": [] },
"page": {
"next_cursor": null,
"cursor_expires_at": null,
"has_more": false,
"returned": 0
},
"warnings": [],
"meta": {
"capability": "zhihu.trends.list",
"result_status": "empty",
"fetched_at": "2026-10-12T18:53:48.000Z",
"cached": false,
"replayed": false,
"unavailable": {},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a recording of 2026-10-12 18:53 UTC, edited by hand to show this case. The request ID and balance are made up.
Size as sent: 400 B in the standard view (400 B compact, 400 B full).
curl "https://api.dataxapi.com/v1/zhihu/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.zhihu.trends.list() print(result["data"]["items"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.zhihu.trends.list();
console.log(result.data.items);dataxapi call zhihu.trends.list
{
"mcpServers": {
"dataxapi": {
"type": "http",
"url": "https://api.dataxapi.com/mcp",
"headers": {
"Authorization": "Bearer ${DATAXAPI_API_KEY}"
}
}
}
}Add this to your MCP client, then ask your agent to call zhihu.trends.list.
Parameters
Which list: the hot list. Values: hot (default). Example: hot.
How much of each item to return. All three cost the same. Values: compact, standard (default), full.
Return only these fields. Each by its path, such as author.name.
Known limits
- About 30 items a page, 50 at most. The page size is the platform's;
limitis not accepted. - Everything comes in one page; no cursor is issued.
- Answers come from a shared snapshot refreshed every 10 minutes;
meta.cachedsays so andmeta.fetched_atis when it was taken.
Returned fields
data.items is a list of trend objects. Stable: fields are only ever added.
The platform's ID for the entry
Name of the entry
Position on the board, from 1; a pinned entry has none
The platform's heat score
Answers the listed question has
Which numbers of this item are approximate or lower bounds; absent when all are exact
Show all 8 fields →
Path of the field, such as metrics.views
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 206 B, standard 206 B, full 228 B (measured on the response recorded 2026-10-12 18:53 UTC).
When you are charged
X-Max-Price to refuse anything above your own limit)Prices as read 2026-10-21 09:10 UTC, under price book 2, in effect since 2026-10-17 11:00 UTC; the Playground reads the price in force before a run.
Errors
What this endpoint can answer with; codes all endpoints share are on the full list.
invalid_paramsA parameter is invalidRetry: After a fixNoinsufficient_balanceThe balance is too lowRetry: After a fixNoupstream_failedThe data source failedRetry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the Zhihu hot list API cost?
$0.0020 per call. The most one call can cost is $0.0020.
When am I not charged?
Errors and timeouts are not charged; an empty result is charged $0.0020.
How many items does one call return, and how do I get the next page?
About 30 items a page, 50 at most. The page size is the platform's; limit is not accepted. Everything comes in one page; no cursor is issued.
The same thing on other platforms
All 16 Zhihu endpoints
Use it in your AI
Copy this prompt
Your API key is built in, so there is nothing to configure.
No account yet? Sign-up takes an email and no card, and a failed call is never charged.
Paste it into your agent
It reads the page the prompt points to and connects itself.
Now ask something
Use one of these, or your own words.
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call zhihu.trends.list.Other clients →Show the text
Use the DataXAPI endpoint zhihu.trends.list (Zhihu hot list). Get Zhihu's hot list: the questions on it, their rank, heat (approximate) and answer count; an entry's ID is its question's. Call GET https://api.dataxapi.com/v1/zhihu/trends/list with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - board: Which list: the hot list. Values: hot (default). Example: hot. - view: How much of each item to return. All three cost the same. Values: compact, standard (default), full. - fields: Return only these fields. Each by its path, such as author.name. Price: $0.0020 per call. Errors and timeouts are not charged; an empty result is charged $0.0020. The answer is JSON: data.items holds trend; meta.billing.amount is what this call was charged. Example: curl "https://api.dataxapi.com/v1/zhihu/trends/list" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/zhihu/trends/list.md
Names and identifiers
- In Chinese
- 知乎热榜 API
- Endpoint ID
zhihu.trends.list- Endpoint
GET /v1/zhihu/trends/list
Start with one key.
207 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.