raw.zhihu.article_search

Zhihu content search

LiveBeta

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

Keyword search over Zhihu answers and articles; answers are the same records as answer detail (same ids). Answers or articles only, sort by relevance, most upvoted or newest, filter by publish time (Zhihu applies it loosely). Pass the previous page's cursor and search_id back to continue (adjacent pages may repeat a few records: deduplicate by id); stop when has_more is false. No results answers empty and is not charged.

Typical uses: Tracking trends and topics, monitoring keywords and following competitors.

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.

keywordstringRequired

Search keyword

Max 100 charsPattern\S

Exampledeepseek

typestring · enum

Type: all (the default), answer (answers only) or article (articles only)

DefaultallOne ofall · answer · article

sortstring · enum

Order: general (relevance, the default), most_liked (most upvoted) or latest

DefaultgeneralOne ofgeneral · most_liked · latest

publish_timestring · enum

Published within: all (the default), a day, a week, a month, three months, half a year or a year

DefaultallOne ofall · day · week · month · quarter · half_year · year

cursorinteger

The cursor from the previous page's response

Default0Range0–1000

search_idstring

The search_id from the previous page's response; leave it out for the first page

Pattern^[0-9a-f]{32}$

curl 'https://api.qovia.ai/v1/raw/zhihu/article_search?keyword=deepseek' \
  -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_25f7dab19356",
        "src": "social",
        "platform": "zhihu",
        "lang": "zh-CN",
        "text": "这波开源再次把A\\和O吊起来锤！DS YES\n客观地说，对所以厂商间接的价格压力不小。对国产芯片，昇腾是最大的受益者；其他国产厂商面对的门槛被明显抬高了，国产厂商工作的兄弟们压力不小。\nDeepInfer 最早基于 vLLM 开发，现在的 vLLM 痕迹已经很少，调度器、输入准备…",
        "author": {
          "uid_hash": "a90a26b11344",
          "followers": 7645,
          "nickname": "不***猫",
          "user_id": "00000000000000000000000000000006",
          "url_token": "example-user-6"
        },
        "metrics": {
          "likes": 378,
          "comments": 21,
          "saves": 136
        },
        "extra": {
          "source_id": "2095938107812193081",
          "content_type": "answer",
          "title": "如何看待DeepSeek于10月20日开源的推理框架DeepInfer？",
          "question_id": "2095923427483951981",
          "published_at": "2026-10-20T18:03:05+08:00",
          "updated_at": "2026-10-20T18:03:05+08:00",
          "images": [],
          "cover_url": null,
          "url": "https://www.zhihu.com/question/2095923427483951981/answer/2095938107812193081"
        },
        "prov": {
          "hash": "0x33bd97c85d10ed12",
          "ts": "2026-10-21T23:45:00+08:00",
          "source": "live"
        }
      },
      {
        "id": "soc_zhi_bcd8236779c2",
        "src": "social",
        "platform": "zhihu",
        "lang": "zh-CN",
        "text": "10月17日，DeepSeek开放了自研搜索API。提供搜索、抓取两个接口，开发者几行代码调用，AI就有了一双能看全网的眼睛。\n搜索一次半分钱，5块钱1000次，请求失败不计费。\nDeepSeek出手就干大事。互联网这30年，信息入口的钱有两种赚法，他选了第三种。\n一种是百度式，…",
        "author": {
          "uid_hash": "86304c158b44",
          "followers": 2037,
          "nickname": "小***论",
          "user_id": "00000000000000000000000000000007",
          "url_token": "example-user-7"
        },
        "metrics": {
          "likes": 13,
          "comments": 1,
          "saves": 10
        },
        "extra": {
          "source_id": "2095207817133216122",
          "content_type": "article",
          "title": "实测DeepSeek搜索，半分钱撞了百度的命根子",
          "question_id": null,
          "published_at": "2026-10-18T17:41:10+08:00",
          "updated_at": "2026-10-18T17:41:10+08:00",
          "images": [
            "https://pic1.zhimg.com/v2-e502668fbe60b2d00cee40968825f82c_r.jpg"
          ],
          "cover_url": "https://picx.zhimg.com/80/v2-e502668fbe60b2d00cee40968825f82c_qhd.jpg?source=4e949a73",
          "url": "https://zhuanlan.zhihu.com/p/2095207817133216122"
        },
        "prov": {
          "hash": "0xb854e0bc66c21058",
          "ts": "2026-10-21T23:45:00+08:00",
          "source": "live"
        }
      }
    ],
    "cursor": 20,
    "has_more": true,
    "search_id": "600fd1f58c9c6284ffaac78be50e4d04",
    "prov": {
      "hash": "0x69388e0514229e45",
      "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