Zhihu Comment replies API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
List the replies under one Zhihu comment, up to 100 per call, with text, likes, reply count, time and replier. Pass the content link plus a comment_id from a comments row whose reply count is above zero.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to comment_replies. Price $0.56 per 1,000 requests ($0.000556 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 Comment replies endpoint (zhihu/comment_replies).
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 comment_replies, and put the parameters inside params.
- Required parameters:
- url: The content URL or profile URL required by content-oriented actions. content_detail and content_comments accept answer, article, or video links (question pages are not supported).
- comment_id: The comment identifier required by comment_replies, taken from a content_comments row whose reply_count is non-zero.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, text, like_count, posted_at, reply_count, author_id, author_name, author_avatar_url (Author avatar URL).
- Example request body:
{
"platform": "zhihu",
"action": "comment_replies",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118",
"comment_id": "11472966499"
}
}
- Price: $0.56 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 | comment_replies | Capability identifier, fixed value. |
url | body.params | string | Yes | - | The content URL or profile URL required by content-oriented actions. content_detail and content_comments accept answer, article, or video links (question pages are not supported); profile and user_articles accept zhihu.com/people/ profile links. |
comment_id | body.params | string | Yes | - | The comment identifier required by comment_replies, taken from a content_comments row whose reply_count is non-zero. |
limit | body.params | integer (1–100) | No | 20 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
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": "comment_replies",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118",
"comment_id": "11472966499"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "zhihu", "action": "comment_replies", "results": [ { "id": "•••", "text": "一个这种古人式模型如何认识西方和理解西方和现代化的?感觉会很有意思", "like_count": 6, "author_id": "•••", "author_name": "•••", "author_avatar_url": "https://pic1.zhimg.com/•••", "platform": "zhihu" }, { "id": "•••", "text": "非常好的想法,可以用来回答很多知乎问题。[捂嘴]", "like_count": 3, "author_id": "•••", "author_name": "•••", "author_avatar_url": "https://picx.zhimg.com/•••", "platform": "zhihu" } ], "count": 8, "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. |
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. |
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. |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
author_id | Author's unique ID on the platform. |
author_name | Author's display name. |
author_avatar_url | Author avatar URL; on comment results, the commenter's avatar. |
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.