> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relayos.com.br/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/api-keys — List API Keys

> List all active API keys for your RelayOS project. Key values are not returned — only metadata including name, ID, and creation date.

Use this endpoint to retrieve the metadata for all active API keys in your project. This is useful for auditing which keys exist and identifying keys by name before revoking them. For security, key values are never returned — only the `id`, `name`, and `createdAt` fields.

## Request

**`GET https://api.relayos.com.br/v1/api-keys`**

This endpoint takes no request body or query parameters.

```bash theme={null}
curl https://api.relayos.com.br/v1/api-keys \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Response

A `200` response returns an array of API key metadata objects.

<ResponseField name="id" type="string">
  Unique identifier for the key. Use this value with `DELETE /v1/api-keys/{id}` to revoke the key.
</ResponseField>

<ResponseField name="name" type="string">
  The descriptive label assigned when the key was created.
</ResponseField>

<ResponseField name="createdAt" type="string">
  ISO 8601 timestamp of when the key was created.
</ResponseField>

```json theme={null}
[
  {
    "id": "key_01hwxyz222bbb",
    "name": "production-backend",
    "createdAt": "2026-05-14T12:00:00Z"
  },
  {
    "id": "key_01hwxyz333ccc",
    "name": "staging-worker",
    "createdAt": "2026-05-10T09:15:00Z"
  }
]
```

<Info>
  Key values (`rly_live_...`) are never included in list responses. If you have lost a key value, create a new key and revoke the old one.
</Info>