Identity Service Unavailable

auth-unavailable · 503

The API couldn't read the identity service's signing keys, so it couldn't check the token and changed nothing.

The token isn't the problem, and there is nothing in the request to fix. A token the API checked and refused answers invalid-token instead.

This type adds no members to the ones every error carries.

Common causes

  • The identity service is unreachable, and the API holds no signing keys from before.

How to fix the call

  • Retry the same request after a short wait, with a growing delay.
  • Keep the token: it hasn't been refused.
  • If it lasts, tell the user the platform can't sign anyone in right now, and quote requestId.

Example response

json
{
  "type": "auth-unavailable",
  "title": "Identity Service Unavailable",
  "detail": "The identity service's signing keys could not be read, so this request could not be authenticated. Nothing has changed; try again shortly.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects",
  "method": "GET",
  "instance": "GET /v1/projects",
  "status": 503,
  "docs": "https://ghaym.me/docs/errors/auth-unavailable"
}