Validation errors

Request validation in its common styles: /register — hand-written rules, 422 application/problem+json (RFC 7807) with per-field errors. /strict — rejects unknown fields (400) as well as invalid ones (422). /annotations — DataAnnotations model; [ApiController] produces the framework's automatic 400. /problem/{type} — sample problem documents for each common error status. Nothing is stored, so the same payload always gets the same answer.

• POSThttps://api.testingapis.com/api/validation/annotationsValidate a DataAnnotations model using the framework's automatic 400Validate a DataAnnotations model using the framework's automatic 400.
• GEThttps://api.testingapis.com/api/validation/problemList the sample problem document typesList the sample problem document types.
• GEThttps://api.testingapis.com/api/validation/problem/{type}Get a sample RFC 7807 problem documentGet a sample RFC 7807 problem document.
• POSThttps://api.testingapis.com/api/validation/registerRegister a userRegister a user; invalid fields return 422 problem+json.
• POSThttps://api.testingapis.com/api/validation/strictAccept only known fieldsAccept only known fields; unknown fields return 400.

curl -X GET "https://api.testingapis.com/api/validation/problem" \
  -H "X-TestingApis-Key: YOUR_API_KEY"

[
  {"type": "bad-request", "status": 400, "url": "/api/validation/problem/bad-request"},
  {"type": "unauthorized", "status": 401, "url": "/api/validation/problem/unauthorized"},
  "… 8 more items"
]