HTTP status codes for APIs in Flask - Performance & Optimization

Performance: HTTP status codes for APIs

MEDIUM IMPACT

This concept affects how quickly clients understand API responses and handle errors, impacting perceived responsiveness and user experience.

Returning API responses with appropriate HTTP status codes

Flask

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

@app.route('/data')
def data():
    # Returns 404 status code on error
    return jsonify({'error': 'Not found'}), 404

Clients can quickly detect errors from status code without parsing body, reducing unnecessary processing and retries.

📈 Performance GainImproves input responsiveness (INP) by reducing client-side delay and network overhead.

Returning API responses with appropriate HTTP status codes

Flask

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

@app.route('/data')
def data():
    # Always returns 200 OK even on error
    return jsonify({'error': 'Not found', 'data': None}), 200

Always returning 200 OK forces clients to parse response body to detect errors, causing extra processing and possible retries.

📉 Performance CostIncreases client processing time and network retries, leading to slower interaction (higher INP).

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Always 200 OK with error in body	N/A	N/A	N/A	[X] Bad
Correct HTTP status codes (e.g., 404, 500)	N/A	N/A	N/A	[OK] Good

Rendering Pipeline

HTTP status codes are part of the network response and do not directly affect browser rendering stages but influence client-side logic and perceived responsiveness.

→Network

→Client Processing

⚠️ BottleneckClient Processing when status codes are misused, causing extra parsing and retries.

Core Web Vital Affected

INP

This concept affects how quickly clients understand API responses and handle errors, impacting perceived responsiveness and user experience.

Optimization Tips

1Always use appropriate HTTP status codes for API responses.

2Avoid returning 200 OK for error conditions to prevent extra client processing.

3Correct status codes improve client responsiveness and reduce network overhead.

Performance Quiz - 3 Questions

Why is it better to return a 404 status code instead of a 200 with an error message in the body?

A It reduces the size of the response body.

B Clients can detect errors faster and avoid unnecessary processing.

C It improves the visual layout of the page.

D It increases the number of DOM nodes.

DevTools: Network

How to check: Open DevTools, go to Network tab, make an API request, and inspect the status code column for the response.

What to look for: Check that error responses return appropriate HTTP status codes (e.g., 404, 500) instead of always 200.

Practice

1. What HTTP status code should a Flask API return when a request is successful and data is sent back?

easy

A. 200 OK

B. 404 Not Found

C. 500 Internal Server Error

D. 201 Created

Solution

1. Step 1: Understand the meaning of status codes

   200 means the request was successful and the server is returning the requested data.

2. Step 2: Match the code to the scenario

   Since the request succeeded and data is returned, 200 OK is the correct code.

3. Final Answer:

   200 OK -> Option A

4. Quick Check:

   Success response = 200 OK [OK]

Hint: Success with data? Use 200 OK [OK]

Common Mistakes:

• Confusing 201 Created with simple success
• Using 404 when resource exists
• Using 500 for client errors

2. Which of the following is the correct way to return a JSON response with a 201 status code in Flask?

easy

A. return data, code=201

B. return data, status=201

C. return json.dumps(data), 201

D. return jsonify(data), 201

Solution

1. Step 1: Recall Flask's return syntax for JSON and status

   Flask uses jsonify() to convert data to JSON and returns a tuple (response, status_code).

2. Step 2: Identify the correct syntax

   return jsonify(data), 201 correctly uses jsonify(data), 201 to return JSON with status 201.

3. Final Answer:

   return jsonify(data), 201 -> Option D

4. Quick Check:

   Flask JSON + status = jsonify(data), 201 [OK]

Hint: Use jsonify() and return tuple (data, status) [OK]

Common Mistakes:

• Using json.dumps without jsonify
• Incorrect keyword arguments like status= or code=
• Returning raw data without JSON conversion

3. Consider this Flask route code:

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

@app.route('/item/')
def get_item(id):
    items = {1: 'apple', 2: 'banana'}
    if id in items:
        return jsonify({'item': items[id]}), 200
    else:
        return jsonify({'error': 'Item not found'}), 404

What HTTP status code will be returned when accessing /item/3?

medium

A. 200

B. 404

C. 500

D. 201

Solution

1. Step 1: Check if id 3 exists in items dictionary

   Items only have keys 1 and 2, so 3 is not found.

2. Step 2: Identify the returned status code for missing item

   The else block returns 404 Not Found with an error message.

3. Final Answer:

   404 -> Option B

4. Quick Check:

   Missing resource = 404 Not Found [OK]

Hint: Missing item? Return 404 Not Found [OK]

Common Mistakes:

• Assuming 200 even if item missing
• Confusing 404 with 500 server error
• Returning 201 for missing resource

4. This Flask API code is intended to return a 400 Bad Request if the 'name' field is missing in JSON input:

@app.route('/add', methods=['POST'])
def add():
    data = request.get_json()
    if 'name' not in data:
        return {'error': 'Name required'}, 400
    return {'message': 'Added'}, 201

What is the main problem with this code?

medium

A. It returns a dict instead of using jsonify

B. It returns 201 instead of 200 on success

C. It does not import request from flask

D. It uses wrong status code for missing name

Solution

1. Step 1: Check imports needed for request

   The code uses request.get_json() but does not show importing request from flask.

2. Step 2: Identify the error caused by missing import

   Without importing request, the code will raise a NameError at runtime.

3. Final Answer:

   It does not import request from flask -> Option C

4. Quick Check:

   Missing import request causes error [OK]

Hint: Always import request to use request.get_json() [OK]

Common Mistakes:

• Ignoring missing imports causing runtime errors
• Thinking returning dict is invalid (Flask accepts dict)
• Confusing 201 Created as wrong success code here

5. You want to create a Flask API endpoint that creates a new user. If the username already exists, return 400 Bad Request. If creation succeeds, return 201 Created with the new user's ID. Which code snippet correctly implements this behavior?

hard

A. def create_user():
data = request.get_json()
if data['username'] in users:
return {'error': 'User exists'}, 400
new_id = len(users) + 1
users[new_id] = data['username']
return {'id': new_id}, 201

B. def create_user():
data = request.get_json()
if data['username'] in users:
return {'error': 'User exists'}, 404
new_id = len(users) + 1
users[new_id] = data['username']
return {'id': new_id}, 200

C. def create_user():
data = request.get_json()
if data['username'] in users:
return {'error': 'User exists'}, 500
new_id = len(users) + 1
users[new_id] = data['username']
return {'id': new_id}, 201

D. def create_user():
data = request.get_json()
if data['username'] in users:
return {'error': 'User exists'}, 201
new_id = len(users) + 1
users[new_id] = data['username']
return {'id': new_id}, 400

Solution

1. Step 1: Check status code for existing user

   400 Bad Request is correct when username already exists, indicating client error.

2. Step 2: Check status code for successful creation

   201 Created is the correct code for successful resource creation.

3. Step 3: Verify code matches these codes

   def create_user(): data = request.get_json() if data['username'] in users: return {'error': 'User exists'}, 400 new_id = len(users) + 1 users[new_id] = data['username'] return {'id': new_id}, 201 returns 400 for existing user and 201 for success, matching requirements.

4. Final Answer:

   Option A code snippet -> Option A

5. Quick Check:

   Existing user = 400, success = 201 [OK]

Hint: Use 400 for bad input, 201 for successful creation [OK]

Common Mistakes:

• Using 404 or 500 for existing user error
• Returning 200 instead of 201 on creation
• Mixing up success and error codes