> For the complete documentation index, see [llms.txt](https://relationlabs.gitbook.io/relation-one-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://relationlabs.gitbook.io/relation-one-api/api-zh/api/follows/follower.md).

# 粉丝列表

## <mark style="color:blue;">GET</mark> /api/v1/follower

* 说明：查询粉丝列表
* Header

| Field         | Type   | Remarks                                                            |
| ------------- | ------ | ------------------------------------------------------------------ |
| ApiKey        | String | 从管理员获取的[ApiKey](/relation-one-api/api-zh/guide/glossary.md#apikey) |
| Authorization | String | Bearer ${unifiedAuthToken} ,其中unifiedAuthToken来自/api/v1/auth接口的返回  |

* Request Parameters

| Field   | Type   | Remarks                         |
| ------- | ------ | ------------------------------- |
| address | String | relationId or address           |
| limit   | int    | 每次查询数量，上限100                    |
| cursor  | string | 上一页返回的 cursor数据，cursor为空表示查询第一页 |

* Request Example

```shell
curl  GET 'https://api.relationlabs.ai/api/v1/follower?address=5x4wh-yiaaa-aaaaj-abidq-cai&cursor=1234&limit=10' \
--header 'ApiKey: <ApiKey>' \
--header 'Authorization: Bearer eyJhbGciOiJFUzI1NiJ9.eyJqdGkiOiJiOTE5N1Y1OGJmYTY0NDRlYmU2ODA1OTc2MmViNzdlZSIsImlzcyI6InJlbGF0aW9ubGFicy5haSIsImlhdCI6MTY2MDgyNDM0MSwic3ViIjoiYmFmMzQta2lhYWEtYWFhYWstYWNnamEtY2FpIiwiZXhwIjoxNjYxNDI5MTQxfQ.Y_1NR0N3NgQCzaR1owS6Ga4AbOIfvH7ucZJJ9-HUK_FrXBtG_WjTa3XNDfmHZIwCFDOzAjSHNcRdDaR0NZGUIw'
```

* Response Parameters

| Field | Type             | Remarks |
| ----- | ---------------- | ------- |
| code  | String           | 返回码     |
| desc  | String           | 返回信息    |
| data  | FollowerResponse | 数据      |

The FollowerResponse field consists of the following subfields:

| Field  | Type            | Remarks    |
| ------ | --------------- | ---------- |
| cursor | String          | 游标         |
| list   | List\[Follower] | follower列表 |

The Follower field consists of the following subfields:

| Field      | Type   | Remarks |
| ---------- | ------ | ------- |
| relationId | String | 用户id    |
| name       | String | 用户姓名    |
| avatar     | String | 用户头像    |

* Response Body

```json
{
  "code": "0",
  "desc": "success",
  "data": {
    "cursor": "987a6dc3e3a34c759f3a3607f002d69d",
    "list": [
      {
        "relationId": "1pvde-wiaaa-aaaaj-abihq-cai",
        "name": "test_user",
        "avatar": "https://3fypb-gqaaa-aaaag-aaedq-cai.ic1.io/avatar/17b46f1160e14e1d91e32d3b59d8d6aa"
      }
    ]
  }
}
```

* Return Code

| code | desc    | Remarks |
| ---- | ------- | ------- |
| 0    | success | 接口调用成功  |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://relationlabs.gitbook.io/relation-one-api/api-zh/api/follows/follower.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.