1. Docs
  2. API Reference
  3. List users in Account

List users in Account

GET/api/v1/administrators

Returns a paginated page of the Account's dashboard members joined to their account_members row, exposing each member's account_role, membership-derived is_active flag, and joined_at. Supports q substring search across name and email, a status filter (active/inactive), and sorting by name, email, joined, or created. Requires administrator.view.

Authentication

Bearer TokenAuthorization Option A

JWT access token. Never send alongside X-API-Key: a request carrying both is refused.

API KeyX-API-Key Option B

API key for management-tier access. Never send alongside an Authorization header: a request carrying both is refused.

Requires permission administrator.viewAccount

View the Account's administrators. A scoped API key must hold it as a scope; a full-access key holds every scope within its Environment except the named-only and account scopes; a developer's token needs the Console capability that covers it. A credential without it is refused with 403.

Query Parameters

pagenumber Optional

Page number (1-based)

min 1

takenumber Optional

Items per page (1-100, default 20)

range 1–100

qstring Optional

Search term

max length 200

sort_byenum Optional

Sort column. Defaults to `name`, A to Z.

one of "name" · "email" · "joined" · "created"

orderenum Optional

Sort direction

one of "asc" · "desc"

statusenum Optional

Filter by Account membership status: `active`, or `inactive` for a membership that is not active

one of "active" · "inactive"

Responses

application/json

  • itemsUserResponseDto[]*
  • paginationPageMetaDto*

application/json

  • errorApiErrorBodyDto*

application/json

  • errorApiErrorBodyDto*

application/json

  • errorApiErrorBodyDto*

Errors

When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs. A request refused by an authorization check answers 403 with the code authorization.denied, and its data names the denial_reason and the permission checked.

403authorization.deniedForbidden
When it happens

The credential does not hold the permission this operation checks: a scoped API key without the scope, a developer without the Console capability that covers it, or a permission granted somewhere other than the node the request targets. The error's data names the permission.

Remediation

Add the permission named in the Authentication section to the key's scopes, or ask an account administrator to grant the covering capability, then retry. For a node-scoped operation, make sure the grant reaches the node you are acting on.

Pagination

This endpoint returns a paginated collection. Use the query parameters below to page through results.

pagenumber

Page number (1-indexed). Defaults to 1.

takenumber

Items per page (1 to 100). Defaults to 20.

Each response includes an items array alongside a pagination object with item_count, page_count, has_previous_page, and has_next_page fields.

Returned object

UserResponseDtoView all properties on this resource
Request
curl -X GET "https://auth.canopy-io.com/api/v1/administrators?page=0&take=0&q=value&sort_by=name&order=asc&status=active" \
  -H "X-API-Key: $CANOPY_API_KEY"
Response
{
  "items": [
    {
      "id": "string",
      "email": "string",
      "first_name": "string",
      "last_name": "string",
      "name": "string",
      "avatar_url": "string",
      "is_active": false,
      "account_role": "owner",
      "email_verified": false,
      "created_at": "2026-04-20T12:00:00.000Z",
      "joined_at": "2026-04-20T12:00:00.000Z"
    }
  ],
  "pagination": {
    "page": 0,
    "take": 0,
    "item_count": 0,
    "page_count": 0,
    "has_previous_page": false,
    "has_next_page": false
  }
}
 Related endpoints
GETGet a user
DELETERemove user from Account
 Was this page helpful?

Tell us how we can improve this guide.

Canopy