Mark an archived key for destruction

Transitions an ARCHIVED key to PENDING_DESTRUCTION state, establishing
a mandatory cooling-off period before logical deletion is permitted.

The response includes destructionEligibleFrom — the earliest timestamp
at which DELETE will succeed. DELETE requests before that date return
412 Precondition Failed.

No scheduler is required: destruction remains manual but is gated by
the temporal constraint. When a scheduler microservice is added, it will
call the same DELETE endpoint automatically.

Valid source state: ARCHIVED only.
State transition: ARCHIVED → PENDING_DESTRUCTION.

Authorization: requires scope admin.keys.mark-for-destruction.

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

Request to schedule an archived key for destruction with a mandatory cooling-off period

int32
0 to 365
Defaults to 30

Number of days to wait before the key can be logically deleted.
Defaults to 30 days when not specified. The system enforces this
as a temporal gate on the DELETE endpoint (412 Precondition Failed
until the date has elapsed). An explicit value of 0 means no
cooling-off period: destructionEligibleFrom is set to the
mark-for-destruction instant, so DELETE is permitted immediately.

int32
Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

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