Zhihu content search API
Get a page of Zhihu answers and articles matching a search; either kind alone, by relevance, newest or most upvoted. About 18 items a call, 20 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/search/content? It is this address now. What changed for old endpoints
curl -G "https://api.dataxapi.com/v1/zhihu/posts/search" \ --data-urlencode "query=咖啡机推荐" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "87ee6f95-7dde-47c6-8b04-4ec1594169d0",
"data": {
"items": [
{
"id": "3250756632",
"url": "https://www.zhihu.com/answer/3250756632",
"type": "article",
"title": "咖啡机推荐入门指南:一篇讲清楚",
"text": "咖啡机推荐这件事,越简单越好",
"published_at": "2026-03-03T08:11:12.000Z",
"author": {
"id": "cbf102a15e966bc955fc8f2b452b62fa",
"username": "laozhou_gear",
"name": "老周说装备",
"avatar_url": "https://picx.zhimg.com/v2-671ebb705befb9d2492d_l.jpg",
"followers": 10699
},
"metrics": { "likes": 224, "comments": 3, "favorites": 0 },
"post_id": null,
"parent_id": null
},
// … 16 more
]
},
"page": {
"next_cursor": "c1.Km3J8vP9d1xw85c8i-GQVxvJL7XKz0me6b3X34wR",
"cursor_expires_at": "2026-10-12T20:18:45.000Z",
"has_more": true,
"returned": 17
},
"warnings": [],
"meta": {
"capability": "zhihu.posts.search",
"result_status": "complete",
"fetched_at": "2026-10-12T19:18:45.000Z",
"cached": false,
"replayed": false,
"unavailable": {
"lang": "capability",
"author.verified": "capability",
"metrics.shares": "platform",
"metrics.views": "capability",
"metrics.reposts": "platform",
"images": "capability",
"hashtags": "platform",
"mentions": "capability",
"is_pinned": "capability",
"root_id": "platform"
},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a response recorded 2026-10-12 19:18 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: 180.6 KB in the standard view (31.9 KB compact, 180.6 KB full).
{
"code": "ok",
"request_id": "15382efd-b6f4-4024-a3f9-7df9b0c9661e",
"data": { "items": [] },
"page": {
"next_cursor": null,
"cursor_expires_at": null,
"has_more": false,
"returned": 0
},
"warnings": [],
"meta": {
"capability": "zhihu.posts.search",
"result_status": "empty",
"fetched_at": "2026-10-12T19:18:45.000Z",
"cached": false,
"replayed": false,
"unavailable": {
"lang": "capability",
"author.verified": "capability",
"metrics.shares": "platform",
"metrics.views": "capability",
"metrics.reposts": "platform",
"images": "capability",
"hashtags": "platform",
"mentions": "capability",
"is_pinned": "capability",
"root_id": "platform"
},
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
}
}
}From a recording of 2026-10-12 19:18 UTC, edited by hand to show this case. The request ID and balance are made up.
Size as sent: 651 B in the standard view (651 B compact, 651 B full).
curl -G "https://api.dataxapi.com/v1/zhihu/posts/search" \ --data-urlencode "query=咖啡机推荐" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.zhihu.posts.search(query="咖啡机推荐") print(result["data"]["items"])
import { DataXAPI } from "@dataxapi/sdk";
const dx = new DataXAPI(); // reads DATAXAPI_API_KEY
const result = await dx.zhihu.posts.search({ query: "咖啡机推荐" });
console.log(result.data.items);dataxapi call zhihu.posts.search 'query=咖啡机推荐'{
"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.posts.search.
Parameters
Search terms. Example: 咖啡机推荐.
Answers only, or articles only; both when left out. Values: answer, article. Example: answer.
By relevance, newest first, or most upvoted first. Values: relevance (default), latest, popular. Example: relevance.
Cursor returned by the previous page. Pass page.next_cursor of the page before, unchanged. Each page is charged as a call of its own.
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 18 items a page, 20 at most. The page size is the platform's;
limitis not accepted. - For the next page pass
page.next_cursorascursor; a cursor is valid for 1 hour.page.has_moreis false on the last page. - 13 fields of the object are not available from this endpoint
Returned fields
data.items is a list of post objects. Stable: fields are only ever added.
ID; pass it unchanged to the get endpoint
Link that opens the post
Content formatvideoimagetextarticle
Title
Body text
Long text: the compact view keeps the first 500 characters and says so in warnings.
Language of the text
Show all 34 fields →
When it was published
Author
Author's account ID
Author's handle
Author's display name
Author's avatar
Whether the author is verified
Author's follower count
Engagement counts
Likes
On this platform: Upvotes
Comments
Shares
Saves
Views
Reposts
Image addresses
Hashtags, without the #
Accounts mentioned in the text
Account ID
Handle
Display name
Whether the author pinned it
ID of the thread's root post when this is a reply; otherwise null
ID of the item it replies to directly; otherwise null
ID of the first-level reply its thread hangs under
Which numbers of this item are approximate or lower bounds; absent when all are exact
Path of the field, such as metrics.views
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 1.8 KB, standard 10.6 KB, full 10.6 KB (measured on the response recorded 2026-10-12 19:18 UTC).
What this endpoint cannot give
langNot provided hereauthor.verifiedNot provided heremetrics.sharesThe platform has nonemetrics.viewsNot provided heremetrics.repostsThe platform has noneimagesNot provided herehashtagsThe platform has nonementionsNot provided herementions[].idNot provided herementions[].usernameNot provided herementions[].nameNot provided hereis_pinnedNot provided hereroot_idThe platform has noneWhen 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 fixNocursor_mismatchThe cursor was issued for another endpoint or other parametersRetry: After a fixNoinsufficient_balanceThe balance is too lowRetry: After a fixNocursor_expiredThe cursor expired; start again from the first pageRetry: NoNoupstream_failedThe data source failedRetry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the Zhihu content search 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 18 items a page, 20 at most. The page size is the platform's; limit is not accepted. For the next page pass page.next_cursor as cursor; a cursor is valid for 1 hour. page.has_more is false on the last page.
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.posts.search.Other clients →Show the text
Use the DataXAPI endpoint zhihu.posts.search (Zhihu content search). Get a page of Zhihu answers and articles matching a search; either kind alone, by relevance, newest or most upvoted. Call GET https://api.dataxapi.com/v1/zhihu/posts/search with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - query (required): Search terms. Example: 咖啡机推荐. - type: Answers only, or articles only; both when left out. Values: answer, article. Example: answer. - sort: By relevance, newest first, or most upvoted first. Values: relevance (default), latest, popular. Example: relevance. - cursor: Cursor returned by the previous page. Pass page.next_cursor of the page before, unchanged. Each page is charged as a call of its own. - 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 post; meta.billing.amount is what this call was charged. Example: curl -G "https://api.dataxapi.com/v1/zhihu/posts/search" \ --data-urlencode "query=咖啡机推荐" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/zhihu/posts/search.md
Names and identifiers
- In Chinese
- 知乎内容搜索 API
- Endpoint ID
zhihu.posts.search- Endpoint
GET /v1/zhihu/posts/search
Start with one key.
207 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.