Skip to main content
HTTP status422 Unprocessable Entity
Codevalidation_error
Retry?No — fix the request and re-issue.

​
When this happens

The request matched the route but the body or query parameters failed schema validation. Examples:
  • A required field is missing.
  • A field has the wrong type.
  • An enum field has a value not in the allowed set.
  • A numeric field is out of range.
  • limit exceeds the per-endpoint cap (see Pagination).

​
Example response

For a missing required field: 
{
  "detail": [
    {
      "loc": ["body", "policy_slug"],
      "msg": "Field required",
      "type": "missing"
    }
  ],
  "code": "validation_error",
  "request_id": "5b3f6c7e-7d24-4d40-9b12-3a59c01c6e91",
  "doc_url": "https://docs.lasscyber.com/errors/validation_error"
}
detail is an array of items, each shaped { loc, msg, type }:
FieldMeaning
locPath to the offending field. body.policy_slug means the JSON body’s top-level policy_slug.
msgHuman-readable message.
typePydantic / FastAPI error type, e.g. missing, value_error, type_error.integer.

​
How to fix

  1. Read the loc of every item in detail.
  2. Compare with the auto-generated schema in the API reference.
  3. Fix the request and re-send.

​
SDK behaviour

SDKException
Pythonagnes.ValidationError with field_errors: dict[str, str] mapping dotted-path → message.
TypeScriptValidationError with fieldErrors: Record<string, string>.
Both SDKs walk the detail array for you so you can branch on specific fields without re-parsing JSON.