Skip to content

Projection Signing Key Not Published

URI: https://docs.ankatech.co/errors/projection-signing-key-not-published
HTTP Status: 404 Not Found

When you see this

A platform administrator asked to revoke a projection signing key whose kid is not in the published set. Unknown, already retired and already revoked keys deliberately get this one answer. Nothing was changed.

Common Causes

  • The key was already revoked — by another administrator, or by an earlier attempt of the same request.
  • The key was retired by the platform after its replacement took over.
  • The kid was copied incorrectly.

Response Example

HTTP/1.1 404 Not Found
Content-Type: application/problem+json

{
  "type": "https://docs.ankatech.co/errors/projection-signing-key-not-published",
  "title": "Projection Signing Key Not Published",
  "status": 404,
  "detail": "The projection signing key is not in the published set",
  "instance": "/api/v3/admin/platform/projection-signing-keys/Zb8nC4qWe7Rt1Yu5Io9Pa3Sd6Fg2Hj0Kl4Zx8Cv1Bmw/actions/revoke",
  "timestamp": 1798596000,
  "extensions": {
    "requestId": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }
}

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

How to Resolve

  1. List the projection signing keys again and take the kid from the current set.
  2. If the key is gone, there is nothing left to revoke.

See Projection Signing Keys for the screen that lists, rotates and revokes these keys.

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