Zhihu Question details API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Read one Zhihu question from its link or ID, with title, description, topics, answer, follower, view, comment and upvote counts, dates and the asker.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to question_detail. Price $0.79 per 1,000 requests ($0.000792 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 details endpoint (zhihu/question_detail).
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_detail, 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. An unrecognized link returns 422, and a question that does not exist returns 503.
- Returns one object. Main fields: id, type, url, title, text, topics, answer_count (Answer count: on profile, the answers t…), follower_count (Followers: on hot_list, people followin…), visit_count (Views of the topic (topic_search)), comment_count, like_count, posted_at; 16 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
"platform": "zhihu",
"action": "question_detail",
"params": {
"url": "https://www.zhihu.com/question/265808959"
}
}
- Price: $0.79 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 | question_detail | Capability identifier, fixed value. |
url | body.params | string | Yes | - | A Zhihu question link (https://www.zhihu.com/question/<question ID>), an answer link under it, or the numeric question ID. An unrecognized link returns 422, and a question that does not exist returns 503; neither is charged. |
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": "question_detail",
"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
#{ "id": "req_…", "platform": "zhihu", "action": "question_detail", "results": { "id": "265808959", "type": "question", "url": "https://www.zhihu.com/question/265808959", "title": "为什么网上Python爬虫教程这么多,但是做爬虫的这么少呢?爬虫发展又该是如何呢?", "text": "很多人学习Python进阶可能都写过几个爬虫,但是最终做爬虫的人却比较少呢?是因为真的像别人说的那样,爬虫真的没“技术含量”,还是爬虫随着反爬的不断提升,做爬虫的代价越来越高难以维持成本?还希望能谈一谈爬虫的发展该是怎样的?可能做到双赢吗?请指教", "topics": [ "Python", "爬虫 (计算机网络)", "Python 入门" ], "answer_count": 291, "follower_count": 2895, "visit_count": 1995333, "comment_count": 10, "like_count": 151, "posted_at": "2018-01-18T15:44:12+00:00", "updated_at": "2018-01-19T02:34:45+00:00", "author_id": "•••", "author_name": "苏•••", "author_url": "https://www.zhihu.com/•••", "platform": "zhihu" }, "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. |
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). |
topics | Keeps the platform's own meaning |
answer_count | Answer count: on profile, the answers the author has written; on hot_list, the answers under the question. |
follower_count | Followers: on hot_list, people following the question; on user_search, the user's followers; on column_search, people following the column; on topic_search, people following the topic. |
visit_count | Views of the topic (topic_search). |
comment_count | Comments. null means not disclosed, not 0. |
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. |
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. |
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.