Reference
http_error
A generic fallback used when a failure has an HTTP status but no more specific code was assigned.
What it means
A generic fallback used when a failure has an HTTP status but no more specific code was assigned.
Retry with backoff
Transient. Retry with exponential backoff and jitter, not a fixed interval.
What causes it
- A framework-level rejection that did not map to one of the taxonomy's own classes.
How to fix it
- Read `status` and `detail` — on this code they carry the whole signal.
- If you can reproduce it, send us the `request_id`; a fallback code reaching a client usually means a case that deserves its own.
What the response looks like
{
"error": {
"code": "http_error",
"message": "A generic fallback used when a failure has an HTTP status but no more specific code was assigned",
"request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
},
"type": "https://integrable.cloud/docs/errors/http_error",
"title": "HTTP Error",
"status": 400,
"detail": "A generic fallback used when a failure has an HTTP status but no more specific code was assigned",
"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.