Zhihu User answers API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Page through the answers a Zhihu user wrote, newest first, 20 per page, from a profile link or profile ID. Each answer has the question it answers, full text, upvotes, comments, publish and edit times. Find the profile ID with user_search.
Price $0.81 per 1,000 requests ($0.000806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Please help me write a data collection script with the EveryInfra Zhihu User answers endpoint (zhihu/user_answers).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to zhihu and action to user_answers, and put the parameters inside params.
- Required parameters:
- url: A Zhihu profile link (https://www.zhihu.com/people/<profile ID>) or the profile ID alone. Nicknames are not accepted; find the profile ID with user_search first.
- Optional parameters:
- page_token: Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received. 20 answers per page, newest first; each page is one call.
- Returns a list of records. Main fields of each record: id, type, url, question_id (ID of the question the answer belongs t…), title, text, like_count, comment_count, posted_at, updated_at (When the answer was last edited (questi…), author_id, author_name; 16 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
"platform": "zhihu",
"action": "user_answers",
"params": {
"url": "https://www.zhihu.com/people/zhihuadmin"
}
}
- Price: $0.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | zhihu | Platform identifier, fixed value. |
action | body | string | Yes | user_answers | Capability identifier, fixed value. |
url | body.params | string | Yes | - | A Zhihu profile link (https://www.zhihu.com/people/<profile ID>) or the profile ID alone. Nicknames are not accepted; find the profile ID with user_search first. |
page_token | body.params | string | No | - | Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received. 20 answers per page, newest first; each page is one call. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "zhihu",
"action": "user_answers",
"params": {
"url": "https://www.zhihu.com/people/zhihuadmin"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
{
"id": "req_…",
"platform": "zhihu",
"action": "user_answers",
"results": [
{
"id": …,
"type": …,
"url": …,
"question_id": …,
"title": …,
"text": …,
"like_count": …,
"comment_count": …,
"posted_at": …,
"updated_at": …,
"author_id": …,
"author_name": …,
"author_url": …,
"author_avatar_url": …,
"author_bio": …,
"author_verification_label": …,
"platform": …
}
],
"next_page_token": …,
"pagination": { … },
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
type | Record type; values depend on the capability (for example video / image / text). |
url | Link to the record on the platform. |
question_id | ID of the question the answer belongs to (question_answers), the same as the requested question. |
title | Title. null when the platform has no titles (for example text-only posts). |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
comment_count | Comments. null means not disclosed, not 0. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
updated_at | When the answer was last edited (question_answers), ISO 8601 in UTC; the same as posted_at when never edited. |
author_id | Author's unique ID on the platform. |
author_name | Author's display name. |
author_url | Link to the author's profile on the platform. |
author_avatar_url | Author avatar URL; on comment results, the commenter's avatar. |
author_bio | Author bio as written on Zhihu. |
author_verification_label | Verification description of the author, such as a profession or institution. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.