# Zhihu User articles API (zhihu.user_articles)

- Canonical page: https://everyinfra.com/en/zhihu-api/user_articles
- Endpoint: POST https://api.everyinfra.com/api/v1/social with {"platform": "zhihu", "action": "user_articles", "params": {...}}
- Price: $0.000556 per call ($0.56 per 1,000 requests); failed calls and empty results are not charged
- Returns: list, default 20, max 100 per call
- Mode: sync; add "mode": "async" for slow tasks

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.

## Health

- Live health (24h percent, hourly and daily trends): https://api.everyinfra.com/api/v1/social/availability?platform=zhihu&action=user_articles

## Parameters

| name | type | required | default | description |
|---|---|---|---|---|
| url | not declared | yes | not declared | 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 | 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. |

## Response fields (items in `results`)

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

## Example

```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"
  }
}'
```

```python
import os
import requests

response = requests.post(
    "https://api.everyinfra.com/api/v1/social",
    headers={"Authorization": f"Bearer {os.environ['EVERYINFRA_API_KEY']}"},
    json={
        "platform": "zhihu",
        "action": "user_articles",
        "params": {
            "url": "https://www.zhihu.com/people/zhihuadmin",
        },
    },
    timeout=120,
)
print(response.status_code)
print(response.json())
```

## Response example

Real response to the example request above, captured 2026-10-24T18:28:34Z. `results` and `count` are real with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2 of 20. `id`, `billing` and `quota` differ on every call, so only their shape is shown.

```text
{
  "id": "req_…",
  "platform": "zhihu",
  "action": "user_articles",
  "results": [
    {
      "id": "•••",
      "url": "https://zhuanlan.zhihu.com/p/2096920883935851275",
      "title": "知乎关于持续强化“自媒体”创作者信息来源标注的公告",
      "text": "为切实维护平台健康有序、真实可靠的内容生态秩序，充分保障广大网民依法获取真实、准确、有效信息的合法权益，知乎严格落实中央网信办关于规范信息来源标注、加强内容标识提示、强化信息真实性管理相关工作部署要求，切实履行平台主体责任，持续加强站内“…",
      "like_count": 36,
      "comment_count": 5,
      "collect_count": 6,
      "posted_at": "2026-10-23T03:08:59+00:00",
      "platform": "zhihu",
      "author_id": "•••",
      "author_name": "•••",
      "author_url": "https://www.zhihu.com/people/zhihuadmin",
      "author_avatar_url": "https://picx.zhimg.com/•••",
      "author_bio": "•••",
      "author_verified": true,
      "author_verification_label": "知乎 官方账号"
    },
    {
      "id": "•••",
      "url": "https://zhuanlan.zhihu.com/p/2096918782090523453",
      "title": "关于开展「清朗·整治AI技术滥用」专项行动的社区公告",
      "text": "维护和谐、健康的网络生态，营造认真、专业、友善的社区氛围，保障用户的内容创作和讨论环境，知乎积极响应「清朗·整治AI技术滥用」专项行动要求，切实开展对各类AI技术滥用的违规行为的全面整治工作。重点整治如下： 从严打击利用AI 制作发布社会谣言、不…",
      "like_count": 4,
      "comment_count": 0,
      "collect_count": 1,
      "posted_at": "2026-10-23T03:01:54+00:00",
      "platform": "zhihu",
      "author_id": "•••",
      "author_name": "•••",
      "author_url": "https://www.zhihu.com/people/zhihuadmin",
      "author_avatar_url": "https://picx.zhimg.com/•••",
      "author_bio": "•••",
      "author_verified": true,
      "author_verification_label": "知乎 官方账号"
    }
  ],
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}
```

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

## Also

- Capability catalog (no key): https://api.everyinfra.com/api/v1/social/catalog?platform=zhihu
- OpenAPI: https://everyinfra.com/openapi.json · Agents guide: https://everyinfra.com/agents.md
