GET /me/api-keys
Lists keys for the current org, sorted by created_at descending. The response matches the api_keys field in GET /me.
When
true, includes revoked keys (with non-null revoked_at).POST /me/api-keys
Creates a new key. The plaintext value is returned once.
Body
Optional human-readable label, max 64 chars.
Permission scopes for the new key. Default
["*"] means full access. Scoped keys (e.g. ["read"]) are reserved for future use.Response — 201
Plaintext key. Store immediately.
Metadata for the key, including id, prefix, display_id, name, scopes, and timestamps.
DELETE /me/api-keys/{id}
Revokes a key. Returns 204 No Content.
The key’s UUID (the
id field, not the prefix or display_id).Examples
Operational tips
- One key per environment. Mint
production,staging, andlocal-devseparately. - Alert if a key has not been used in 30 days. It may be abandoned.
- Do not share keys across services. Give each service its own key so revocation is narrow.

