Error reference / request-invalid
Request body or parameters invalid
The JSON or query parameters did not match the schema.
| Problem type | /problems/request-invalid |
|---|---|
| HTTP status | 422 |
| Emitted by | Dashboard (JSON requests), REST API (/v1) |
| Title values | Request body or parameters invalid |
| Trigger | REST API (/v1): request body/params failed validation |
What happened
The request failed schema validation before any handler ran: a missing required member, a wrong type, or an unknown enum value. The response is HTTP 422 and detail lists the first few offending locations as path: message.
What it means
Nothing was processed. This is the schema check; validation-failed is the engine’s semantic check that runs after it.
What to do next
Fix the locations detail names. The request schemas are in the OpenAPI document at /v1/openapi.json; generated clients enforce them before sending.
Problem body
Every error is an RFC 9457 problem document with media type
application/problem+json. The type member is the
stable identifier to switch on; docs_url is this page.
{
"type": "/problems/request-invalid",
"title": "Request body or parameters invalid",
"status": 422,
"instance": "/v1/...",
"docs_url": "https://docs.signenvoy.com/errors/request-invalid"
}