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

# List API Keys

> List your organization's API keys and the permissions each one holds.

### Headers

**authorization** `string` *required*

Your API key for authentication. Restricted keys cannot list keys.

### Body

**type** `string` *required*

The kind of keys to list. Use `org` for organization keys.

**target\_id** `string`

The ID of your organization. Required when `type` is `org`. You must be an owner or admin of it.

### Response

**data.keys** `array`

The organization's keys. Each entry identifies a key by its first 14 characters and never includes the full value.

**data.keys\[].key** `string`

The first 14 characters of the key. Pass this value to [Rename API Key](https://docs.bland.ai/api-v1/patch/keys-rename.md) and [Delete API Key](https://docs.bland.ai/api-v1/delete/keys-delete.md).

**data.keys\[].owner** `string`

The ID of the user who created the key, when known. A restricted key belongs to the organization and keeps working after its creator leaves.

**data.keys\[].name** `string | null`

The key's name, or `null` if it has none.

**data.keys\[].scopes** `string[] | null`

The permissions the key holds, with implied permissions included. `null` means the key has full access. See [Restricted keys](https://docs.bland.ai/api-v1/post/keys-create.md#restricted-keys).

**data.scoped\_keys\_enabled** `boolean`

Whether your organization can create restricted keys. When `false`, `POST /keys/create` with `scopes` returns `403` with the error `SCOPED_KEYS_NOT_ENABLED`.

**data.restricted\_keys\_available** `boolean`

Whether restricted key creation is currently available for your organization. This is `false` when the rollout is not enabled, your organization runs on a pinned deployment, or the availability check fails. `POST /keys/create` checks again: it returns `403` with `SCOPED_KEYS_NOT_ENABLED` when the rollout is not enabled, or `409` with `RESTRICTED_KEYS_UNAVAILABLE` when enabled but blocked by a pinned deployment. A `false` value alone does not identify the reason. See [Pinned deployments](https://docs.bland.ai/api-v1/post/keys-create.md#pinned-deployments).

**errors** `null | array`

`null` on success, or a list of errors.

```json Response theme={null}
{
  "data": {
    "keys": [
      {
        "key": "org_9f3c1a7b2d",
        "owner": "3c2f7a91-1b4e-4d6a-9e0f-5a8b7c6d5e4f",
        "name": "Production server",
        "scopes": null
      },
      {
        "key": "org_s_4b1e9c07",
        "owner": "3c2f7a91-1b4e-4d6a-9e0f-5a8b7c6d5e4f",
        "name": "Pathway CI",
        "scopes": ["agents:read", "agents:write"]
      }
    ],
    "scoped_keys_enabled": true,
    "restricted_keys_available": true
  },
  "errors": null
}
```

***

Docs for agents: [llms.txt](https://docs.bland.ai/llms.txt)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.