Skip to main content

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.
boolean
default:"false"
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

string
Optional human-readable label, max 64 chars.
array[string]
default:"[\"*\"]"
Permission scopes for the new key. Default ["*"] means full access. Scoped keys (e.g. ["read"]) are reserved for future use.

Response — 201

string
Plaintext key. Store immediately.
object
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.
string
required
The key’s UUID (the id field, not the prefix or display_id).
Revocation is irreversible. Existing JWTs created from a revoked key keep working until they expire, up to 24h after revocation.

Examples

Operational tips

  • One key per environment. Mint production, staging, and local-dev separately.
  • 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.