What is x-zse-96 on Zhihu and why do my requests fail without it?

x-zse-96 is a signature header Zhihu's web app adds to its API calls. It is computed by a function in Zhihu's JavaScript from the request URL, the x-zse-93 version header and the d_c0 cookie. Requests without a valid value are refused, and Zhihu has changed the scheme over time (2.0, then 3.0), so old signers stop working. XTikAPI reads Zhihu with 16 endpoints from $0.002 a call. A failed call is not charged, and a verified account gets $0.5 of trial balance.

Updated 2026-11-18

How developers handle it

2021 write-ups reverse the 2.0 signer as an MD5-based function in Zhihu's main bundle. By 2022 people ran Zhihu's own signing code inside a local browser (JsRPC) and called it from Python because the 3.0 version was harder to copy.

Not every failure is a signature problem: Zhihu also returns error 40362 when it is limiting access.

Without signing

zhihu.posts.search searches by keyword; zhihu.question_answers.list lists answers by question_id; zhihu.accounts.detail reads a profile by its url token. No x-zse header, cookie or browser of yours.

Why XTikAPI

  • One API key for Zhihu and every other supported platform, with the same JSON shape: data holds the result, meta says what was billed.
  • A failed call or a timeout is not charged; the response says charged: false.
  • X-Max-Price caps what one call may cost, and the same Idempotency-Key within 24 hours is never billed twice.
  • Prepaid balance, no subscription. Balance never expires, and unused top-up money can be refunded within 14 days.

Endpoints

Sources