Zhihu Account search API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Find Zhihu users by nickname or keyword, 20 per page, with profile ID, bio, followers, answer and article totals, upvotes received and recognition label. The profile ID works in profile, user_answers and user_pins.

Price $0.81 per 1,000 requests ($0.000806 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

Please help me write a data collection script with the EveryInfra Zhihu Account search endpoint (zhihu/user_search).

How the endpoint works:
- 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 user_search, and put the parameters inside params.
- Required parameters:
  - keyword: A nickname or keyword to find Zhihu users; each returned username works in profile, user_answers and user_pins.
- Optional parameters:
  - page_token: Page token. Leave it out for the first page, then pass back the previous response's next_page_token exactly as received. 20 users per page; each page is one call.
- Returns a list of records. Main fields of each record: user_id, username (Zhihu profile ID (user_search), the par…), display_name, url, bio, avatar_url, gender (Gender (user_search): male or female), follower_count (Followers: on hot_list, people followin…), answer_count (Answer count: on profile, the answers t…), article_count, received_upvote_count, verification_label (Recognition Zhihu shows for the account…).
- Example request body:
{
  "platform": "zhihu",
  "action": "user_search",
  "params": {
    "keyword": "python"
  }
}
- Price: $0.81 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	`user_search`	Capability identifier, fixed value.
`keyword`	body.params	`string`	Yes	-	A nickname or keyword to find Zhihu users; each returned `username` works in `profile`, `user_answers` and `user_pins`.
`page_token`	body.params	`string`	No	-	Page token. Leave it out for the first page, then pass back the previous response's `next_page_token` exactly as received. 20 users per page; each page is one call.

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": "user_search",
  "params": {
    "keyword": "python"
  }
}'

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

Response example

Field preview

No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.

json

{
  "id": "req_…",
  "platform": "zhihu",
  "action": "user_search",
  "results": [
    {
      "user_id": …,
      "username": …,
      "display_name": …,
      "url": …,
      "bio": …,
      "avatar_url": …,
      "gender": …,
      "follower_count": …,
      "answer_count": …,
      "article_count": …,
      "received_upvote_count": …,
      "verification_label": …,
      "platform": …
    }
  ],
  "next_page_token": …,
  "pagination": { … },
  "count": …,
  "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
`user_id`	User's unique ID on the platform.
`username`	Zhihu profile ID (user_search), the part after zhihu.com/people/; pass it as `url` to profile, user_answers or user_pins.
`display_name`	Display name; can differ from username.
`url`	Link to the record on the platform.
`bio`	Profile bio written by the account; may contain line breaks and emoji.
`avatar_url`	Avatar image link. Some platforms return sized CDN links that can expire.
`gender`	Gender (user_search): male or female; absent when the user does not show it.
`follower_count`	Followers: on hot_list, people following the question; on user_search, the user's followers; on column_search, people following the column.
`answer_count`	Answer count: on profile, the answers the author has written; on hot_list, the answers under the question.
`article_count`	Keeps the platform's own meaning
`received_upvote_count`	Keeps the platform's own meaning
`verification_label`	Recognition Zhihu shows for the account (user_search), such as an excellent-answerer badge or an organisation verification; absent when there is none.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

Errors and billing

401: Missing or invalid key.
402: Insufficient balance. Top up first.
422: Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
429: Per-minute request limit reached. Wait for Retry-After, then try again.
503: Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
200 empty: No data. No charge.

Errors