Create an API key

POST 
/api/v1/auth/api-keys

Mint a new API key for the authenticated admin or owner.

Scopes are validated against the caller's role bundle (reduce-only; wildcards owner-only). The full key is returned exactly once in the response body — it cannot be recovered later.

• Router-gated by release_api_keys (404 when off).
• API-key scope required: api_keys:create.
• 400 on invalid scopes or scope escalation attempts.

Request

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.