Sign in to run requests with your own sandbox key. Sign in
422 Unprocessable Content

unprocessable_content — Unprocessable content

Message “The request could not be completed.”

What causes it

  • A record could not be persisted for a reason the `validation_failed` path did not report — the framework raised while saving. This comes with no `details`.

How to fix it

  1. Check the request body against the operation's schema and resend.
  2. If it persists, contact support with the `request_id`, the operation, and the approximate time.

Operations that return it

Any operation can return this code.

See the API reference for the full list of operations.

Example response

HTTP/1.1 422 Unprocessable Content · Content-Type: application/json

422 Unprocessable Content
{
  "error": {
    "code": "unprocessable_content",
    "message": "The request could not be completed.",
    "details": [],
    "request_id": "6f1c2a3e-8d4b-4c5e-9f0a-1b2c3d4e5f60",
    "doc_url": "https://cascades.crscreditapi.com/docs/api/errors/unprocessable_content"
  }
}