# List organization members

## GET `/v1/orgs/{id}/members`

Read the organization roster, including provisioned people who have not signed in. Local membership is used if the identity provider cannot supply the roster.

## Authentication

Use a person's Bearer access token or console session. See [Authentication](https://augenta.pages.dev/docs/authentication.md).

## Request example

```bash
curl --fail-with-body -X GET "https://api.augenta.ai/v1/orgs/$AUGENTA_ORG_ID/members" \
  -H "Authorization: Bearer $AUGENTA_ACCESS_TOKEN"
```

## Parameters

<a id="request-parameters-id"></a>

### `request.parameters.id`

`string` · required

path parameter.

Min length: `1`.

<a id="request-parameters-limit"></a>

### `request.parameters.limit`

`integer` · optional

query parameter.

Default: `50`.

Minimum: `1`. Maximum: `200`.

<a id="request-parameters-page"></a>

### `request.parameters.page`

`string` · optional

query parameter.

Min length: `1`. Max length: `4096`.

## Response 200

One bounded resource page. Follow nextPageUrl unchanged; the authenticated page retains caller, active organization, filters and limit. Access is rechecked on every request. Administration lists use live keyset reads and may change between pages.

Content-Type: `application/json`

<a id="response-200-object"></a>

### `response.200.object`

`string` · always present

Allowed values: `"list"`.

<a id="response-200-url"></a>

### `response.200.url`

`string` · always present

<a id="response-200-data"></a>

### `response.200.data`

`array<value>` · always present

<a id="response-200-data-object"></a>

### `response.200.data.object`

`string` · always present

Allowed values: `"organization_member"`, `"workspace_member"`.

<a id="response-200-data-id"></a>

### `response.200.data.id`

`string` · always present

Min length: `1`.

<a id="response-200-data-userid"></a>

### `response.200.data.userId`

`string` · always present

Min length: `1`.

<a id="response-200-data-organization"></a>

### `response.200.data.organization`

`string` · always present

<a id="response-200-data-workspace"></a>

### `response.200.data.workspace`

`string` · conditional

<a id="response-200-data-name"></a>

### `response.200.data.name`

`string` · conditional

<a id="response-200-data-email"></a>

### `response.200.data.email`

`string` · conditional

<a id="response-200-data-role"></a>

### `response.200.data.role`

`string` · conditional

<a id="response-200-data-workspacerole"></a>

### `response.200.data.workspaceRole`

`string` · conditional

<a id="response-200-data-orgrole"></a>

### `response.200.data.orgRole`

`string` · conditional

<a id="response-200-data-via"></a>

### `response.200.data.via`

`string` · conditional

<a id="response-200-data-addedat"></a>

### `response.200.data.addedAt`

`string` · conditional

<a id="response-200-data-addedbyuserid"></a>

### `response.200.data.addedByUserId`

`string` · conditional

<a id="response-200-data-permissions"></a>

### `response.200.data.permissions`

`array<string>` · conditional

<a id="response-200-data-memberclass"></a>

### `response.200.data.memberClass`

`string` · conditional

<a id="response-200-data-hassignedin"></a>

### `response.200.data.hasSignedIn`

`boolean` · conditional

<a id="response-200-data-joinedat"></a>

### `response.200.data.joinedAt`

`string` · conditional

<a id="response-200-nextpageurl"></a>

### `response.200.nextPageUrl`

`string | null` · always present

## Response 400

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

<a id="response-400-error"></a>

### `response.400.error`

`object` · always present

<a id="response-400-error-code"></a>

### `response.400.error.code`

`string` · always present

Stable. The Errors page lists every code.

<a id="response-400-error-message"></a>

### `response.400.error.message`

`string` · always present

Human-readable. May change; don't parse it.

<a id="response-400-error-retryable"></a>

### `response.400.error.retryable`

`boolean` · always present

<a id="response-400-error-retryafterseconds"></a>

### `response.400.error.retryAfterSeconds`

`integer` · conditional

Capacity retry interval, also present as Retry-After before stream headers commit. SSE error events retain this field after HTTP 200 is committed.

Minimum: `1`.

<a id="response-400-error-billingurl"></a>

### `response.400.error.billingUrl`

`string` · conditional

Top-up action when error.code is insufficient_balance (HTTP 402).

<a id="response-400-requestid"></a>

### `response.400.requestId`

`string` · always present

The request's id, as in the `X-Request-Id` response header.

## Response 401

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 403

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 404

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 409

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 429

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 500

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 503

Invalid parameters, unavailable resource, changed revision or insufficient human permissions. API keys cannot administer organizations or Workspaces.

Content-Type: `application/json`

Response fields use the same schema as Response 400.
