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_idof every failed attempt. - Do not rotate or delete your key because of this code.
- On
POST /v1/runsthe sameIdempotency-Keyis safe to reuse: the request was refused before a run existed. - If it persists for several minutes, report a
request_id.
Example
Related
- Authentication - how a credential is checked.
- invalid_credential - the 401 when the credential itself is rejected.
- Error handling - a status-to-action table and a retry helper for every error.
- Request ids - send your own
x-request-idand quote it when you report a problem. - Problem codes - every code, its status, and whether a retry can help.