validation_error
The request does not match the expected schema (missing field, wrong type, or invalid value).
| HTTP | code | Retryable? |
|---|---|---|
| 400 | validation_error | no |
When it happens
The body, query parameters, or headers fail input validation. This includes one case that surprises many clients: a parameter we do not recognise is rejected, not ignored. Send a misspelled or retired parameter name and you get a 400 rather than a silently unfiltered response — deliberate on a money API, where an ignored filter returns the wrong answer without telling you.
How to resolve it
Read detail (every failure, joined with ; ) and the errors array, which carries the same messages one per entry for programmatic handling. They name the exact field: property asset should not exist means that parameter does not exist — check its name in the endpoint reference. Do not retry without changing the request.
Example
{
"type": "https://docs.skipo.com/errors/validation_error",
"title": "Validation error",
"status": 400,
"code": "validation_error",
"retryable": false,
"detail": "property asset should not exist; assetSymbol must be a valid asset symbol"
}
Back to the error catalog · See the error format.