Zhihu User articles API

Q: Can I read the comments on one of these articles?

Yes. Pass the row's url to the Zhihu Content comments capability, which accepts article links, and expand busy threads with Zhihu Comment replies. comment_count on each row shows which articles are worth that second call.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Gather a Zhihu author's published pieces from their profile link, up to 100 per call, with type, title, full text, likes, comments, favorites and date. Rows share the shape of search results, and one batch may not cover the author's full archive.

Zhihu User articles lists the pieces one author has published, given the author's profile link in url. Each row carries the type, title, full text, the counts of likes, comments and favorites, when it was posted, cover image and link, plus the author's name, bio, followers and verification as they stand when you call. Researchers and PR teams use it to review an expert's body of work before citing or hiring them, follow what a competitor's spokesperson writes, or collect long-form writing on a field for analysis.

text arrives in full with HTML removed, so the list already gives you the body of each piece. Because the author fields are captured on every call, storing them with a date gives you a record of follower growth and verification changes. Sort by posted_at for a timeline, or by like_count and collect_count to see which pieces readers valued and saved.

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 User articles endpoint (zhihu/user_articles).

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 user_articles, 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).
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, type, url, title, text, like_count, comment_count, collect_count, posted_at, cover_image_url (Cover image URL), author_id, author_name; 18 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu.
- Example request body:
{
  "platform": "zhihu",
  "action": "user_articles",
  "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	`user_articles`	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.
`limit`	body.params	`integer (1–100)`	No	`20`	The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

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_articles",
  "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": "user_articles",
  "results": [
    {
      "id": …,
      "type": …,
      "url": …,
      "title": …,
      "text": …,
      "like_count": …,
      "comment_count": …,
      "collect_count": …,
      "posted_at": …,
      "cover_image_url": …,
      "platform": …,
      "author_id": …,
      "author_name": …,
      "author_url": …,
      "author_avatar_url": …,
      "author_bio": …,
      "author_follower_count": …,
      "author_verified": …,
      "author_verification_label": …
    }
  ],
  "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
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`type`	Record type; values depend on the capability (for example video / image / text).
`url`	Link to the record on the platform.
`title`	Title. null when the platform has no titles (for example text-only posts).
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`like_count`	Likes. null means the platform or this capability does not disclose it; it is not 0.
`comment_count`	Comments. null means not disclosed, not 0.
`collect_count`	Saves or favorites. null means not disclosed, not 0.
`posted_at`	Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it.
`cover_image_url`	Cover image URL.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
`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.

FAQ

Which link should I pass as `url`?

The author's profile link: https://www.zhihu.com/people/ followed by the name segment from the address bar, as in the zhihuadmin example on this page. A link to a single answer or article points at content rather than a person; it belongs with the Zhihu Content detail and Content comments capabilities instead.

Can I read the comments on one of these articles?

Yes. Pass the row's url to the Zhihu Content comments capability, which accepts article links, and expand busy threads with Zhihu Comment replies. comment_count on each row shows which articles are worth that second call.

Do the author fields replace a profile lookup?

Often they do: every row repeats the author's name, bio, number of followers, and whether and how they are verified, current as of the call. When you need the profile on its own, without any articles, call the Zhihu Details capability with the same profile link.

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).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

Zhihu: Public Articles Are Not Granted for Arbitrary Republication or Model Training ↗
Intellectual property terms in the Zhihu agreement require verifying relevant authorizations from the author and platform, while restricting unauthorized scraping, commercial use, and AI model development or training. Reading the content does not replace these permissions, nor does it indicate an endorsement by Zhihu.
Checked 2026-09-04