API reference

Error code: temporarily_unavailable

temporarily_unavailable returns HTTP 503 with type: api_error. The service is briefly unavailable. Branch on this code — it is stable — and apply the fix below.

2 min read

503HTTP status
temporarily_unavailableerror.code
RetryHandling

What triggers it

The service is briefly unavailable. Maintenance or an overloaded dependency.

Example response

{
  "error": {
    "type": "api_error",
    "code": "temporarily_unavailable",
    "message": "The service is briefly unavailable."
  }
}

How to fix it

Retry with backoff; the service returns shortly.

This class is transient — see Retrying failed requests.

In practice

In a well-built client, temporarily_unavailable is handled by branching on error.code rather than on the human error.message, which may be reworded over time. The HTTP status (503) gives the broad api_error class; the code gives the specifics; and, on field errors, error.param pinpoints the input to fix.

This code is transient, so it belongs in the retry path: back off with jitter, honour Retry-After on a 429, and pair writes with an idempotency key so a retry after a timeout never double-applies. See Retrying failed requests and Build a resilient API client.

Frequently asked questions

Is temporarily_unavailable safe to retry?

Yes, with exponential backoff — it is transient.

Will this code ever change?

No. Error codes are stable contract. The human message may be reworded, but the code you branch on will not change.

Do I branch on the code or the HTTP status?

Both — the status for the retry-or-not decision, the code for the specific behaviour. See the error envelope.

Funding for UK limited companies

Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.