400 Bad Request in Rest API - Time & Space Complexity

Time Complexity: 400 Bad Request

O(n)

Understanding Time Complexity

When a server returns a 400 Bad Request error, it means the request sent by the client is not understood or is malformed.

We want to understand how the server's processing time changes as the size or complexity of the bad request grows.

Scenario Under Consideration

Analyze the time complexity of this simple request validation process.

// Pseudocode for request validation
function validateRequest(request) {
  if (!request.headers || !request.body) {
    return 400; // Bad Request
  }
  for (let field of requiredFields) {
    if (!request.body.hasOwnProperty(field)) {
      return 400; // Bad Request
    }
  }
  return 200; // OK
}
    

This code checks if the request has required headers and body fields, returning 400 if something is missing.

Identify Repeating Operations

Look for loops or repeated checks that affect time.

• Primary operation: Loop over required fields in the request body.
• How many times: Once for each required field.

How Execution Grows With Input

The time to validate grows as the number of required fields increases.

Input Size (n)	Approx. Operations
10	10 checks
100	100 checks
1000	1000 checks

Pattern observation: The time grows directly with the number of fields to check.

Final Time Complexity

Time Complexity: O(n)

This means the time to detect a bad request grows linearly with the number of required fields checked.

Common Mistake

[X] Wrong: "The 400 Bad Request check is always constant time because it just returns an error."

[OK] Correct: The server must check each required field, so the time depends on how many fields it verifies before deciding the request is bad.

Interview Connect

Understanding how validation scales helps you write efficient APIs and shows you can reason about server performance in real projects.

Self-Check

"What if the validation also checked nested objects inside the request body? How would the time complexity change?"

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