Reference
internal_error
Something failed on our side that was not anticipated. The response deliberately carries no detail beyond a request id.
What it means
Something failed on our side that was not anticipated. The response deliberately carries no detail beyond a request id.
Retry with backoff
Transient. Retry with exponential backoff and jitter, not a fixed interval.
What causes it
- An unhandled exception. The full trace is logged server-side and never sent to a client — a traceback in a response body is a disclosure, not a courtesy.
How to fix it
- Quote the `request_id` from the response when you contact support. It is what lets us find the exact stack.
- Retry once with backoff; a genuinely transient fault will clear.
What the response looks like
{
"error": {
"code": "internal_error",
"message": "Something failed on our side that was not anticipated. The response deliberately carries no detail beyond a request id",
"request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
},
"type": "https://integrable.cloud/docs/errors/internal_error",
"title": "Internal Error",
"status": 500,
"detail": "Something failed on our side that was not anticipated. The response deliberately carries no detail beyond a request id",
"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.