# Zhihu Question details API (zhihu.question_detail)

- Canonical page: [https://everyinfra.com/en/zhihu-api/question_detail](https://everyinfra.com/en/zhihu-api/question_detail?utm_medium=ai_doc&utm_campaign=page_md)
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "zhihu", "action": "question_detail", "params": {...}}
- Price: $0.000792 per call ($0.79 per 1,000 requests); failed calls and empty results are not charged
- Returns: single object
- Mode: sync; add "mode": "async" for slow tasks

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=zhihu&action=question_detail

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | 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. |

## Response fields (items in `results`)

| 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 | platform-native 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). |

## Example

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

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "zhihu",
        "action": "question_detail",
        "params": {
            "url": "https://www.zhihu.com/question/265808959",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-11-21T07:25:12Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "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": { … }
}
```

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
