Rest API - HTTP Status Codes
A REST API uses 422 Unprocessable Entity for validation errors. How should it handle nested JSON validation errors for a user address field?
A REST API uses 422 Unprocessable Entity for validation errors. How should it handle nested JSON validation errors for a user address field?
hard📝 Application Q9 of 15
Step-by-Step Solution
Solution:
Step 1: Understand nested validation error reporting
Best practice is to return detailed nested error info so clients know exactly which nested fields failed.Step 2: Compare with other options
Ignoring nested details or using 400/500 is less precise and not recommended for validation errors.Final Answer:
Return 422 with a JSON error object showing nested keys and messages -> Option AQuick Check:
Nested validation errors need detailed JSON in 422 response [OK]
Quick Trick: Use nested JSON error details with 422 for complex validation [OK]
Common Mistakes:
MISTAKES- Returning generic error messages for nested fields
- Using 400 or 500 instead of 422 for validation
- Not including nested keys in error response
Master "HTTP Status Codes" in Rest API
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Rest API Quizzes