Revoke an API key

DELETE 
/api/v1/auth/api-keys/:key_id

Revoke one of the caller's API keys (soft delete).

After revocation the key is rejected at authentication time. The stored record is retained and a revocation audit event is emitted.

• Router-gated by release_api_keys (404 when off).
• 400 if the key is already revoked.
• 404 if the key does not belong to the caller.
• API-key scope required: api_keys:revoke.

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.