400 Bad Request in Rest API - Mini Project: Build & Apply

Understanding and Handling 400 Bad Request in REST API

📖 Scenario: You are building a simple REST API that accepts user data. Sometimes, users send incorrect or incomplete data, and your API needs to respond properly with a 400 Bad Request error.

🎯 Goal: Build a small REST API endpoint that checks incoming data and returns a 400 Bad Request response if the data is missing required fields.

📋 What You'll Learn

Create a dictionary called user_data with keys name and email and exact values "Alice" and "[e-mail]"

Create a variable called required_fields that contains a list with "name" and "email"

Write a for loop that checks if each field in required_fields is in user_data

Print "400 Bad Request: Missing {field}" if a required field is missing, otherwise print "200 OK: Data is valid"

💡 Why This Matters

🌍 Real World

APIs often receive data from users or other systems. Validating this data and responding with clear error messages helps keep the system reliable and user-friendly.

💼 Career

Understanding how to handle 400 Bad Request errors is important for backend developers, API designers, and anyone working with web services to ensure robust and clear communication with clients.

1

DATA SETUP: Create user data dictionary

Create a dictionary called user_data with these exact entries: 'name': 'Alice' and 'email': '[e-mail]'

Rest API

# Create the user_data dictionary with name and email
# Your code here

Hint

Use curly braces {} to create a dictionary with keys and values.

2

CONFIGURATION: Define required fields list

Create a variable called required_fields that contains a list with the strings 'name' and 'email'

Rest API

user_data = {'name': 'Alice', 'email': '[e-mail]'}
# Create the required_fields list with 'name' and 'email'
# Your code here

Hint

Use square brackets [] to create a list of required field names.

3

CORE LOGIC: Check for missing fields

Write a for loop using variable field to check if each field in required_fields is present in user_data. If a field is missing, print "400 Bad Request: Missing {field}" and stop checking further.

Rest API

user_data = {'name': 'Alice', 'email': '[e-mail]'}
required_fields = ['name', 'email']
# Write a for loop to check each required field in user_data
# Your code here

Hint

Use for field in required_fields: and check if field not in user_data: inside the loop.

4

OUTPUT: Print success message if all fields present

Add an else block to the for loop that prints "200 OK: Data is valid" if no required fields are missing.

Rest API

user_data = {'name': 'Alice', 'email': '[e-mail]'}
required_fields = ['name', 'email']
for field in required_fields:
    if field not in user_data:
        print(f"400 Bad Request: Missing {field}")
        break
# Add else block to print success message if no fields are missing
# Your code here

Hint

The else after a for loop runs only if the loop did not break.

Practice

1.

What does a 400 Bad Request status code indicate in a REST API?

easy

A. The server cannot process the request because it is malformed or invalid.

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

C. The server encountered an internal error while processing the request.

D. The client is not authorized to access the requested 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 400 status

   400 means the request is bad because it is malformed or invalid, so the server refuses to process it.

3. Final Answer:

   The server cannot process the request because it is malformed or invalid. -> Option A

4. Quick Check:

   400 Bad Request = malformed or invalid request [OK]

Hint: 400 means client sent bad or incomplete data [OK]

Common Mistakes:

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

2.

Which of the following is the correct way to respond with a 400 Bad Request status in a REST API using HTTP headers?

easy

A. HTTP/1.1 200 OK

B. HTTP/1.1 500 Internal Server Error

C. HTTP/1.1 400 Bad Request

D. HTTP/1.1 404 Not Found

Solution

1. Step 1: Recall HTTP status line format

   The status line starts with HTTP version, then status code and reason phrase.

2. Step 2: Match status code to 400 Bad Request

   The correct status line for 400 Bad Request is "HTTP/1.1 400 Bad Request".

3. Final Answer:

   HTTP/1.1 400 Bad Request -> Option C

4. Quick Check:

   Status line for 400 = HTTP/1.1 400 Bad Request [OK]

Hint: 400 status line always includes '400 Bad Request' phrase [OK]

Common Mistakes:

• Using 200 OK for error responses
• Confusing 400 with 500 server error
• Using 404 Not Found for bad requests

3.

Consider this REST API response snippet:

{
  "error": "Invalid JSON format",
  "status": 400
}

What does this response tell the client?

medium

A. The client sent a request with invalid JSON data.

B. The server successfully processed the request.

C. The requested resource was not found.

D. The server is down and cannot respond.

Solution

1. Step 1: Analyze the error message and status code

   The error says "Invalid JSON format" and status is 400, indicating a bad request.

2. Step 2: Interpret the meaning for the client

   The client sent JSON data that the server could not parse, so the request is invalid.

3. Final Answer:

   The client sent a request with invalid JSON data. -> Option A

4. Quick Check:

   400 + invalid JSON = client sent bad data [OK]

Hint: Error message + 400 means client sent bad data [OK]

Common Mistakes:

• Thinking 400 means server error
• Assuming resource not found
• Ignoring the error message details

4.

Given this Python Flask code snippet for a REST API endpoint:

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

@app.route('/submit', methods=['POST'])
def submit():
    data = request.get_json()
    if not data or 'name' not in data:
        return jsonify({'error': 'Missing name field'}), 400
    return jsonify({'message': f"Hello, {data['name']}!"})

What is the likely cause of a 400 Bad Request response?

medium

A. The server returned a success message.

B. The client sent a POST request without JSON body or missing 'name' key.

C. The client used GET method instead of POST.

D. The server crashed due to a syntax error.

Solution

1. Step 1: Check the condition triggering 400 response

   The code returns 400 if JSON data is missing or 'name' key is absent.

2. Step 2: Understand when this happens

   If client sends no JSON or JSON without 'name', server responds with 400 Bad Request.

3. Final Answer:

   The client sent a POST request without JSON body or missing 'name' key. -> Option B

4. Quick Check:

   Missing JSON or 'name' key triggers 400 [OK]

Hint: 400 occurs if required JSON field is missing [OK]

Common Mistakes:

• Assuming server crashed
• Confusing HTTP methods
• Thinking 400 means success

5.

You are designing a REST API that requires a JSON payload with a username and age. Which of these is the best way to respond with a 400 Bad Request when the client sends invalid data?

1. Return 400 with a message explaining the missing or invalid fields.
2. Return 200 OK with an error message in the body.
3. Return 500 Internal Server Error.
4. Ignore the error and process the request anyway.

hard

A. Option 2: Return 200 OK with an error message in the body.

B. Option 4: Ignore the error and process the request anyway.

C. Option 3: Return 500 Internal Server Error.

D. Option 1: Return 400 with a message explaining the missing or invalid fields.

Solution

1. Step 1: Understand proper use of HTTP status codes

   400 Bad Request is used to indicate client errors like invalid or missing data.

2. Step 2: Evaluate each option

   Option 1 correctly uses 400 with clear error message; others misuse status codes or ignore errors.

3. Final Answer:

   Option 1: Return 400 with a message explaining the missing or invalid fields. -> Option D

4. Quick Check:

   Use 400 + clear message for client errors [OK]

Hint: Use 400 with clear error message for invalid client data [OK]

Common Mistakes:

• Returning 200 OK for errors
• Using 500 for client mistakes
• Ignoring validation errors