Reference
service_unavailable
The API is temporarily not accepting this work.
503HTTP 503 · Service Unavailable
What it means
The API is temporarily not accepting this work.
Retry with backoff
Transient. Retry with exponential backoff and jitter, not a fixed interval.
What causes it
- A deploy or migration is in progress.
- A dependency is being shed deliberately to protect the rest of the system.
How to fix it
- Retry with backoff — this is the code most likely to clear by itself.
- Check the status page before investigating your own integration.
What the response looks like
503 application/problem+json
{
"error": {
"code": "service_unavailable",
"message": "The API is temporarily not accepting this work",
"request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
},
"type": "https://integrable.cloud/docs/errors/service_unavailable",
"title": "Service Unavailable",
"status": 503,
"detail": "The API is temporarily not accepting this work",
"instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.
Still stuck
Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.
Something here wrong or missing? Tell us — the documentation and the API are maintained by the same person, so a correction is a fix rather than a ticket.