EmailmoversMyDataHub docs
Browse the docs

Errors

Platform

The request is not valid

validation-failed: HTTP 422. Fix each entry in errors, using did_you_mean where given, and send it again.

Generated from the contractsView as Markdown

validation-failed is returned with HTTP status 422. Its type URI is https://emailmovers.com/mydatahub/docs/errors/validation-failed.

What it means

The request is readable but not valid. errors lists every problem with a JSON pointer, and did_you_mean offers the closest valid values.

A company, count, quote or suppression list that the body names but does not exist is reported here, with a pointer to the member.

What to do

Fix each entry in errors, using did_you_mean where given, and send it again.

Members it adds

Beyond type, title, status, detail, code and next_step, this problem carries errors and did_you_mean. They are published in the Problem schema of the OpenAPI document.

Example

{
  "type": "https://emailmovers.com/mydatahub/docs/errors/validation-failed",
  "title": "The request is not valid",
  "status": 422,
  "code": "validation-failed",
  "detail": "Unknown field company.employees.",
  "next_step": "Fix each entry in errors, using did_you_mean where given, and send it again.",
  "instance": "/v1/counts",
  "did_you_mean": ["company.employee_band"],
  "errors": [
    {
      "pointer": "/audience/where/all/0/field",
      "code": "invalid_value",
      "message": "Unknown field company.employees.",
      "did_you_mean": ["company.employee_band"]
    }
  ]
}

See also

All problem types are listed on Errors.