422 Unprocessable Entity in Rest API

Introduction

The 422 Unprocessable Entity status tells you that the server understands your request but cannot process it because the data is wrong or incomplete.

When a user submits a form with missing required fields.

When the data sent to the server does not follow the expected format.

When an API receives a request with invalid values that it cannot handle.

When you want to tell the client that the request is syntactically correct but semantically wrong.

When validating input data before saving it to a database.

Syntax

Rest API

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json

{
  "error": "Description of what is wrong with the data"
}

422 is part of the HTTP status codes used in REST APIs to communicate errors.

It means the server understood the request but the data is invalid or incomplete.

Examples

This response tells the client that the email field is required but was not provided.

Rest API

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json

{
  "error": "Email field is missing"
}

This response informs the client that the password does not meet the minimum length requirement.

Rest API

HTTP/1.1 422 Unprocessable Entity
Content-Type: application/json

{
  "error": "Password must be at least 8 characters"
}

Sample Program

This simple Flask app checks if the JSON request has an email and a password of at least 8 characters. If not, it returns a 422 status with an error message.

Rest API

from flask import Flask, request, jsonify

app = Flask(__name__)

@app.route('/register', methods=['POST'])
def register():
    data = request.json
    if not data or 'email' not in data:
        return jsonify({'error': 'Email field is missing'}), 422
    if len(data.get('password', '')) < 8:
        return jsonify({'error': 'Password must be at least 8 characters'}), 422
    return jsonify({'message': 'User registered successfully'})

if __name__ == '__main__':
    app.run(debug=True)

Important Notes

422 is different from 400 Bad Request because 400 means the request is malformed, while 422 means the request is well-formed but the data is invalid.

Always provide clear error messages with 422 so clients know how to fix their data.

Summary

422 means the server understands the request but the data is invalid or incomplete.

Use 422 to tell clients exactly what is wrong with their input.

It helps improve communication between client and server for better user experience.

Practice

1. What does the HTTP status code 422 Unprocessable Entity indicate in a REST API?

easy

A. The server encountered an unexpected error.

B. The server understands the request but the data is invalid or incomplete.

C. The requested resource was not found on the server.

D. The client is not authorized to access the resource.

Solution

1. Step 1: Understand HTTP status codes

   HTTP status codes communicate the result of a client's request to the server.

2. Step 2: Identify the meaning of 422

   422 means the server understood the request but the data sent is invalid or incomplete, so it cannot process it.

3. Final Answer:

   The server understands the request but the data is invalid or incomplete. -> Option B

4. Quick Check:

   422 = invalid or incomplete data [OK]

Hint: 422 means data is wrong but request format is correct [OK]

Common Mistakes:

• Confusing 422 with 404 Not Found
• Thinking 422 means server error
• Assuming 422 means unauthorized access

2. Which of the following is the correct way to respond with a 422 status code in a REST API using Express.js (Node.js)?

easy

A. res.sendStatus(404);

B. res.status(200).json({ message: 'Success' });

C. res.status(500).json({ error: 'Server error' });

D. res.status(422).send('Invalid input data');

Solution

1. Step 1: Identify correct status code usage

   To send a 422 status, use res.status(422) in Express.js.

2. Step 2: Confirm response method

   Using .send() or .json() after setting status sends the response properly.

3. Final Answer:

   res.status(422).send('Invalid input data'); -> Option D

4. Quick Check:

   Express 422 response = res.status(422).send() [OK]

Hint: Use res.status(422) to set code before sending response [OK]

Common Mistakes:

• Using wrong status code like 404 or 500
• Forgetting to set status before sending response
• Sending 200 OK for invalid data

3. Consider this JSON response from a REST API:

{
  "status": 422,
  "errors": {
    "email": "Invalid email format",
    "password": "Password too short"
  }
}

What does this response tell the client?

medium

A. The server could not process the request because the email and password fields are invalid.

B. The server processed the request successfully with no errors.

C. The server is down and cannot handle requests.

D. The client is not authorized to access this resource.

Solution

1. Step 1: Analyze the status code

   Status 422 means the server understood the request but found invalid data.

2. Step 2: Interpret the errors object

   The errors show specific problems: invalid email format and password too short.

3. Final Answer:

   The server could not process the request because the email and password fields are invalid. -> Option A

4. Quick Check:

   422 + errors = invalid input fields [OK]

Hint: 422 with errors means input fields have problems [OK]

Common Mistakes:

• Thinking 422 means server failure
• Ignoring the errors object details
• Assuming success when status is 422

4. You wrote this code snippet in a REST API controller:

if (!user.email.includes('@')) {
  res.status(422).json({ error: 'Invalid email' });
}
// further processing

But clients report they still get 200 OK even with invalid emails. What is the likely bug?

medium

A. The client is ignoring the 422 status code.

B. The status code 422 is not supported by REST APIs.

C. The function does not return after sending the 422 response, so processing continues.

D. The email validation logic is correct, so the bug is elsewhere.

Solution

1. Step 1: Check response flow

   After sending a response, the function must stop further processing to avoid sending another response.

2. Step 2: Identify missing return

   If return is missing before res.status(422)..., the code continues and may send 200 OK later.

3. Final Answer:

   The function does not return after sending the 422 response, so processing continues. -> Option C

4. Quick Check:

   Return after res.status(422) to stop processing [OK]

Hint: Always return after sending 422 response to stop code [OK]

Common Mistakes:

• Not returning after sending response
• Misunderstanding 422 support in REST
• Blaming client instead of server code

5. You are designing a REST API endpoint for user registration. Which approach best uses the 422 status code to improve client communication when input data is invalid?

hard

A. Return 422 with a JSON object listing each invalid field and a clear error message.

B. Return 422 with a generic message: 'Invalid data'.

C. Return 400 Bad Request without details about the errors.

D. Return 200 OK and ignore invalid fields silently.

Solution

1. Step 1: Understand purpose of 422

   422 is used to tell clients exactly what data is invalid to help fix input.

2. Step 2: Choose detailed error reporting

   Providing a JSON object with each invalid field and message improves client experience.

3. Final Answer:

   Return 422 with a JSON object listing each invalid field and a clear error message. -> Option A

4. Quick Check:

   422 + detailed errors = better client feedback [OK]

Hint: Use 422 with detailed errors for clear client feedback [OK]

Common Mistakes:

• Sending vague error messages
• Using wrong status codes like 400 or 200
• Not informing client about specific invalid fields