Rest API - HTTP Status Codes
What will be the HTTP status code returned if a REST API receives a request with correct JSON syntax but missing a required field, and it uses 422 for validation errors?
What will be the HTTP status code returned if a REST API receives a request with correct JSON syntax but missing a required field, and it uses 422 for validation errors?
medium📝 Predict Output Q5 of 15
Step-by-Step Solution
Solution:
Step 1: Understand validation error handling
If the API uses 422 for semantic validation errors, missing required fields trigger 422 because the request is syntactically valid but semantically incomplete.Step 2: Compare with other status codes
400 is generic bad request, 404 is resource missing, 500 is server error, so 422 fits best for validation errors.Final Answer:
422 Unprocessable Entity -> Option DQuick Check:
Missing required field with valid syntax = 422 [OK]
Quick Trick: Use 422 for missing required fields with valid syntax [OK]
Common Mistakes:
- Using 400 instead of 422 for validation errors
- Returning 404 for missing fields
- Confusing 422 with server errors
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