Skip to content

Key-State Seal Key Not Found

URI: https://docs.ankatech.co/errors/key-state-seal-key-not-found
HTTP Status: 404 Not Found

When you see this

A reopening named a key-state seal key generation that is neither ACTIVE nor PREVIOUS on this deployment. Only those two generations can be closed, so only they can be reopened. Nothing was changed.

Returned by POST /api/v3/admin/platform/key-state-seal-keys/{generation}/reopen (reopenKeyStateSealKey).

Common Causes

  • The generation number does not exist on this deployment.
  • The generation is RETIRED: its wrapped key was erased when a rotation completed.

Response Example

{
  "type": "https://docs.ankatech.co/errors/key-state-seal-key-not-found",
  "title": "Key-State Seal Key Not Found",
  "status": 404,
  "detail": "No ACTIVE or PREVIOUS key-state seal key of that generation exists on this deployment.",
  "instance": "/api/v3/admin/platform/key-state-seal-keys/7/reopen",
  "extensions": {
    "requestId": "6f1c2d3e-4a5b-4c6d-8e7f-9a0b1c2d3e4f"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. This is an Admin API body, so the correlation identifier is extensions.requestId; see Error Index & Overview.

How to Resolve

  1. Read listKeyStateSealKeys (GET /api/v3/admin/platform/key-state-seal-keys, newest generation first) and take the generation that reads ACTIVE or PREVIOUS with proofClosedBy MISMATCH.
  2. Reopen that generation.

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