validation_error

The payload was well-formed JSON but failed schema validation.

• A required field was absent.
• A field carried the wrong type — a string where a number was expected, or null on a non-nullable field.
• A string ran past its maximum length, or an enum value is not one of the accepted set.

• Read `details.errors` — it is the full per-field validation report, with the JSON path to each failure.
• Validate against the OpenAPI schema before sending. The generated SDKs do this for you.

This code carries a details object with more than the message can say:

{
  "error": {
    "code": "validation_error",
    "message": "The payload was well-formed JSON but failed schema validation",
    "details": { ... },
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/validation_error",
  "title": "Validation Error",
  "status": 422,
  "detail": "The payload was well-formed JSON but failed schema validation",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• bad_request

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.