Token Signing Key Set Not Initialized

URI: https://docs.ankatech.co/errors/token-signing-key-set-not-initialized
HTTP Status: 503 Service Unavailable

When you see this

A key-set operation reached admin-api before the user-token signing key set existed. On a fresh deployment the platform's scheduler creates the first ACTIVE and NEXT keys on its next tick, within 60 seconds. Nothing was changed.

Common Causes

• The environment was created a moment ago and the scheduler has not ticked yet.
• The scheduler cannot initialize the set because the custody root is unavailable or the deployment key-protection backend is not bound yet.

Response Example

HTTP/1.1 503 Service Unavailable
Content-Type: application/problem+json
Retry-After: 60

{
  "type": "https://docs.ankatech.co/errors/token-signing-key-set-not-initialized",
  "title": "Token Signing Key Set Not Initialized",
  "status": 503,
  "detail": "The token signing key set has not been initialized",
  "instance": "/api/v3/admin/platform/token-signing-keys",
  "timestamp": 1790820180,
  "extensions": {
    "requestId": "c2a9e7d4-5f1b-4c3a-8e6d-0b9f7a2c4e51"
  }
}

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

How to Resolve

1. Retry after Retry-After (one scheduler tick).
2. If the answer persists past a few ticks, check that the deployment key-protection backend is bound (GET /api/v3/admin/platform/setup/status) and read admin-api's log for the scheduler's initialization attempts.

See Admin API — Platform Token Signing Keys^*.

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