# List your API keys

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

Organization owners/admins can list all keys in their organization, including keys whose creator has left. Other members see only keys they created. No secret or secret hash is returned.

## 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/keys" \
  -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

Key metadata visible to you.

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

The resource type. Always api_key.

Allowed values: `"api_key"`.

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

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

`string` · always present

Public credential identity used in administration routes. It is not the authentication secret.

Min length: `1`.

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

### `response.200.data.orgId`

`string` · always present

Owning Organization's Augenta ID.

Min length: `1`.

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

### `response.200.data.label`

`string` · always present

Human-readable credential name.

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

### `response.200.data.createdByUserId`

`string` · always present

Person who issued the credential.

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

### `response.200.data.createdAt`

`string` · always present

Recorded credential creation time.

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

### `response.200.data.scope`

`string` · conditional

Scope metadata, when present.

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

### `response.200.data.workspaceIds`

`array<string>` · conditional

Assigned Workspaces. An empty array permits one-shot Consolidate only.

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

### `response.200.data.workspaceId`

`string` · conditional

Legacy single-Workspace assignment, when applicable.

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

### `response.200.data.connectorId`

`string` · conditional

Legacy Connector-backed credential reference, when applicable.

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

### `response.200.data.lastActiveAt`

`string` · conditional

Last recorded authentication activity, when available.

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

### `response.200.data.revokedAt`

`string` · conditional

Recorded revocation time, when revoked.

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

### `response.200.nextPageUrl`

`string | null` · always present

## Response 400

invalid_request: invalid fields or destination.

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

unauthenticated: sign in first.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 403

forbidden: this action requires a person with the necessary role; API keys cannot administer resources.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 404

not_found: the key is unavailable.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 409

conflict: the operation could not be completed.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 429

rate_limited: retry after Retry-After.

Content-Type: `application/json`

Response fields use the same schema as Response 400.

## Response 500

internal_error: quote requestId when reporting a failure.

Content-Type: `application/json`

Response fields use the same schema as Response 400.
