---
title: "List organization members"
method: GET
path: "/organizations/{org_id}/members"
tags: ["Organizations"]
---

# List organization members

`GET /organizations/{org_id}/members`

Retrieves a paginated list of members for the specified organization.

## Query parameters

- `sort_by` 'email' | 'role' | 'joined_at'
- `cursor` string
- `sort_order` 'asc' | 'desc'
- `limit` integer

## Response `200`

Returned information about organization members

- object
  - `members` MemberWithUser[], required
    - `member` Member, required
      - `id` string, uuid, required
      - `user_id` string, uuid, required
      - `org_id` string, required
      - `role` 'admin' | 'member' | 'editor' | 'viewer' | 'collaborator', required — The role of the organization member. Some role values may not be available for all organizations.
      - `joined_at` string, date-time
    - `user` MemberUserInfo, required
      - `email` string, email, required
      - `has_mfa` boolean — Whether the member has MFA (TOTP) enabled
      - `deactivated_at` string, date-time — Timestamp of when the user account was deactivated. Absent for active users. When present, the UI should render a "Deactivated" badge inline next to the member.
  - `pagination` CursorPagination — To paginate the response, issue an initial request with `limit` value. Then, add the value returned in the response `.pagination.next` attribute into the request under the `cursor` query parameter to the subsequent request to retrieve next page in pagination. The contents on cursor `next` are opaque, clients are not expected to make any assumptions on the format of the data inside the cursor.
    - `next` string
    - `sort_by` string
    - `sort_order` string

## Other responses

- `default` — General Error. The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received. - If no response is returned from the API, a network error or timeout likely occurred. - In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results. The following HTTP methods are considered non-idempotent: `POST`, `PATCH`, `DELETE`, and `PUT`. Retrying these methods is generally **not safe**. The following methods are considered idempotent: `GET`, `HEAD`, and `OPTIONS`. Retrying these methods is **safe** in the event of a network error or timeout. Any request that returns a `503 Service Unavailable` response is always safe to retry. Any request that returns a `423 Locked` response is safe to retry. `423 Locked` indicates that the resource is temporarily locked, for example, due to another operation in progress.

---

[API](https://skmtc.net/neon/apis/neon-api.md) · [All operations](https://skmtc.net/neon/apis/neon-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/neon/neon-api/revisions/cfde79a5c713/schema)