Skip to main content

validation-failed

HTTP status: 400 Bad Request Type URI: https://docs.evinor.ai/problems/validation-failed

The request failed input validation — an out-of-range value, an unknown field, or a bad path/query parameter. (A body that is not valid JSON at all is a malformed-body instead.) The body includes an errors array with one { field, message } entry per problem, so you can pinpoint what to fix.

{
  "type": "https://docs.evinor.ai/problems/validation-failed",
  "title": "Validation failed",
  "status": 400,
  "detail": "The request payload failed validation.",
  "request_id": "…",
  "errors": [
    { "field": "filter.min_reports", "message": "Expected integer" },
    { "field": "actions", "message": "Array must contain at least 1 element(s)" }
  ]
}

A request that is well-formed but refused because of its content carries a stable code member instead of errors. POST /v1/reports uses this for checks against the event type, such as a role sent with the wrong value field (ROLE_VALUE_TYPE_MISMATCH). See Reporting events for every code.

Common causes​

  • Missing or wrongly-typed fields in a create/update body.
  • An unrecognized query parameter, or a limit outside the allowed range.
  • A malformed Idempotency-Key header (must be 1–255 characters of A-Za-z0-9_-).

How to resolve​

Correct each field named in the errors array and resend. Consult the API Reference for each endpoint's exact request schema. Because validation failures are never cached, you may safely retry with the same Idempotency-Key after fixing the payload.