Zhihu Details API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Look up a Zhihu author from a zhihu.com/people/ link and get bio, followers, verification label, answer and article totals and upvotes received. Content links do not work here, and the verification label does not vouch for identity.

Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Zhihu Details endpoint (zhihu/profile).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to zhihu and action to profile, and put the parameters inside params.
- Required parameters:
- url: The content URL or profile URL required by content-oriented actions. content_detail and content_comments accept answer, article, or video links (question pages are not supported).
- Returns one object. Main fields: author_id, author_name, author_url, author_avatar_url (Author avatar URL), author_bio (Author bio as written on Zhihu), author_follower_count, author_verified (Whether the author is verified), author_verification_label (Verification description of the author,…), answer_count, article_count, received_upvote_count.
- Example request body:
{
"platform": "zhihu",
"action": "profile",
"params": {
"url": "https://www.zhihu.com/people/zhihuadmin"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`zhihu`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`profile`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	The content URL or profile URL required by content-oriented actions. content_detail and content_comments accept answer, article, or video links (question pages are not supported); profile and user_articles accept zhihu.com/people/ profile links.

Code samples

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": "profile",
  "params": {
    "url": "https://www.zhihu.com/people/zhihuadmin"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "zhihu",
  "action": "profile",
  "results": {
    "author_id": …,
    "author_name": …,
    "author_url": …,
    "author_avatar_url": …,
    "author_bio": …,
    "author_follower_count": …,
    "author_verified": …,
    "author_verification_label": …,
    "answer_count": …,
    "article_count": …,
    "received_upvote_count": …,
    "platform": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`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.
`author_avatar_url`	Author avatar URL; on comment results, the commenter's avatar.
`author_bio`	Author bio as written on Zhihu.
`author_follower_count`	Author's follower count. null means not disclosed.
`author_verified`	Whether the author is verified.
`author_verification_label`	Verification description of the author, such as a profession or institution.
`answer_count`	Keeps the platform's own meaning
`article_count`	Keeps the platform's own meaning
`received_upvote_count`	Keeps the platform's own meaning
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).