ZhihuSocial mediaComing soon
Zhihu user answers API
The answers a person wrote, by their handle, 20 a page, newest first: the question (as title), the text, upvotes, comments and time posted.
GEThttps://api.okdata.online/v1/zhihu/users/answers/list
Also calledanswers by a zhihu userzhihu answer history
- Price
- $0.002
- per call · failed calls are free
- Returns
- About 20 posts a page
- with a cursor for the next page
- If a call fails
- Not charged
- When a data source fails, the next one is tried; errors and timeouts cost nothing.
- Status
- coming soon
- Listed but not callable yet: a call answers capability_paused and is not charged.
Parameters
| Name | Type | Description |
|---|---|---|
usernamerequired | string | The handle in the profile's link (url_token): what follows zhihu.com/people/. |
cursor | string | Opaque cursor from page.next_cursor of the previous call. Each page is a separate call. |
view | stringcompactstandardfull | How much of each object comes back. full adds platform-specific fields under ext. |
fields | string[] | Fields to keep, by path (author.name), to save tokens. In a query string: comma-separated. |
cursor, view and fields work the same on every endpoint: how requests work.
Request
cURL
curl -G "https://api.okdata.online/v1/zhihu/users/answers/list" \
-H "Authorization: Bearer $OKDATA_API_KEY" \
--data-urlencode 'username=zhihuadmin'Python
import os
import requests
resp = requests.get(
"https://api.okdata.online/v1/zhihu/users/answers/list",
headers={"Authorization": f"Bearer {os.environ['OKDATA_API_KEY']}"},
params={"username": "zhihuadmin"},
timeout=60,
)
body = resp.json()
if body["code"] != "ok":
raise RuntimeError(f"{body['code']}: {body['message']} (charged: {body['charged']})")
for row in body["data"]["items"]:
print(row["id"], row["metrics"]["likes"], row["text"][:60])
print("cost: $" + body["meta"]["billing"]["amount"])TypeScript
const url = new URL('https://api.okdata.online/v1/zhihu/users/answers/list');
url.searchParams.set('username', "zhihuadmin");
const res = await fetch(url, {
headers: {
Authorization: `Bearer ${process.env.OKDATA_API_KEY}`,
},
});
const body = await res.json();
if (body.code !== 'ok') throw new Error(`${body.code}: ${body.message}`);
for (const row of body.data.items) {
console.log(row.id, row.metrics.likes, row.text.slice(0, 60));
}
console.log('cost: $' + body.meta.billing.amount);MCPtools/call
{
"name": "call",
"arguments": {
"capability": "zhihu.users.answers.list",
"username": "zhihuadmin"
}
}Response
{
"code": "ok",
"request_id": "0f6c2a8e-4b1d-4e0a-9a51-3c7d2b9e1f20",
"data": {
"items": [
{
"id": "3283784039",
"url": "https://www.zhihu.com/question/568657112/answer/3283784039",
"type": "text",
"title": "预算 3000 元左右,有哪些不错的露营装备推荐?",
"text": "先说结论:帐篷和睡袋别省,其他都可以慢慢换。",
"lang": "zh",
"published_at": "2026-11-02T09:30:00Z",
"author": {
"id": "b32409944256dfd62a963434fcda6aa9",
"username": "qingzhuang-tubu",
"name": "轻装徒步",
"avatar_url": "https://cdn.example.com/avatar/trailkit.jpg",
"followers": 15700,
"verified": true
},
"metrics": {
"views": null,
"likes": 48200,
"comments": 1312,
"shares": null,
"favorites": 9650,
"reposts": null
},
"images": null,
"hashtags": null
}
]
},
"page": {
"next_cursor": "eyJvIjoyMH0",
"has_more": true
},
"warnings": [],
"meta": {
"capability": "zhihu.users.answers.list",
"billing": {
"amount": "0.002",
"currency": "USD",
"balance_after": "9.998"
},
"unavailable": {
"metrics.views": "platform",
"metrics.shares": "platform",
"metrics.reposts": "platform"
},
"cached": false,
"replayed": false,
"fetched_at": "2026-11-11T08:00:00Z"
}
}Coming soon
This endpoint is listed but not callable yet: a call answers capability_paused and is not charged. The parameters, fields and price on this page are the contract it will open with; the status page and the changelog say when it does.
Known limits
- About 20 posts come back per page; the platform sets the page size, so there is no page-size parameter.
- For the next page, pass
page.next_cursorback ascursor. A cursor stays valid for 24 hours. Whenpage.has_moreis false there is nothing left. - 3 fields of Post this endpoint cannot give
Returned fields
data.items is a list of Post.
| Field | Type | View | Description |
|---|---|---|---|
id | string | compact | Post ID on the platform. |
url | string | compact | Link to the post. |
type | string | compact | What kind of post it is. |
title | string | null | compact | Title, where the platform has one (videos, notes, articles). |
text | string | compact | Caption, body or description as plain text; articles come as Markdown.Long text: view=compact may shorten it. |
lang | string | null | standard | Language code, as reported or detected. |
Show all 12 fieldsHide the other 6
| Field | Type | View | Description |
|---|---|---|---|
published_at | string | null | compact | When it was published, ISO 8601 in UTC; null only where the source gives no time (wechat_mp.articles.metrics, wechat_channels.videos.metrics, youtube.channels.videos.list with type=short), then listed in meta.unavailable. |
author | AccountRef | compact | Who posted it. |
metrics | Metrics | compact | Counts at fetch time; a count the platform hides is null. |
images | string[] | null | standard | Image URLs for image posts and notes. |
hashtags | string[] | null | standard | Hashtags or topics, without the # sign. |
ext | object | full | Platform-specific extras. Only returned with view=full. |
The view column is the smallest view a field comes back in: compact returns only compact fields, standard adds the standard ones, full returns everything. The default is standard.
What this endpoint cannot give
These fields of Post come back as null here, and meta.unavailable names each one with its reason.
metrics.viewsthe platform does not show itmetrics.sharesthe platform does not show itmetrics.repoststhe platform does not show it
When it is charged
One call costs $0.002 and returns one page of about 20 posts. Collecting 1,000 posts takes about 50 calls, $0.10 in total. Each page is a separate call; failed calls are not charged.
Data comes back$0.002 per call
Bad parameters, errors, timeoutsFree
| When | Charge |
|---|---|
| Each further page | A new call: $0.002 |
| Most one call costs | $0.002 |
| An empty answer | $0.002 |
| Not found (the platform has no such item) | Free |
| Bad parameters, errors, timeouts | Free |
| A retry with the same Idempotency-Key within 24 hours | Charged once |
A failed call is free; an empty answer costs $0.002; not found is free.
Prices from price book 1b273c48fea9634e. Every price on this platform →
Common errors
Every error has the same shape and says whether it was charged. The ones this endpoint can return:
| HTTP | Code | Meaning | Charged |
|---|---|---|---|
| 400 | invalid_params | A parameter is missing, has the wrong type or value, or the method is wrong. problems lists each one; param names the first.Retry: after a fix | no |
| 400 | cursor_mismatch | The cursor was sent to another endpoint, or with other parameters than the page it came from (view and fields may change).Retry: after a fix | no |
| 401 | unauthorized | The key is missing, malformed, revoked, disabled or expired (reason says which when known).Retry: no | no |
| 402 | insufficient_balance | The balance (available) cannot cover the most this call could cost (required).Retry: after a fix | no |
| 404 | not_found | The post, account or page does not exist or is not public. Endpoints whose charge_when_not_found is above 0 charge this answer (the source billed us for it): the body then says charged: true and amount.Retry: no | no |
| 410 | cursor_expired | The cursor is older than the endpoint's cursor lifetime (page.cursor_expires_at said when).Retry: no | no |
| 429 | rate_limited | The account sent too many requests this minute (reason: rate) or has too many calls running (reason: concurrency).Retry: yes | no |
| 500 | settlement_unknown | The data came back, but the charge could not be confirmed.Retry: with the same Idempotency-Key | unknown until looked up |
| 502 | upstream_failed | Every data source for this endpoint failed on this request.Retry: yes | no |
| 503 | capability_paused | This endpoint is paused right now; nothing ran.Retry: yes | no |
| 504 | timeout | The data did not come back in time. The hold was released, so nothing was charged.Retry: yes | no |
Questions
Can I call the Zhihu user answers API now?
This endpoint is listed but not callable yet: a call answers capability_paused and is not charged. The parameters, fields and price on this page are the contract it will open with; the status page and the changelog say when it does.
How much does the Zhihu user answers API cost?
One call costs $0.002 and returns one page of about 20 posts. Collecting 1,000 posts takes about 50 calls, $0.10 in total. Each page is a separate call; failed calls are not charged.
How do I get the next page?
Pass page.next_cursor from the response back as the cursor parameter. When page.has_more is false there is nothing left. Every page is its own call at $0.002.
Do I need a Zhihu account, cookies or a QR login?
No. You send only your okdata API key. The data is public data from Zhihu; nothing is fetched with your own Zhihu account.
Am I charged when a call fails?
No. Every error response says charged: false, except a timeout, which says charged: null until the outcome is known. Resend with the same Idempotency-Key and you are never charged twice.
What if Zhihu does not show a field?
The field is null, and meta.unavailable names it with the reason: platform (the platform never shows it) or capability (we cannot fetch it yet).
All 15 Zhihu endpoints
Main Zhihu endpoints
- Zhihu search$0.002/call
- Zhihu question answers$0.002/call
- Zhihu question detailcoming soon$0.002/call
- Zhihu answer detailcoming soon$0.002/call
- Zhihu answer commentscoming soon$0.002/call
- Zhihu comment repliescoming soon$0.002/call
- Zhihu article detailcoming soon$0.002/call
- Zhihu column articlescoming soon$0.002/call
- Zhihu pin detailcoming soon$0.002/call
- Zhihu user profilecoming soon$0.002/call
- Zhihu user searchcoming soon$0.002/call
- Zhihu user followerscoming soon$0.002/call
- Zhihu user articlescoming soon$0.002/call
- Zhihu user pinscoming soon$0.002/call
Names and ID
- Name
- Zhihu user answers API
- Short name
- Zhihu user answers
- ID
zhihu.users.answers.list- Endpoint
GET /v1/zhihu/users/answers/list- Category
- Social media
- Also called
- answers by a zhihu user, zhihu answer history
- Returns
- Post[]: 12 fields