400 Bad Request in Rest API - Step-by-Step Execution

Concept Flow - 400 Bad Request

Client sends HTTP request

↓

Server receives request

↓

Server checks request syntax

↓

Process request

↓

Send response

↓

End

The server checks the client's request. If the request is malformed or invalid, it responds with 400 Bad Request and stops processing.

Execution Sample

Rest API

POST /api/data HTTP/1.1
Host: example.com
Content-Type: application/json

{"name": "John", "age": }

Client sends a POST request with invalid JSON (missing age value), causing a 400 Bad Request response.

Execution Table

Step	Action	Request Content	Validation Result	Server Response
1	Receive request	{"name": "John", "age": }	Syntax check started	None
2	Parse JSON body	{"name": "John", "age": }	Invalid JSON syntax	Prepare 400 Bad Request
3	Send response	N/A	N/A	HTTP 400 Bad Request with error message
4	End	N/A	N/A	Connection closed or waiting for new request

💡 Request JSON is invalid, so server stops processing and returns 400 Bad Request.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
request_content	N/A	{"name": "John", "age": }	{"name": "John", "age": }	N/A	N/A
validation_result	N/A	Pending	Invalid JSON syntax	N/A	N/A
server_response	N/A	None	Prepare 400 Bad Request	Sent 400 Bad Request	Completed

Key Moments - 3 Insights

Why does the server respond with 400 Bad Request instead of processing the data?

Because the request content is malformed (invalid JSON), the server detects this during syntax validation (see execution_table step 2) and stops further processing to avoid errors.

Is 400 Bad Request caused by server problems or client mistakes?

It is caused by client mistakes, such as sending malformed requests. The server is working correctly but refuses to process bad input (see execution_table steps 1-3).

What happens after the server sends the 400 Bad Request response?

The server ends the current request handling and waits for new requests or closes the connection (see execution_table step 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the validation result at step 2?

A Valid JSON

B Invalid JSON syntax

C Pending validation

D Server error

💡 Hint

Check the 'Validation Result' column at step 2 in the execution_table.

At which step does the server send the 400 Bad Request response?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look at the 'Server Response' column to find when the response is sent.

If the JSON was valid, how would the 'Validation Result' change at step 2?

A It would be 'Invalid JSON syntax'

B It would be 'Preparing 400 Bad Request'

C It would be 'Valid JSON'

D It would be 'Connection closed'

💡 Hint

Refer to the 'Validation Result' column in the execution_table and imagine a valid request.

Concept Snapshot

400 Bad Request:
- Means client sent a malformed or invalid request
- Server checks request syntax before processing
- If invalid, server responds with HTTP 400 status
- Client must fix request format to succeed
- Common causes: bad JSON, missing fields, wrong headers

Full Transcript

When a client sends an HTTP request, the server first checks if the request is valid. If the request has bad syntax, like invalid JSON, the server stops processing and sends back a 400 Bad Request response. This tells the client that the request was wrong and needs fixing. The server does not process bad requests to avoid errors. After sending the 400 response, the server ends the current request handling and waits for new requests. This error is caused by client mistakes, not server problems.

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