---
title: "获取社区成员（无分页）/Get community members (no pagination)"
method: GET
path: "/api/v1/twitter/web/fetch_community_members"
tags: ["Twitter-Web-API"]
---

# 获取社区成员（无分页）/Get community members (no pagination)

`GET /api/v1/twitter/web/fetch_community_members`

## Request

- Base URL: `https://api.tikhub.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.tikhub.io/api/v1/twitter/web/fetch_community_members`
- Auth: HTTP bearer

# [中文]
### 用途:
- 获取社区成员列表

### ⚠️ 本接口不支持分页（No pagination）
- 单次调用只返回第一页，约 19 条成员，无法获取更多。
- 上游虽然会在响应里给出 next_cursor，但把该 cursor 传回去只会得到空列表
  （已在多个不同规模的社区上验证，行为一致）。
- cursor 参数仅为兼容上游后续修复而保留，当前传入无任何效果，请勿依赖。
- 如需完整成员名单，本接口无法满足。

### 参数:
- community_id: 社区ID，例如：1493290339532222469
- cursor: 游标，默认为None。本接口不支持分页，传入无效
### 返回:
- 社区成员列表（仅第一页，约 19 条）

# [English]
### Purpose:
- Get community members

### ⚠️ No pagination
- A single call returns only the first page (~19 members). There is no way to fetch more.
- Upstream does return a `next_cursor` in the response, but passing that cursor back yields an
  empty list (verified across communities of different sizes — the behaviour is consistent).
- The `cursor` parameter is kept only for forward compatibility if upstream fixes this. It currently
  has no effect — do not rely on it.
- If you need a complete member list, this endpoint cannot provide it.

### Parameters:
- community_id: Community ID, for example: 1493290339532222469
- cursor: Cursor, default is None. No pagination supported; passing it has no effect
### Return:
- Community member list (first page only, ~19 members)

# [示例/Example]
community_id = "1493290339532222469"
cursor = None

## Query parameters

- `community_id` string, required: 社区ID/Community ID
- `cursor` string: 游标（本接口不支持分页，传入无效）/Cursor (no pagination, has no effect)

## Response `200`

Successful Response

- ResponseModel
  - `code` integer: HTTP status code | HTTP状态码
  - `request_id` string, nullable: Unique request identifier | 唯一请求标识符
  - `message` string: Response message (EN-US) | 响应消息 (English)
  - `message_zh` string: Response message (ZH-CN) | 响应消息 (中文)
  - `support` string: Support message | 支持消息
  - `time` string: The time the response was generated | 生成响应的时间
  - `time_stamp` integer: The timestamp the response was generated | 生成响应的时间戳
  - `time_zone` string: The timezone of the response time | 响应时间的时区
  - `docs` string, nullable: Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接
  - `cache_message` string, nullable: Cache message (EN-US) | 缓存消息 (English)
  - `cache_message_zh` string, nullable: Cache message (ZH-CN) | 缓存消息 (中文)
  - `cache_url` string, nullable: The URL to access the cached result | 访问缓存结果的 URL
  - `router` string: The endpoint that generated this response | 生成此响应的端点
  - `params` unknown
  - `data` unknown

## Other responses

- `422`: Validation Error

## Changes

- **2026-10-08** `96a122a5f220`: 2 info
  - added the optional property `detail/items/ctx` to the response with the `422` status
  - added the optional property `detail/items/input` to the response with the `422` status
- **2026-09-05** `eab99e8bfe5b`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/changes/api/v1/twitter/web/fetch_community_members/get.md)

---

[API](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi.md) - [All operations](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/llms.txt) - [OpenAPI document](https://skmtc.dev/tikhub/apis/tikhub-douyin-tiktok-xiaohongshu-lemon8-bilibili-kuaishou-pi/revisions/86a3483c705a?raw)