Zhihu user_followers API

Zhihu user_followers data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

1 documented endpoints
GET /v1/zhihu/users/{username}/followers

Contract summary (English): List Zhihu followers (capability zhihu.user_followers)

Normalized response entity: zhihu/user_followers
capability: zhihu.user_followers

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

Analyze a {{platform}} account's audience: follower and following lists as normalized, paginated JSON.
Spot shared followers between accounts to map audiences and detect engagement groups.
Estimate audience quality and overlap before partnerships — no raw page exports needed.

Response fields

Zhihu zhihu.user_followers response (normalized envelope)

Response envelope of the /v1/zhihu zhihu.user_followers capability. Cursor is opaque and platform-independent; page size follows the request's `limit` parameter (1..100, default 20).

Field	Type	Required	Description
data	profile[]	Required	—
next_cursor	string \| null	Required	Opaque pagination cursor; null when the list is exhausted.
meta.request_id	string	Required	—
meta.freshness.mode	cache \| default \| live	Required	—
meta.freshness.age_seconds	integer \| null	Optional	—
meta.freshness.source_layer	cache \| db \| upstream	Required	—
meta.freshness.stale	boolean	Optional	—
meta.billing.cache_hit	boolean	Required	—
meta.billing.amount_credits	integer	Required	Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent).

Field notes are shown in the contract's original English.

Response meta

Field	Type	Required	Description
mode	cache \| default \| live	Required	Effective mode after merging param > max_age > source policy (D-004).
age_seconds	integer \| null	Optional	Age of served data; null when unknown.
source_layer	cache \| db \| upstream	Required	Which layer served the response (PRD §10).
stale	boolean	Optional	True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_credits	integer	Required	Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hit	boolean	Required	—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/zhihu/users/{username}/followers

curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/zhihu/users/newdev/followers"

{
  "data": [
    {
      "id": "9905000122",
      "platform": "zhihu",
      "type": "profile",
      "username": "meshdata-zhihu",
      "display_name": "知乎数据答主",
      "description": "知乎数据开放。",
      "profile_image_url": "https://cdn.example.com/avatar/zhihu-meshdata.jpg",
      "verified": false,
      "metrics": {
        "followers": 86500,
        "following": 35,
        "posts": 128
      },
      "fetched_at": "2026-09-21T09:00:00Z"
    }
  ],
  "next_cursor": null,
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 200,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

How are long follower lists handled?

Lists are cursor-paginated — request the next page with the returned cursor until you have what you need.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the user_followers capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.

View pricing Browse all APIs