Archive a cryptographic key

Moves a revoked key to archived state for compliance/audit retention.
Archived keys are read-only and cannot be used for cryptographic operations.

Workflow:

  1. Validates tenant access from JWT
  2. Validates key is in REVOKED state
  3. Updates key status to ARCHIVED in PostgreSQL
  4. Publishes audit event to Kafka

Use cases:

  • Long-term compliance retention after revocation
  • Audit trail preservation
  • Historical data retention requirements

State transition: REVOKED → ARCHIVED (other states rejected with 409).

Authorization: requires scope admin.keys.archive.

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

Key archived 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