Zhihu API coverage: search vs question answers
PostToData currently enables Zhihu keyword search and a bounded first page of answers to a question. Individual answer/article detail, comments, comment replies and user profiles are not enabled. A provider listing a Zhihu endpoint is not evidence that it returned usable data in testing.
Documentation reviewed: 2026-11-13 · By PostToData
Two enabled operations, two different inputs
Use search with query for keyword discovery. Use answers with a numeric question ID or public question URL for available answers to one question. Keep long IDs as strings so JavaScript does not round them.
Question answers are normalized into post records with available text, author, votes and individual answer links. Up to 20 answers from the first page can be returned; the endpoint does not automatically follow cursors or retrieve answer comments.
Verified availability and explicit gaps
The question-answer integration returned three answers in a production upstream test on 13 November 2026. This dated verification is not an uptime guarantee or proof of complete question coverage.
Additional upstream checks on the same date did not qualify the remaining detail, comment, reply or profile operations for production. They stay disabled instead of being shown as usable APIs. Recheck the live catalog before depending on a newly added action.
Build a bounded research task
Start with one keyword search to find relevant questions. Inspect the returned source URL, then separately approve one answers request for the chosen question. Do not derive a question ID by guessing from an answer ID.
Keep each answer URL next to the summary, distinguish quoted evidence from model interpretation, and report the sample size and collection time. A limited answer sample cannot establish the opinion distribution of all Zhihu users.
Current prices & implemented operations
| Operation | Per successful call | 1,000 successful calls |
|---|---|---|
| Zhihu · Search posts | $0.003 | $3.00 |
| Zhihu · Question answers | $0.003 | $3.00 |
The 1,000-call figure is list price multiplied by calls, not 1,000 records or a top-up package. The example only previews the first operation: no upstream fetch or charge. To retrieve data, remove dry_run=1 and supply Authorization: Bearer API_KEY. Keep max_price_usd to reject a price above the approved amount.
curl --get "https://posttodata.com/v1/zhihu/search" \
--data-urlencode 'query=咖啡' \
--data-urlencode 'limit=3' \
--data-urlencode 'max_price_usd=0.003' \
--data-urlencode 'dry_run=1'A per-call ceiling is not a shared budget for the whole task. Bound the number of approved calls and stop on 402, 412 or 429; do not automatically raise limits or rotate accounts.
Frequently asked questions
Can I fetch Zhihu article comments or nested replies?
Not through the enabled PostToData Zhihu integration today. Those operations remain unavailable; no endpoint or page claims a successful integration for them.
What happens if the upstream fails?
The request returns an error and does not debit customer credit. Stop the workflow and retain the request ID; repeated retries or multiple new accounts do not create additional free quota.