422 Unprocessable Entity in Rest API - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does HTTP status 422 mean?

When a server responds with status code 422, what is the best description of this response?

A The requested resource was not found on the server.

B The server understood the request but the data was invalid or semantically incorrect.

C The client is not authorized to access the requested resource.

D The server encountered an unexpected error and could not complete the request.

💡 Hint

Think about the difference between syntax errors and semantic errors in requests.

422 means the server understood the request syntax but the content was invalid or could not be processed.

❓ Predict Output

intermediate

What is the HTTP status code returned?

Consider this REST API response after sending invalid JSON data:

{"error": "Invalid email format"}

Which HTTP status code is most appropriate?

A 400 Bad Request

B 404 Not Found

C 422 Unprocessable Entity

D 500 Internal Server Error

💡 Hint

Think about whether the syntax or the content is invalid.

422 is used when the request syntax is correct but the content is invalid, like an invalid email format.

❓ Predict Output

advanced

What is the output of this API error handler?

Given this Python Flask code snippet handling a POST request:

from flask import Flask, request, jsonify
app = Flask(__name__)

@app.route('/user', methods=['POST'])
def create_user():
    data = request.get_json()
    if not data or 'email' not in data:
        return jsonify({'error': 'Missing email'}), 422
    if '@' not in data['email']:
        return jsonify({'error': 'Invalid email format'}), 422
    return jsonify({'message': 'User created'}), 201

# Assume client sends: {"email": "userexample.com"}

What is the HTTP status code returned?

A 500

B 201

C 400

D 422

💡 Hint

Check the email validation logic and the returned status codes.

The email is missing '@', so the server returns 422 Unprocessable Entity with an error message.

🔧 Debug

advanced

Why does this API return 422 instead of 400?

Look at this Express.js code snippet:

app.post('/submit', (req, res) => {
  const { age } = req.body;
  if (typeof age !== 'number') {
    return res.status(422).json({ error: 'Age must be a number' });
  }
  res.status(200).send('Success');
});

Why is 422 used instead of 400?

A Because the request syntax is correct but the data type is semantically wrong.

B Because the resource was not found.

C Because the user is unauthorized.

D Because the server crashed processing the request.

💡 Hint

Think about the difference between syntax errors and semantic errors in data.

422 is used when the request is syntactically valid but the content is semantically invalid, like wrong data type.

🧠 Conceptual

expert

When should a REST API return 422 instead of 400?

Which scenario best describes when a REST API should return a 422 Unprocessable Entity instead of a 400 Bad Request?

A The JSON syntax is valid but some fields fail validation rules.

B The JSON syntax is invalid and cannot be parsed.

C The requested URL does not exist on the server.

D The client is not authenticated to access the resource.

💡 Hint

Consider the difference between syntax errors and semantic validation errors.

400 is for malformed syntax, 422 is for semantically invalid content despite correct syntax.