---
title: "List a team's members"
method: GET
path: "/v1/teams/{team}/members"
tags: ["Team Members"]
---

# List a team's members

`GET /v1/teams/{team}/members`

## Request

- Base URL: `https://api.subscriby.net`
- URL: `https://api.subscriby.net/v1/teams/{team}/members`
- Auth: HTTP bearer

```bash
curl https://api.subscriby.net/v1/teams/$TEAM_ID/members \
  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"
```

The team's owner as the first row followed by every member. Not paginated: a team's collaborator list is small by construction.

`email` is **omitted entirely** unless the token carries `team-member:view`. Listing who is on a team and reading how to reach them are different asks, and the fine-grained ability is what separates them. A roster-only token gets every other field and no `email` key at all: not `null`, absent.

The same `team-member:view-any` permission gates the dashboard's **Settings → Teams → Manage Members** page: only team owners and members holding the permission via their role can load it. Free-tier teams auto-assign everyone as owner, so this only matters on Growth-tier teams with multiple collaborators.

## Path parameters

- `team` string, uuid, required

## Response `200`

Array of `TeamMemberResource`

- object
  - `data` TeamMemberResource[], required: The items.
    - `id` string, required: The collaborator's user id, the value the member routes take.
    - `team_id` string, required: The team the membership is on.
    - `name` string, required: The collaborator's name.
    - `email` string: The collaborator's email address. Present only for a token holding `team-member:view`; a roster-only token gets no `email` key at all, not null. The show route requires that ability, so it always includes it.
    - `role_id` string, nullable, required: The role the collaborator holds on this team, or null for the owner pseudo-row.
    - `is_owner` boolean, required: True only for the single team creator, who is returned alongside the members but bypasses the membership table entirely.
    - `joined_at` string, nullable, required: When the collaborator joined, ISO 8601; the team's creation for the owner.

## Other responses

- `401`: `AUTHENTICATION_REQUIRED`: the request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an `sbt_test_` token on production).
- `403`: `TOKEN_MISSING_ABILITY`: the token is valid but does not carry the ability this endpoint requires; `error.context.required_ability` names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers `FORBIDDEN`, `TEAM_TIER_REQUIRED` or `CONNECTOR_TIER_REQUIRED` with the same status, and says so in its own description.
- `404`: `RESOURCE_NOT_FOUND`: an id in the path names nothing the token can see. `TENANT_MISMATCH`: the project sits outside the token's `scope:project:` allow-list, or the token carries no team scope. Both answer 404 rather than 403 so that existence outside the token's scope cannot be inferred.
- `429`: `RATE_LIMITED`: the token has spent its 300 requests a minute or 10,000 an hour; `Retry-After` says when the next one is accepted.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)