raw.zhihu.answers

Zhihu question answers

LiveBeta

GEThttps://api.qovia.ai/v1/raw/zhihu/answers

Answers to one question, up to 20: text (plain text, its images listed apart), author (with followers), upvotes, comments, saves, published and edited times, as the same records as answer detail (same ids). Zhihu's default order or newest first. First page only: Zhihu's next page cannot be reached through the current source. A question without answers answers empty, one that does not exist 404 or empty; neither is charged.

Typical uses: Tracking a single post or product: reach, engagement over time and archiving.

Price: $0.001 / call$1 per 1k · fixed price
Billing: Charged only for successful, non-empty resultsthe charge is in meta.charged_usd
Scope: raw:zhihuThe API key needs this scope
Rate limit: NoneNo per-account or per-endpoint request limit

Parameters

Sent as query parameters

Only these parameters are accepted; any other one returns 400.

question_idstringRequired

Question ID (the number in zhihu.com/question/<ID>)

Pattern^[0-9]{1,20}$

Example2096149013556721446

sortstring · enum

Order: default (Zhihu's ranking, the default) or latest (newest first)

DefaultdefaultOne ofdefault · latest

countinteger

How many answers

Default20Range1–20

curl 'https://api.qovia.ai/v1/raw/zhihu/answers?question_id=2096149013556721446' \
  -H "Authorization: Bearer $QOVIA_KEY"

Replace $QOVIA_KEY with your API key

Example response200 OK

{
  "request_id": "00000000-0000-0000-0000-000000000000",
  "data": {
    "items": [
      {
        "id": "soc_zhi_0adb8742dcb5",
        "src": "social",
        "platform": "zhihu",
        "lang": "zh-CN",
        "text": "必须点个赞，对老百姓确实是个好事来的。\n简单来说，这套制度其实有点类似支付宝的亲情卡，就是你可以把某个人绑定你的亲情卡，然后设定一个限额，被绑定的这个人用支付宝支付的时候就可以直接用亲情卡支付，说白了就是可以在这个限额内花你的钱。\n只不过支付宝亲情卡的绑定门槛比较低，只要你愿意，…",
        "author": {
          "uid_hash": "86af6819638a",
          "followers": 16239,
          "nickname": "法途萤光",
          "user_id": "67ea9758246085568d7b80fd4dc7e1cd",
          "url_token": "lao-bei-jing-feng-jing"
        },
        "metrics": {
          "likes": 575,
          "comments": 118,
          "saves": 376
        },
        "extra": {
          "source_id": "2096190323630387908",
          "content_type": "answer",
          "title": "医保个人账户跨省共济落地全国，意味着什么？将带来哪些利好？",
          "question_id": "2096149013556721446",
          "published_at": "2026-10-21T10:45:18+08:00",
          "updated_at": "2026-10-21T10:45:18+08:00",
          "images": [
            "https://pic1.zhimg.com/v2-e642605f52f9daec39c479ea4b30c974_r.jpg?source=1def8aca"
          ],
          "cover_url": "https://pica.zhimg.com/80/v2-321f1f4709aab5b1d37b1f459cfdd7a8_720w.jpg?source=1def8aca",
          "url": "https://www.zhihu.com/question/2096149013556721446/answer/2096190323630387908"
        },
        "prov": {
          "hash": "0xb583077894ac21f0",
          "ts": "2026-10-21T23:45:00+08:00",
          "source": "live"
        }
      },
      {
        "id": "soc_zhi_5ef66c782c7d",
        "src": "social",
        "platform": "zhihu",
        "lang": "zh-CN",
        "text": "这是在医保跨省就医先备案再结算的基础上又一项便利的举措。\n推出医保个人账户跨省共济，对于那些个人账户躺着大笔资金，又在异地有亲人要就医治疗的人来说，终于可以使用个人账户的资金来帮助亲人看病了。意味着你职工医保个人账户里的钱，可以跨省给在老家的近亲属用了。\n知乎有一个比较热的讨论话…",
        "author": {
          "uid_hash": "edd664f97ba1",
          "followers": 104,
          "nickname": "任***生",
          "user_id": "00000000000000000000000000000001",
          "url_token": "example-user-1"
        },
        "metrics": {
          "likes": 64,
          "comments": 24,
          "saves": 22
        },
        "extra": {
          "source_id": "2096156906813387925",
          "content_type": "answer",
          "title": "医保个人账户跨省共济落地全国，意味着什么？将带来哪些利好？",
          "question_id": "2096149013556721446",
          "published_at": "2026-10-21T08:32:31+08:00",
          "updated_at": "2026-10-21T08:32:31+08:00",
          "images": [],
          "cover_url": null,
          "url": "https://www.zhihu.com/question/2096149013556721446/answer/2096156906813387925"
        },
        "prov": {
          "hash": "0x7ee96186b1cd145c",
          "ts": "2026-10-21T23:45:00+08:00",
          "source": "live"
        }
      }
    ],
    "prov": {
      "hash": "0x606c3670bc320b62",
      "ts": "2026-10-21T23:45:00+08:00",
      "source": "live"
    }
  },
  "meta": {
    "billed": true,
    "charged_usd": "0.001000",
    "balance_usd": "9.999000",
    "empty": false
  }
}

Catalog sample, not live data

Response

A success is HTTP 200 with the shared envelope: request_id, data (this endpoint's data, see the example) and meta (the charge). An empty result is also 200, with meta.empty true, not charged, and data may be an empty structure or null.

The response envelope in detail

Errors

Errors this endpoint can return
code	HTTP	Billing	Description
`scope_denied`	403	Not charged	This API key lacks the scope the endpoint requires.
`endpoint_unavailable`	503	Not charged	The endpoint is not available right now (no data source connected yet, or no price configured); nothing ran.
`invalid_params`	400	Not charged	The parameters failed validation: a required one is missing, a type or format is wrong, an array has more items than allowed, an unknown one was sent, or the POST body is not a JSON object. An error in one parameter starts with its name (`item_id: …`); a missing or unknown parameter starts with `params: …`.
`insufficient_balance`	402	Not charged	The balance cannot pay for this call; top up first.
`upstream_busy`Retryable	503	Refunded	The data source is busy or cooling down; refunded. Retry after `Retry-After`.
`upstream_timeout`	504	Refunded	The data source timed out; refunded.
`upstream_error`	502 / 503	Refunded	The data source failed; refunded.
`upstream_rejected`	400	Refunded	The data source rejected these parameters (well-formed, but not accepted); refunded.
`not_found`	404	Refunded	The data source has no such item (deleted, or the ID does not exist); refunded.
`reservation_expired`	504	Refunded	The call took too long and was refunded automatically; no data is returned.

Any request can also fail authentication: 401 invalid_api_key, 403 account_disabled, 429 too_many_auth_failures.

Every error code

Call it from your browser

Needs an account with a balance; playground calls are billed like API calls.

Try in the playground Create an API key

Parameters

Response

Errors

More Zhihu endpoints