400 Bad Request in Rest API - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the HTTP status code returned?

A client sends a malformed JSON payload to a REST API endpoint expecting JSON data. The server detects the invalid JSON format. What HTTP status code will the server most likely return?

A 200 OK

B 500 Internal Server Error

C 404 Not Found

D 400 Bad Request

💡 Hint

Think about which status code means the client sent something wrong.

The 400 Bad Request status code means the server cannot process the request due to client error, such as malformed JSON.

🧠 Conceptual

intermediate

Cause of 400 Bad Request in REST APIs

Which of the following is the most common cause for a REST API to respond with a 400 Bad Request status?

A The client sent invalid or malformed data

B The server encountered an unexpected error

C The requested resource does not exist

D The client is not authorized to access the resource

💡 Hint

400 means the client made a mistake in the request format or content.

400 Bad Request indicates the client sent invalid data or the request could not be understood by the server.

❓ Predict Output

advanced

Output of server response with missing required field

A REST API expects a JSON body with a required field 'username'. The client sends a JSON without 'username'. The server validates and returns a response. What is the likely HTTP status code and message?

Rest API

POST /api/users HTTP/1.1
Content-Type: application/json

{"email": "[e-mail]"}

A 500 Internal Server Error

B 400 Bad Request with error message about missing 'username'

C 404 Not Found

D 201 Created with user details

💡 Hint

Missing required fields usually cause client errors.

The server returns 400 Bad Request because the client did not provide a required field, making the request invalid.

🔧 Debug

advanced

Identify the cause of 400 Bad Request in this API call

A client sends this HTTP request to a REST API but receives a 400 Bad Request response. What is the most likely cause?

Rest API

POST /api/login HTTP/1.1
Content-Type: application/json

{"username": "user1", "password": "12345"}

A Password should be a string, not a number

B Missing Authorization header

C Incorrect HTTP method used

D Server is down

💡 Hint

Check the data types expected by the API.

The API expects the password as a string, but the client sent a number, causing a validation error and 400 Bad Request.

🚀 Application

expert

How to handle 400 Bad Request in client code

You are writing client code to call a REST API. If the server responds with 400 Bad Request, what is the best way to handle it?

A Ignore the error and continue

B Retry the request immediately without changes

C Log the error and prompt the user to correct the input data

D Restart the client application

💡 Hint

400 means the client sent bad data, so fix the data before retrying.

When receiving 400 Bad Request, the client should inform the user to fix the input data before retrying.

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