Skip to main content
POST
List API Keys

Headers

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

Body

string
required
The kind of keys to list. Use org for organization keys.
string
The ID of your organization. Required when type is org. You must be an owner or admin of it.

Response

array
The organization’s keys. Each entry identifies a key by its first 14 characters and never includes the full value.
string
The first 14 characters of the key. Pass this value to Rename API Key and Delete API Key.
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.
string | null
The key’s name, or null if it has none.
string[] | null
The permissions the key holds, with implied permissions included. null means the key has full access. See Restricted keys.
boolean
Whether your organization can create restricted keys. When false, POST /keys/create with scopes returns 403 with the error SCOPED_KEYS_NOT_ENABLED.
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.
null | array
null on success, or a list of errors.

Docs for agents: llms.txt