Authorizations
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:
- Keep root keys secure and never expose them in client-side code
- Use different root keys for different environments
- Rotate keys periodically, especially after team member departures
- Create keys with minimal necessary permissions following least privilege principle
- Monitor key usage with audit logs.
Body
The maximum number of identities to return in a single request. Use this to control response size and loading performance.
1 <= x <= 100
50
Pagination cursor from a previous response. Use this to fetch subsequent pages of results when the response contains a cursor value.
"cursor_eyJrZXkiOiJrZXlfMTIzNCJ9"
Response
Successfully retrieved the list of identities
Metadata object included in every API response. This provides context about the request and is essential for debugging, audit trails, and support inquiries. The requestId
is particularly important when troubleshooting issues with the Unkey support team.
List of identities matching the specified criteria.
Pagination metadata for list endpoints. Provides information necessary to traverse through large result sets efficiently using cursor-based pagination.