Revoke a cryptographic key

Marks a key as REVOKED. This operation is irreversible.

A request body is REQUIRED and must carry a non-blank reason (PRD §231): the
operator's justification is recorded at canonical position 21 of the signed audit
event, so a revocation can be answered later. cause remains optional and defaults
to ADMINISTRATIVE when omitted.

State transition: Any non-deleted, non-revoked state → REVOKED.

Authorization: requires scope admin.keys.revoke.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
uuid
required
string
required
Query Params
string
Body Params

Revocation metadata for the audit trail and compliance reporting

string
enum

Typed reason for revocation. Defaults to ADMINISTRATIVE when not provided.
Use SECURITY_COMPROMISE for incident response — this is recorded separately
in compliance reports.

Allowed:
string
required
length between 1 and 1000

Free-text justification for the audit trail (mandatory)

Responses
204

Key revoked successfully (no content).

406

Not Acceptable — the request Accept header excludes every representation this endpoint produces. Per RFC 9110 §15.5.7 the response carries NO body and NO Content-Type.

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/problem+json