type URI on every invalid_request problem body: https://docs.get-exo.com/errors/invalid_request.
HTTP status: 400 Bad Request.
Why it happens
This is the default code for a 400 that a route did not name more specifically. The common named ones areinvalid_cursor on a tampered pagination cursor and pagination_unsupported on a recall view that is not a list.
A 400 means Exo could not act on the request as sent. A body that parsed but failed validation is 422 validation_error instead.
How to fix it
- Check the request line and headers before the body: a 400 here usually means a query parameter or a header, not a field.
- Quote the
requestIdfrom the response if you need to ask about a specific call.
Related
invalid_cursorpagination_unsupportedsubject_not_supported- Errors for the envelope and the full catalogue