Request validation in Flask - Step-by-Step Execution

Concept Flow - Request validation

Client sends request

↓

Flask receives request

↓

Extract data from request

↓

Validate data format and required fields

↓

Process request

↓

Send success response

↓

End

The server receives a request, extracts data, checks if it meets rules, then processes or returns an error.

Execution Sample

Flask

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

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

This Flask route checks if the JSON request has a 'name' field and returns an error if missing.

Execution Table

Step	Action	Data Extracted	Validation Result	Response
1	Receive POST request with JSON {'name': 'Alice'}	{'name': 'Alice'}	Valid - 'name' present	200 OK, {'message': 'Hello, Alice!'}
2	Receive POST request with JSON {}	{}	Invalid - 'name' missing	400 Bad Request, {'error': 'Name is required'}
3	Receive POST request with no JSON	None	Invalid - no data	400 Bad Request, {'error': 'Name is required'}

💡 Request processing stops after validation passes or fails, returning appropriate response.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
data	None	{'name': 'Alice'}	{}	None
Validation Result	None	Valid	Invalid	Invalid
Response	None	{'message': 'Hello, Alice!'}	{'error': 'Name is required'}	{'error': 'Name is required'}

Key Moments - 2 Insights

Why does the validation fail when the request has no JSON data?

Because 'data' is None, so the condition 'not data' is True, triggering the error response as shown in execution_table row 3.

What happens if the 'name' field is missing in the JSON?

The validation checks 'name' in data and finds it missing, so it returns the error response as in execution_table row 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the response when the JSON contains {'name': 'Alice'}?

A 400 Bad Request with error 'Name is required'

B 500 Internal Server Error

C 200 OK with message 'Hello, Alice!'

D No response sent

💡 Hint

Check execution_table row 1 under Response column.

At which step does the validation detect missing 'name' in the request?

A Step 2

B Step 1

C Step 3

D Validation never detects missing 'name'

💡 Hint

Look at execution_table row 2 Validation Result.

If the code did not check 'not data', what would happen when no JSON is sent?

A It would return a success message

B It would raise an error when accessing data['name']

C It would return an empty JSON response

D It would ignore the request

💡 Hint

Refer to variable_tracker for 'data' being None in step 3 and the code line accessing data['name'].

Concept Snapshot

Request validation in Flask:
- Extract JSON with request.json
- Check if data exists and required fields present
- Return error response if validation fails
- Otherwise, process and respond
- Use status codes (e.g., 400 for bad request)
- Helps ensure server gets expected data

Full Transcript

In Flask, when a client sends a request, the server extracts the JSON data using request.json. The code then checks if the data exists and if required fields like 'name' are present. If the data is missing or the 'name' field is absent, the server returns a 400 Bad Request response with an error message. If validation passes, it processes the request and returns a success message. This flow ensures the server only processes valid requests and helps avoid errors from missing or malformed data.

Practice

1. What is the main purpose of request validation in a Flask application?

easy

A. To store user data permanently

B. To check incoming data for correctness and safety

C. To style the HTML forms automatically

D. To speed up the server response time

Solution

1. Step 1: Understand what request validation means

   Request validation means checking the data sent by users to make sure it is correct and safe to use.

2. Step 2: Identify the main goal of validation

   The main goal is to prevent bad or harmful data from causing errors or security problems.

3. Final Answer:

   To check incoming data for correctness and safety -> Option B

4. Quick Check:

   Request validation = check data safety [OK]

Hint: Validation means checking data is safe and correct [OK]

Common Mistakes:

• Thinking validation speeds up the server
• Confusing validation with styling
• Assuming validation stores data

2. Which of the following is the correct way to access JSON data from a Flask request object?

easy

A. request.get_json()

B. request.json_data

C. request.json()

D. request.data.json

Solution

1. Step 1: Recall Flask's method to get JSON data

   Flask provides the method get_json() to parse JSON from the request body.

2. Step 2: Check each option for correctness

   request.json() uses parentheses but json is a property, not a method. request.json_data and D are not valid Flask attributes.

3. Final Answer:

   request.get_json() -> Option A

4. Quick Check:

   Use get_json() to read JSON data [OK]

Hint: Use request.get_json() to read JSON in Flask [OK]

Common Mistakes:

• Calling request.json as a function
• Using non-existent attributes like json_data
• Trying to access JSON via request.data.json

3. Given this Flask route code, what will be the output if the JSON request body is {"age": 17}?

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

@app.route('/check', methods=['POST'])
def check_age():
    data = request.get_json()
    if data and data.get('age', 0) >= 18:
        return jsonify({'status': 'allowed'})
    else:
        return jsonify({'status': 'denied'})

medium

A. {"status": "allowed"}

B. Empty response

C. 500 Internal Server Error

D. {"status": "denied"}

Solution

1. Step 1: Analyze the JSON input and condition

   The input JSON has "age": 17. The code checks if age is 18 or more.

2. Step 2: Determine which branch runs

   Since 17 is less than 18, the else branch runs, returning {'status': 'denied'}.

3. Final Answer:

   {"status": "denied"} -> Option D

4. Quick Check:

   Age 17 < 18 = denied [OK]

Hint: Check if age >= 18 to allow, else deny [OK]

Common Mistakes:

• Assuming 17 is allowed
• Expecting server error for valid JSON
• Thinking response is empty

4. What is wrong with this Flask code snippet for validating a required 'username' field in JSON?

data = request.get_json()
if 'username' in data:
    return 'Username received'
else:
    return 'Missing username', 400

medium

A. It does not check if data is None before accessing

B. It uses wrong HTTP status code for error

C. It should use request.json instead of get_json()

D. It should return JSON response, not plain text

Solution

1. Step 1: Understand get_json() behavior

   request.get_json() can return None if no JSON is sent or invalid JSON.

2. Step 2: Identify the error in code

   The code accesses 'username' in data without checking if data is None, causing a crash if data is None.

3. Final Answer:

   It does not check if data is None before accessing -> Option A

4. Quick Check:

   Check data is not None before key access [OK]

Hint: Always check if get_json() returned data before use [OK]

Common Mistakes:

• Ignoring None check on JSON data
• Confusing status codes
• Thinking request.json is better than get_json()
• Assuming plain text is always wrong

5. You want to validate a JSON request in Flask to ensure it has a 'name' string and an 'age' integer above 0. Which approach best combines validation and clear error messages?

hard

A. Manually check keys and types, return custom error messages on failure

B. Use request.get_json() and assume data is always correct

C. Use a library like marshmallow to define a schema and validate automatically

D. Skip validation and handle errors later in the code

Solution

1. Step 1: Consider manual validation drawbacks

   Manual checks can be error-prone and verbose, making code hard to maintain.

2. Step 2: Understand benefits of marshmallow

   Marshmallow lets you define clear schemas and automatically validates input, returning helpful error messages.

3. Step 3: Evaluate other options

   Assuming data is correct or skipping validation risks bugs and security issues.

4. Final Answer:

   Use a library like marshmallow to define a schema and validate automatically -> Option C

5. Quick Check:

   Use marshmallow for clear, automatic validation [OK]

Hint: Use marshmallow for easy, clear validation [OK]

Common Mistakes:

• Assuming data is always valid
• Writing complex manual checks
• Ignoring validation completely