[Solved] When should a REST API return a 422 Unprocessable Entity status code? — Ans: When the request body is syntactically correct but contains invalid data | Rest API

Rest API - HTTP Status Codes

When should a REST API return a 422 Unprocessable Entity status code?

AWhen the user is not authenticated

BWhen the requested URL does not exist

CWhen the request body is syntactically correct but contains invalid data

DWhen the server is down for maintenance

Step-by-Step Solution

Solution:

Step 1: Identify the condition for 422
422 is used when the request syntax is correct but the data is invalid or semantically wrong, like missing required fields or invalid formats.
Step 2: Eliminate other options
404 is for missing URLs, 401 for authentication, and 503 for server maintenance, so they don't fit 422.
Final Answer:
When the request body is syntactically correct but contains invalid data -> Option C
Quick Check:
422 triggers on invalid data, not missing URL or auth [OK]

Quick Trick: Use 422 for valid syntax but invalid data [OK]

Common Mistakes:

Master "HTTP Status Codes" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

When should a REST API return a 422 Unprocessable Entity status code?