Returning a 422 status code along with a detailed validation message in the response body allows the client to understand the reason for the failure and take appropriate action. The response body can include information about the specific validation errors, such as missing or invalid input, format requirements, or any other relevant details.
[HttpPost]public IActionResult Create([FromBody] MyModel model){ if (!ModelState.IsValid) { var validationErrors = ModelState.Values .SelectMany(v => v.Errors) .Select(e => e.ErrorMessage) .ToList(); return StatusCode(422, new { errors = validationErrors }); } // Process the valid request // ... return Ok();}
[HttpPost]
public IActionResult Create([FromBody] MyModel model)
{
if (!ModelState.IsValid)
var validationErrors = ModelState.Values
.SelectMany(v => v.Errors)
.Select(e => e.ErrorMessage)
.ToList();
return StatusCode(422, new { errors = validationErrors });
}
// Process the valid request
// ...
return Ok();
422
When an API encounters a validation error, it should typically return a 422 Unprocessable Entity status code. The HTTP 422 status code indicates that the server understands the content type of the request but was unable to process the contained instructions.In the context of validation errors, a 422 status code communicates that the server received the request, but the data within the request did not pass validation. Alongside the 422 status code, the API should provide details about the validation errors in the response body, typically in a well-structured format (e.g., JSON). This allows the client to understand which parts of the request failed validation and provides specific error messages or guidance for correction.