Your API keys (metadata only)
/keysEvery API key of the manager you are signed in as: active keys first, then revoked ones,
newest first within each. Only metadata is returned; a key's value is shown once, when it
is minted, and can never be read back. Revoked keys stay listed, with when each was created,
last used and revoked, so you can audit your key history. Capped at 100 rows; truncated is
true when there are more. No query parameters are accepted.
Only a dashboard session may call this; an API key is refused 403 session_required.
Responses
- 200
- 400
- 401
- 403
- 429
OK. Sent with Cache-Control: private, no-store.
invalid_request: a query parameter was sent.
unauthorized: no credential was sent at all (breaking change: this used to beinvalid_api_key), or a dashboard session failed verification: the access token is missing, malformed or expired, or the identity token is missing or belongs to a different login.invalid_api_key:X-API-Keyis malformed, unknown, or belongs to a different Treasures API.key_revoked: this key has been revoked; mint a new one or ask Treasures.
session_required: an API key cannot manage keys; call this from a signed-in dashboard session. manager_suspended, manager_not_linked, organization_suspended and permission_denied as on every route.
More than 60 requests in the last minute across every key you hold, or more than 120 across your dashboard sessions; each kind has its own budget. The Retry-After header carries the seconds to wait.
Response Headers
Seconds to wait before retrying.