POST

API health

24h health
Normal
  • Healthy / normal
  • Available
Normal

Last 24 hours

Last 30 days

Page through the top-level comments on one Zhihu question itself, not on its answers, 10 per page, with text, likes, reply count, time and commenter.

Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to question_comments. 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 Question comments endpoint (zhihu/question_comments).

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 question_comments, and put the parameters inside params.
- Required parameters:
  - url: A Zhihu question link (https://www.zhihu.com/question/<question ID>), an answer link under it, or the numeric question ID. The comments returned are on the question itself, not on its answers.
- 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, with the same url.
- 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": "question_comments",
  "params": {
    "url": "https://www.zhihu.com/question/265808959"
  }
}
- 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

#
NameInTypeRequiredDefaultDescription
AuthorizationheaderstringYes-Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
platformbodystringYeszhihuPlatform identifier, fixed value.
actionbodystringYesquestion_commentsCapability identifier, fixed value.
urlbody.paramsstringYes-A Zhihu question link (https://www.zhihu.com/question/<question ID>), an answer link under it, or the numeric question ID. The comments returned are on the question itself, not on its answers.
page_tokenbody.paramsstringNo-Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received, with the same url. 10 top-level comments per page in Zhihu's default order, each page is one call, and the last page has no next_page_token.

Code samples

#
bash
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": "question_comments",
  "params": {
    "url": "https://www.zhihu.com/question/265808959"
  }
}'

OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

#
Captured November 21, 2026 at 07:25 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.
json
{  "id": "req_…",  "platform": "zhihu",  "action": "question_comments",  "results": [    {      "id": "•••",      "text": "你指望那些连入门都算不上的教程能有什么用[滑稽]",      "like_count": 1,      "posted_at": "2022-10-20T00:52:41+00:00",      "reply_count": 0,      "author_id": "•••",      "author_name": "低•••号",      "author_avatar_url": "https://picx.zhimg.com/•••",      "platform": "zhihu"    },    {      "id": "•••",      "text": "双赢的另外一方是指谁…",      "like_count": 1,      "posted_at": "2019-10-14T06:51:34+00:00",      "reply_count": 0,      "author_id": "•••",      "author_name": "知•••X",      "author_avatar_url": "https://picx.zhimg.com/•••",      "platform": "zhihu"    }  ],  "next_page_token": …,  "pagination": { … },  "count": 9,  "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.

FieldMeaning
idThe record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
textBody 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_countLikes. null means the platform or this capability does not disclose it; it is not 0.
posted_atPublish 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_countReplies, usually replies to a comment. null means not disclosed.
author_idAuthor's unique ID on the platform.
author_nameAuthor's display name.
author_avatar_urlAuthor avatar URL; on comment results, the commenter's avatar.
platformSource 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.

Errors

Google Analytics needs consent. Privacy