Zhihu Pin details API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Read one Zhihu pin from its link or ID, with text, likes, comments, reposts, saves, date and author, plus images or a video's cover and length when the pin has them.
Send POST https://api.everyinfra.com/api/v1/social with platform set to zhihu and action set to pin_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 Pin details endpoint (zhihu/pin_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 pin_detail, and put the parameters inside params.
- Required parameters:
- url: A Zhihu pin link (https://www.zhihu.com/pin/<pin ID>) or the numeric pin ID (the id of a user_pins row). An unrecognized link returns 422 and is not charged.
- Returns one object. Main fields: id, type, url, text, image_urls (Images in the pin (user_pins)), cover_image_url (Cover image URL), duration_seconds, duration_sec, like_count, comment_count, repost_count (Times the pin was reposted (user_pins)), collect_count; 20 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
"platform": "zhihu",
"action": "pin_detail",
"params": {
"url": "https://www.zhihu.com/pin/2065248867814209080"
}
}
- 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 | pin_detail | Capability identifier, fixed value. |
url | body.params | string | Yes | - | A Zhihu pin link (https://www.zhihu.com/pin/<pin ID>) or the numeric pin ID (the id of a user_pins row). An unrecognized link returns 422 and is not 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": "pin_detail",
"params": {
"url": "https://www.zhihu.com/pin/2065248867814209080"
}
}'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": "pin_detail", "results": { "id": "2065248867814209080", "type": "pin", "url": "https://www.zhihu.com/pin/2065248867814209080", "text": "东野寿终68岁——鸟山明也68岁,当然鸟山明的逝去原因不太一样。其他,谷口治郎(《孤独的美食家》)69岁。荻野真(《孔雀王》)59岁。手冢治虫60岁。安部公房68岁。\n2025年日本男性平均预期寿命81.4岁。\n这些大师们的医疗条件,按说不会比日本普通人差。\n\n当然咯,癌症是遗传、年龄、环境和生活方式共同作用。东野自己也说过肠道病变要规律筛查。死因不同,但长期高强度工作都是共同风险因素之一。\n\n东野出名的高产。一年四五本书是常态。累计出书超过百种。\n鸟山明自己说过,连载《阿拉蕾》和《龙珠》时没有正常生活。\n做他们这行,每天十几小时工作。熬夜(手冢治虫)。…", "like_count": 242, "comment_count": 31, "repost_count": 0, "collect_count": 67, "posted_at": "2026-07-27T17:35:21+00:00", "updated_at": "2026-07-27T17:35:21+00:00", "author_id": "•••", "author_name": "张•••玮", "author_url": "https://www.zhihu.com/•••", "author_avatar_url": "https://picx.zhimg.com/•••", "author_follower_count": 3462354, "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. |
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). |
image_urls | Images in the pin (user_pins); absent for text-only pins. |
cover_image_url | Cover image URL. |
duration_seconds | Duration in seconds. null for content that is not video or audio. |
duration_sec | Keeps the platform's own meaning |
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. |
repost_count | Times the pin was reposted (user_pins). |
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. |
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_follower_count | Author's follower count. null means not disclosed. |
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.