Retrieve a paginated list of API keys for dashboard and administrative interfaces.
Use this to build key management dashboards, filter keys by user with externalId
, or retrieve key details for administrative purposes. Each key includes status, metadata, permissions, and usage limits.
Important: Set decrypt: true
only in secure contexts to retrieve plaintext key values from recoverable keys.
Required Permissions
Your root key must have one of the following permissions for basic key listing:
api.*.read_key
(to read keys from any API)api.<api_id>.read_key
(to read keys from a specific API)Additionally, you need read access to the API itself:
api.*.read_api
or api.<api_id>.read_api
Additional permission required for decrypt functionality:
api.*.decrypt_key
or api.<api_id>.decrypt_key
Unkey uses API keys (root keys) for authentication. These keys authorize access to management operations in the API. To authenticate, include your root key in the Authorization header of each request:
Authorization: Bearer unkey_123
Root keys have specific permissions attached to them, controlling what operations they can perform. Key permissions follow a hierarchical structure with patterns like resource.resource_id.action
(e.g., apis.*.create_key
, apis.*.read_api
).
Security best practices:
Successfully retrieved paginated keys. Use the pagination cursor for additional results when hasMore: true
.
The response is of type object
.