400
Bad Request
bad_request — Bad request
Message
What causes it
- A required top-level parameter was absent from the request body or query string; `details[0].field` names it.
- The query string could not be parsed — for example the same key sent as both a scalar and a nested hash (`filter=1&filter[status]=failed`). This variant comes from the framework with the message "The request could not be completed." and no `details`.
How to fix it
- Add the parameter named in `details[].field` and resend.
- Send filters consistently as `filter[<name>]=<value>`; never mix `filter=` with `filter[...]` in one request.
- Send `Content-Type: application/json` with a JSON object body for write operations.
Operations that return it
Any operation can return this code.
See the API reference for the full list of operations.
Example response
HTTP/1.1 400 Bad Request
· Content-Type: application/json
400 Bad Request
{
"error": {
"code": "bad_request",
"message": "A required parameter is missing.",
"details": [
{
"field": "rows",
"message": "parameter is required"
}
],
"request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
"doc_url": "https://cascades.crscreditapi.com/docs/api/errors/bad_request"
}
}