API error handling in Flask

Introduction

API error handling helps your app tell users when something goes wrong in a clear way. It stops crashes and gives useful messages.

When a user sends wrong data to your API.

When a requested item is not found in the database.

When the server has an internal problem.

When a user tries to access a resource without permission.

When the API endpoint does not exist.

Syntax

Flask

from flask import Flask, jsonify

app = Flask(__name__)

@app.errorhandler(404)
def not_found(error):
    return jsonify({'error': 'Not found'}), 404

@app.errorhandler(500)
def internal_error(error):
    return jsonify({'error': 'Server error'}), 500

Use @app.errorhandler(status_code) to catch specific HTTP errors.

Return a JSON response with an error message and the correct HTTP status code.

Examples

This handles 400 errors when the client sends bad data.

Flask

from flask import Flask, jsonify

app = Flask(__name__)

@app.errorhandler(400)
def bad_request(error):
    return jsonify({'error': 'Bad request'}), 400

This handles 403 errors when a user tries to access something they shouldn't.

Flask

from flask import Flask, jsonify

app = Flask(__name__)

@app.errorhandler(403)
def forbidden(error):
    return jsonify({'error': 'Forbidden access'}), 403

This catches all other errors not specifically handled and returns a 500 error.

Flask

from flask import Flask, jsonify

app = Flask(__name__)

@app.errorhandler(Exception)
def handle_exception(error):
    return jsonify({'error': 'Something went wrong'}), 500

Sample Program

This simple API returns an item by id. If the id is missing, it returns a 404 error with a message. It also handles general 404 and 500 errors gracefully.

Flask

from flask import Flask, jsonify, request

app = Flask(__name__)

items = {'1': 'apple', '2': 'banana'}

@app.route('/item/<id>')
def get_item(id):
    if id not in items:
        return jsonify({'error': 'Item not found'}), 404
    return jsonify({'item': items[id]})

@app.errorhandler(404)
def not_found(error):
    return jsonify({'error': 'Not found'}), 404

@app.errorhandler(500)
def internal_error(error):
    return jsonify({'error': 'Server error'}), 500

if __name__ == '__main__':
    app.run(debug=True)

Important Notes

Always return JSON for API errors so clients can understand the problem easily.

Use proper HTTP status codes to match the error type.

Test your error handlers by calling routes that cause errors.

Summary

API error handling helps your app respond clearly when things go wrong.

Use @app.errorhandler to catch errors and return JSON messages.

Always include the right HTTP status code with your error response.

Practice

1. What is the main purpose of using @app.errorhandler in a Flask API?

easy

A. To start the Flask application

B. To define new API routes

C. To catch specific errors and return custom responses

D. To connect to a database

Solution

1. Step 1: Understand the role of @app.errorhandler

   This decorator is used to catch errors that happen during API requests.

2. Step 2: Recognize its use for custom responses

   It allows you to send back clear messages and proper HTTP status codes when errors occur.

3. Final Answer:

   To catch specific errors and return custom responses -> Option C

4. Quick Check:

   @app.errorhandler catches errors [OK]

Hint: Remember: errorhandler catches errors to customize responses [OK]

Common Mistakes:

• Thinking it defines routes
• Confusing it with app.run()
• Assuming it manages database connections

2. Which of the following is the correct syntax to handle a 404 error in Flask?

easy

A. @app.errorhandler(404)
def not_found(error):
return 'Not Found', 404

B. @app.route(404)
def not_found():
return 'Not Found'

C. @app.errorhandler('404')
def not_found(error):
return 'Not Found', 404

D. @app.errorhandler(404)
def not_found():
return 'Not Found'

Solution

1. Step 1: Identify correct decorator usage

   The @app.errorhandler decorator takes an integer status code like 404 without quotes.

2. Step 2: Check function signature and return

   The handler function should accept an error argument and return a response with the status code.

3. Final Answer:

   @app.errorhandler(404)\ndef not_found(error):\n return 'Not Found', 404 -> Option A

4. Quick Check:

   Correct decorator and function signature = @app.errorhandler(404) def not_found(error): return 'Not Found', 404 [OK]

Hint: Use integer status codes without quotes in errorhandler [OK]

Common Mistakes:

• Using @app.route instead of @app.errorhandler
• Passing status code as string '404'
• Omitting the error parameter in handler function

3. Given this Flask error handler code:

from flask import abort, jsonify
@app.errorhandler(400)
def bad_request(error):
    return jsonify({'error': 'Bad Request'}), 400

@app.route('/test')
def test():
    abort(400)

What will be the JSON response and status code when accessing /test?

medium

A. {"error": "Bad Request"} with status code 400

B. Plain text 'Bad Request' with status code 200

C. Default Flask 400 error page with status code 400

D. Empty response with status code 400

Solution

1. Step 1: Understand abort triggers error handler

   The abort(400) call triggers the 400 error handler defined by @app.errorhandler(400).

2. Step 2: Check handler return value

   The handler returns a JSON dictionary with the error message and status code 400.

3. Final Answer:

   {"error": "Bad Request"} with status code 400 -> Option A

4. Quick Check:

   abort triggers handler response JSON + 400 [OK]

Hint: abort(code) triggers matching errorhandler response [OK]

Common Mistakes:

• Expecting plain text instead of JSON
• Assuming default Flask error page shows
• Missing status code in response

4. What is wrong with this Flask error handler code?

@app.errorhandler(500)
def internal_error():
    return {'error': 'Server Error'}, 500

medium

A. The decorator should be @app.route, not @app.errorhandler

B. The status code 500 should be a string '500'

C. The return value must be a string, not a dictionary

D. The handler function must accept an error parameter

Solution

1. Step 1: Check function signature for error handlers

   Error handler functions must accept one parameter for the error object.

2. Step 2: Identify missing parameter

   The function internal_error has no parameters, so Flask will raise a TypeError.

3. Final Answer:

   The handler function must accept an error parameter -> Option D

4. Quick Check:

   Error handler functions need error argument [OK]

Hint: Error handlers always need an error parameter [OK]

Common Mistakes:

• Omitting the error parameter
• Using string status codes
• Confusing errorhandler with route decorator

5. You want to create a Flask API error handler that returns a JSON response with a custom message and the correct HTTP status code for any KeyError raised in your routes. Which of the following is the best way to implement this?

hard

A. @app.errorhandler(400)
def handle_key_error(error):
return {'error': 'Missing key in request'}, 400

B. @app.errorhandler(KeyError)
def handle_key_error(error):
return {'error': 'Missing key in request'}, 400

C. @app.route('/error')
def handle_key_error():
return {'error': 'Missing key in request'}, 400

D. @app.errorhandler(Exception)
def handle_key_error(error):
return {'error': 'Missing key in request'}, 400

Solution

1. Step 1: Use exception class in errorhandler

   To catch a specific Python error like KeyError, use it directly in @app.errorhandler(KeyError).

2. Step 2: Return JSON with appropriate status code

   Return a JSON message and HTTP 400 (bad request) status code to indicate client error.

3. Final Answer:

   @app.errorhandler(KeyError)\ndef handle_key_error(error):\n return {'error': 'Missing key in request'}, 400 -> Option B

4. Quick Check:

   Use exception class in errorhandler for specific errors [OK]

Hint: Use exception class in errorhandler to catch specific errors [OK]

Common Mistakes:

• Using status code instead of exception class
• Defining error handler as a route
• Catching all exceptions instead of specific one