Skip to main content
trust_keys_unavailable means the service could not finish checking your credential because the data it checks against was unavailable. Read this page when calls that normally work fail with this code; your credential is not the problem.

What happened

Routes: every protected /v1/* route. The check depends on the kind of credential: The request was refused before any work was done. Nothing was stored or charged. Your credential was not rejected: a wrong, unknown or revoked key answers 401 invalid_credential instead.

How to fix

  • Retry with backoff (for example 2, 4, 8 and 16 seconds). Log the request_id of every failed attempt.
  • Do not rotate or delete your key because of this code.
  • On POST /v1/runs the same Idempotency-Key is safe to reuse: the request was refused before a run existed.
  • If it persists for several minutes, report a request_id.

Example

Retrying with backoff and your own request id: