Invalid Stable KID Transition

URI: https://docs.ankatech.co/errors/stable-kid-status-invalid-transition
HTTP Status: 422 Unprocessable Entity

When you see this

The requested status change for the stable key identifier (stable kid) is not allowed from its current status.

Common Causes

Transitioning a stable kid to a status it cannot reach from its current one.
Reactivating a stable kid that is in a terminal status.
A status change that violates the stable-kid lifecycle rules.

Response Example

{
  "type": "https://docs.ankatech.co/errors/stable-kid-status-invalid-transition",
  "title": "Invalid Stable KID Transition",
  "status": 422,
  "detail": "Stable kid cannot transition from 'RETIRED' to 'ACTIVE'.",
  "instance": "/api/v3/admin/keys/my-mlkem-key/status",
  "correlationId": "550e8400-e29b-41d4-a716-446655440000",
  "timestamp": 1730000000
}

Content-Type: application/problem+json — the response follows RFC 7807 Problem Details.

How to Resolve

Check the stable kid's current status before requesting a transition.
Request only transitions valid from the current status.
If the stable kid is retired or terminal, create a new key instead.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.