Zhihu User Follow Topics API (V1)

Retrieve Zhihu topics followed by a user, with offset pagination. Supply a user URL token. Sample fields include follower counts. Use it in a social research or monitoring workflow. The GET request schema also lists userUrlToken.

Selected price
$0.015385 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Zhihu user URL token, such as the value in `zhihu.com/people/{userUrlToken}`.
Start offset, begins with 0.

Sample response

{
  "code": 0,
  "data": {
    "data": [
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://picx.zhimg.com/89c105a38.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "852913",
          "excerpt": "运营就是对运营过程的计划、qq794283769组织、实施和控制,是与产品生产和服务创造密切相关的各项管理工作的总称。从另一个角度来讲,运营管理也可以指为对生产和提供公司主要的产品和服务的系统进行设计、运行、评价和改进的管理工作。",
          "followers_count": 390603,
          "foot_line": {
            "content": "39 万关注 · 85.2 万讨论"
          },
          "id": "19564940",
          "introduction": "运营就是对运营过程的计划、qq794283769组织、实施和控制,是与产品生产和服务创造密切相关的各项管理工作的总称。从另一个角度来讲,运营管理也可以指为对生产和提供公司主要的产品和服务的系统进行设计、运行、评价和改进的管理工作。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1023617277387632640,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://picx.zhimg.com/v2-dea0d3226b82d115e4a5cb1bf95aa937_qhd.jpg?source=57bbeac9",
          "name": "运营",
          "questions_count": 54754,
          "total_pv": "1194618944",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19564940"
        }
      },
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://pica.zhimg.com/386dc566a.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "25299132",
          "excerpt": "「职场」指的并不是狭义上的工作场所,而是以工作为载体的组织行为和人际关系的总和(包括心理关系)。",
          "followers_count": 14019358,
          "foot_line": {
            "content": "1401 万关注 · 2529 万讨论"
          },
          "id": "19557876",
          "introduction": "「职场」指的并不是狭义上的工作场所,而是以工作为载体的组织行为和人际关系的总和(包括心理关系)。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1023617958010011648,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://pic1.zhimg.com/v2-15c9885c2487fb2333d49b0005fa6ae6_qhd.jpg?source=57bbeac9",
          "name": "职场",
          "questions_count": 528616,
          "total_pv": "52351638036",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19557876"
        }
      },
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://pic1.zhimg.com/v2-40e779d5c5e6bcebda41e92d50594618.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "96175",
          "excerpt": "当存储介质出现损伤或由于人员误操作、操作系统本身故障所造成的数据看不见、无法读取、丢失。工程师通过特殊的手段读取却在正常状态下不可见、不可读、无法读的数据。数据恢复(Data recovery)是指通过技术手段,将保存在台式机硬盘、笔记本硬盘、服务器硬盘、存储磁带库、移动硬盘、U盘、数码存储卡、Mp3等等设备上丢失的电子数据进行抢救和恢复的技术。",
          "followers_count": 2585,
          "foot_line": {
            "content": "2585 关注 · 9.6 万讨论"
          },
          "id": "19578317",
          "introduction": "当存储介质出现损伤或由于人员误操作、操作系统本身故障所造成的数据看不见、无法读取、丢失。工程师通过特殊的手段读取却在正常状态下不可见、不可读、无法读的数据。数据恢复(Data recovery)是指通过技术手段,将保存在台式机硬盘、笔记本硬盘、服务器硬盘、存储磁带库、移动硬盘、U盘、数码存储卡、Mp3等等设备上丢失的电子数据进行抢救和恢复的技术。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1023603704511012864,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://pica.zhimg.com/v2-44358711d8a3c307710c8d11c377bd44_qhd.jpg?source=57bbeac9",
          "name": "数据恢复",
          "questions_count": 7845,
          "total_pv": "229049033",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19578317"
        }
      },
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://pica.zhimg.com/f07808da5625fef3607f8b75b770349f.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "26532554",
          "excerpt": "互联网(英语:Internet),又称网际网络,或音译因特网(Internet)、英特网,互联网始于1969年美国的阿帕网。是网络与网络之间所串连成的庞大网络,这些网络以一组通用的协议相连,形成逻辑上的单一巨大国际网络。通常internet泛指互联网,而Internet则特指因特网。这种将计算机网络互相联接在一起的方法可称作“网络互联”,在这基础上发展出覆盖全世界的全球性互联网络称互联网,即是互相连接一起的网络结构。互联网并不等同万…",
          "followers_count": 20870194,
          "foot_line": {
            "content": "2087 万关注 · 2653 万讨论"
          },
          "id": "19550517",
          "introduction": "互联网(英语:Internet),又称网际网络,或音译因特网(Internet)、英特网,互联网始于1969年美国的阿帕网。是网络与网络之间所串连成的庞大网络,这些网络以一组通用的协议相连,形成逻辑上的单一巨大国际网络。通常internet泛指互联网,而Internet则特指因特网。这种将计算机网络互相联接在一起的方法可称作“网络互联”,在这基础上发展出覆盖全世界的全球性互联网络称互联网,即是互相连接一起的网络结构。互联网并不等同万维网,万维网只是一建基于超文本相互链接而成的全球性系统,且是互联网所能提供的服务其中之一。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1193927277023563776,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://pic4.zhimg.com/v2-c1ea3804dc369dbfad3de0c405c0a3d2_qhd.jpg",
          "name": "互联网",
          "questions_count": 353978,
          "total_pv": "55262983245",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19550517"
        }
      },
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://pic1.zhimg.com/3f30afdfc.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "10151075",
          "excerpt": "阅读是运用语言文字来获取信息,认识世界,发展思维,并获得审美体验的活动。它是从视觉材料中获取信息的过程。视觉材料主要是文字和图片,也包括符号、公式、图表等。阅读是一种主动的过程,是由阅读者根据不同的目的加以调节控制的,陶冶人们的情操,提升自我修养。阅读是一种理解,领悟,吸收,鉴赏,评价和探究文章的思维过程。阅读可以改变命运,但并不是一定改变命运。",
          "followers_count": 26859245,
          "foot_line": {
            "content": "2685 万关注 · 1015 万讨论"
          },
          "id": "19550564",
          "introduction": "阅读是运用语言文字来获取信息,认识世界,发展思维,并获得审美体验的活动。它是从视觉材料中获取信息的过程。视觉材料主要是文字和图片,也包括符号、公式、图表等。阅读是一种主动的过程,是由阅读者根据不同的目的加以调节控制的,陶冶人们的情操,提升自我修养。阅读是一种理解,领悟,吸收,鉴赏,评价和探究文章的思维过程。阅读可以改变命运,但并不是一定改变命运。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1185974444547325952,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://pic1.zhimg.com/v2-d5723c9e63d50dbec8740de55933b96a_qhd.jpg?source=57bbeac9",
          "name": "阅读",
          "questions_count": 241752,
          "total_pv": "14232818012",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19550564"
        }
      },
      {
        "contributions_count": 0,
        "topic": {
          "avatar_url": "https://picx.zhimg.com/v2-78f4b42d0750ff5cecc0f6ec9453bc5f.jpg?source=57bbeac9",
          "category": "n_wiki",
          "discuss_count": "1090786",
          "excerpt": "数据分析是指用适当的统计分析方法对收集来的大量数据进行分析,提取有用信息和形成结论而对数据加以详细研究和概括总结的过程。这一过程也是质量管理体系的支持过程。在实用中,数据分析可帮助人们作出判断,以便采取适当行动。数据分析的数学基础在20世纪早期就已确立,但直到计算机的出现才使得实际操作成为可能,并使得数据分析得以推广。数据分析是数学与计算机科学相结合的产物。",
          "followers_count": 3647794,
          "foot_line": {
            "content": "364 万关注 · 109 万讨论"
          },
          "id": "19559424",
          "introduction": "数据分析是指用适当的统计分析方法对收集来的大量数据进行分析,提取有用信息和形成结论而对数据加以详细研究和概括总结的过程。这一过程也是质量管理体系的支持过程。在实用中,数据分析可帮助人们作出判断,以便采取适当行动。数据分析的数学基础在20世纪早期就已确立,但直到计算机的出现才使得实际操作成为可能,并使得数据分析得以推广。数据分析是数学与计算机科学相结合的产物。",
          "is_black": false,
          "is_following": true,
          "is_super_topic_vote": false,
          "is_vote": false,
          "meta": {
            "category": "n_wiki",
            "id": 1023617847288864768,
            "type": "metapedia"
          },
          "meta_avatar_url": "https://picx.zhimg.com/v2-20382e770da3bff41c52c04e821ec6cc_qhd.jpg?source=57bbeac9",
          "name": "数据分析",
          "questions_count": 43877,
          "total_pv": "3135015372",
          "type": "topic",
          "url": "https://www.zhihu.com/api/v5.1/topics/19559424"
        }
      }
    ],
    "paging": {
      "is_end": true,
      "is_start": true,
      "next": "https://www.zhihu.com/api/v5.1/topics/ming-he-43-93/following_topics_contributions?offset=20&limit=20&user_url_token=ming-he-43-93&include=data[*].topic.introduction",
      "previous": "https://www.zhihu.com/api/v5.1/topics/ming-he-43-93/following_topics_contributions?offset=-20&limit=20&user_url_token=ming-he-43-93&include=data[*].topic.introduction",
      "totals": 6
    }
  },
  "message": null,
  "recordTime": null
}

Response result

Response structure

Inferred from examples
  • codeinteger
  • dataobject
    • dataobject[]
      • contributions_countinteger
      • topicobject
        • avatar_urlstring
        • categorystring
        • discuss_countstring
        • excerptstring
        • followers_countinteger
        • foot_lineobject
          • contentstring
        • idstring
        • introductionstring
        • is_blackboolean
        • is_followingboolean
        • is_super_topic_voteboolean
        • is_voteboolean
        • metaobject
          • categorystring
          • idinteger
          • typestring
        • meta_avatar_urlstring
        • namestring
        • questions_countinteger
        • total_pvstring
        • typestring
        • urlstring
    • pagingobject
      • is_endboolean
      • is_startboolean
      • nextstring
      • previousstring
      • totalsinteger
  • messagenull
  • recordTimenull

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Zhihu User Follow Topics API (V1) with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.