Zhihu Content detail API
API health
- 24h health
- Normal
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Read one Zhihu answer, article or video from its link. Get title, text, upvote, comment and favorite counts, publish time and author details. Question pages are not supported, and comments are not included.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to content_detail. 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 Content detail endpoint (zhihu/content_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 content_detail, 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).
- Returns one object. Main fields: id, type, url, title, text, like_count, comment_count, collect_count, posted_at, author_id, author_name, author_url; 17 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
"platform": "zhihu",
"action": "content_detail",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
}
}
- 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 | content_detail | 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. |
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": "content_detail",
"params": {
"url": "https://zhuanlan.zhihu.com/p/2032860336215307118"
}
}'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": "content_detail", "results": { "id": "2032860336215307118", "type": "article", "url": "https://zhuanlan.zhihu.com/p/2032860336215307118", "title": "GPT之父把AI扔回1930年:没见过一行代码,却「发明」了Python!", "text": "编辑:桃子\n【新智元导读】你敢信?一个活在95年前的AI,竟写出了Python代码。GPT之父下场,用2600亿Token炼出了一个「老古董」AI。\n一个从未见过电脑的AI,竟写出了现代编程语言!\n这可不是什么科幻的设定。\n就在今天,GPT之父Alec Radford带队发布了震撼全网的「talkie」——\n总参数130亿,一个只读过1931年之前旧文献的大模型。\ntalkie的「世界观」(全部训练数据),被冻结在了1930年12月31日。\n那个时代,没有互联网,没有维基百科,更没有任何现代代码。\n它读过的最「新」的东西,是近百年前的专利书、科学期刊、礼…", "like_count": 146, "comment_count": 64, "collect_count": 126, "posted_at": "2026-04-29T08:36:06+00:00", "platform": "zhihu", "author_id": "•••", "author_name": "•••", "author_url": "https://www.zhihu.com/•••", "author_avatar_url": "https://picx.zhimg.com/•••", "author_bio": "", "author_verified": true, "author_verification_label": "人工智能话题下的优秀答主" }, "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). |
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. |
collect_count | Saves or favorites. 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. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
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_follower_count | Author's follower count. null means not disclosed. |
author_verified | Whether the author is verified. |
author_verification_label | Verification description of the author, such as a profession or institution. |
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.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- Zhihu: Public Articles Are Not Granted for Arbitrary Republication or Model Training ↗
Intellectual property terms in the Zhihu agreement require verifying relevant authorizations from the author and platform, while restricting unauthorized scraping, commercial use, and AI model development or training. Reading the content does not replace these permissions, nor does it indicate an endorsement by Zhihu.
Checked 2026-09-04