list_community_members
Read · Sign-in needed
List your community members
The wallets in your token's community, with email, holder group, verification time and any handles they shared (X, Discord, Telegram, ENS, SNS). The token page's owner is always listed first on page one. Owner or manager; wallet session only. Contains personal contact data: show it only to the creator.
| Reads or changes | Reads only |
| Sign-in | Yes |
| Scope | api:read |
| Calls | GET /api/v2/registration/{id}/community/members (API Explorer) |
Input
JSON Schema, as the server serves it.
json
{
"additionalProperties": false,
"properties": {
"chain": {
"description": "The token page's chain: a key (`base`, `arbitrum`, `solana`), a numeric chain id or CAIP-2. Required because a token id names a different token page on every chain; the role check and the data both stay on this chain.",
"examples": [
"base"
],
"type": "string"
},
"id": {
"description": "The token page's id (the registration's numeric token id)",
"format": "int64",
"minimum": 1,
"type": "integer"
},
"limit": {
"default": 25,
"maximum": 100,
"minimum": 1,
"type": "integer"
},
"offset": {
"default": 0,
"minimum": 0,
"type": "integer"
},
"status": {
"default": "all",
"enum": [
"all",
"verified",
"unverified"
],
"type": "string"
},
"tier": {
"description": "A holder group id, or `all`",
"type": "string"
}
},
"required": [
"chain",
"id"
],
"type": "object"
}Example
A tools/call request:
json
{
"name": "list_community_members",
"arguments": {
"chain": "base",
"id": 1
}
}