Reference
bad_request
The request could not be processed, and the reason does not fit a more specific code.
What it means
The request could not be processed, and the reason does not fit a more specific code.
Do not retry
The identical request will fail the same way every time. Change it first.
What causes it
- A query parameter had a value the endpoint does not accept.
- A combination of otherwise-valid parameters is contradictory.
- The endpoint received a shape it recognises but cannot act on in the current state.
How to fix it
- Read `detail` — on this code it is written for a human and names the actual problem.
- Compare the request against the endpoint in the API reference, parameter by parameter.
What the response looks like
{
"error": {
"code": "bad_request",
"message": "The request could not be processed, and the reason does not fit a more specific code",
"request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
},
"type": "https://integrable.cloud/docs/errors/bad_request",
"title": "Bad Request",
"status": 400,
"detail": "The request could not be processed, and the reason does not fit a more specific code",
"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.