Validation error responses in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a validation error response in FastAPI?

It is the message FastAPI sends back when the data sent by the user does not match the expected format or rules. It helps the user know what went wrong.

beginner

How does FastAPI automatically handle validation errors?

FastAPI uses Pydantic models to check data. If data is wrong, it returns a clear JSON error response with details about which fields failed and why.

beginner

What HTTP status code does FastAPI use for validation errors by default?

FastAPI returns status code 422 Unprocessable Entity when validation fails.

intermediate

How can you customize validation error responses in FastAPI?

You can write an exception handler for RequestValidationError to change the error message or format before sending it back to the user.

beginner

What information does FastAPI include in its validation error response?

It includes the location of the error (like body or query), the field name, the error message, and the type of error.

What status code does FastAPI return for validation errors?

A 404 Not Found

B 422 Unprocessable Entity

C 500 Internal Server Error

D 400 Bad Request

FastAPI returns 422 when the input data fails validation checks.

Which library does FastAPI use to validate data models?

A Marshmallow

B Cerberus

C Pydantic

D Voluptuous

FastAPI uses Pydantic to define and validate data models.

How can you change the default validation error response in FastAPI?

A By writing a custom exception handler for RequestValidationError

B By changing the HTTP status code in the route decorator

C By editing the FastAPI source code

D By using a different web framework

Custom exception handlers let you modify how validation errors are returned.

What key information is NOT included in FastAPI's validation error response?

A Location of the error (body, query, etc.)

B Error message explaining the problem

C Field name where error occurred

D User's IP address

User's IP address is not part of the validation error details.

If a user sends a string instead of an integer in a request body, what will FastAPI do?

A Return a validation error response with details

B Accept the string without error

C Crash the server

D Ignore the field silently

FastAPI will return a validation error explaining the type mismatch.

Explain how FastAPI handles validation errors and what the user sees when data is invalid.

Think about what happens when input data does not match the expected model.

Describe how you can customize the validation error responses in FastAPI.

Consider how FastAPI lets you catch and change errors before sending them.

Practice

1. What does FastAPI do when a request body fails validation by Pydantic models?

easy

A. It logs the error but returns a success response.

B. It automatically returns a detailed validation error response to the client.

C. It crashes the server with an unhandled exception.

D. It ignores the error and processes the request anyway.

Solution

1. Step 1: Understand FastAPI's validation mechanism

   FastAPI uses Pydantic models to validate incoming request data automatically.

2. Step 2: Observe default error handling

   If validation fails, FastAPI returns a JSON response describing the validation errors without crashing.

3. Final Answer:

   It automatically returns a detailed validation error response to the client. -> Option B

4. Quick Check:

   Validation failure triggers automatic error response = D [OK]

Hint: Validation errors trigger automatic JSON error responses [OK]

Common Mistakes:

• Thinking FastAPI crashes on validation errors
• Assuming errors are ignored silently
• Believing errors are only logged without response

2. Which import is required to customize validation error responses in FastAPI?

easy

A. from fastapi.responses import ValidationErrorResponse

B. from fastapi import RequestValidationError

C. from pydantic import ValidationError

D. from fastapi.exceptions import RequestValidationError

Solution

1. Step 1: Identify the correct module for RequestValidationError

   FastAPI's RequestValidationError is located in fastapi.exceptions, not directly in fastapi.

2. Step 2: Check other options

   Pydantic's ValidationError is different and not used for FastAPI's error handler. No ValidationErrorResponse class exists.

3. Final Answer:

   from fastapi.exceptions import RequestValidationError -> Option D

4. Quick Check:

   RequestValidationError import is from fastapi.exceptions = A [OK]

Hint: RequestValidationError is in fastapi.exceptions module [OK]

Common Mistakes:

• Importing RequestValidationError directly from fastapi
• Confusing Pydantic's ValidationError with FastAPI's
• Assuming a ValidationErrorResponse class exists

3. Given this FastAPI code snippet, what will be the response if the client sends {"age": "twenty"}?

from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class User(BaseModel):
    age: int

@app.post("/user")
async def create_user(user: User):
    return {"age": user.age}

medium

A. 422 Unprocessable Entity with validation error details

B. {"age": "twenty"}

C. 200 OK with age set to 0

D. 500 Internal Server Error

Solution

1. Step 1: Analyze the Pydantic model validation

   The User model expects an integer for age, but the client sends a string "twenty" which cannot be converted to int.

2. Step 2: Understand FastAPI's response to invalid data

   FastAPI automatically returns a 422 status with a JSON body describing the validation error.

3. Final Answer:

   422 Unprocessable Entity with validation error details -> Option A

4. Quick Check:

   Invalid type triggers 422 validation error = A [OK]

Hint: Invalid data types cause 422 validation error response [OK]

Common Mistakes:

• Expecting the server to accept wrong types silently
• Assuming a 500 error instead of 422
• Thinking the response echoes invalid input

4. Identify the error in this FastAPI code that tries to customize validation error responses:

from fastapi import FastAPI, Request
from fastapi.exceptions import RequestValidationError
from fastapi.responses import JSONResponse

app = FastAPI()

@app.exception_handler(RequestValidationError)
async def validation_exception_handler(request: Request, exc: RequestValidationError):
    return JSONResponse(status_code=400, content={"error": exc.errors()})

medium

A. The status_code 400 is incorrect; it should be 422 for validation errors.

B. The exception handler must return a Response, not JSONResponse.

C. The exc.errors() method does not exist on RequestValidationError.

D. The handler function must not be async.

Solution

1. Step 1: Check the correct HTTP status code for validation errors

   FastAPI uses 422 Unprocessable Entity for validation errors by default, not 400 Bad Request.

2. Step 2: Verify other parts of the handler

   Returning JSONResponse is valid, exc.errors() is a valid method, and async handlers are allowed.

3. Final Answer:

   The status_code 400 is incorrect; it should be 422 for validation errors. -> Option A

4. Quick Check:

   Validation errors use 422 status code, not 400 = B [OK]

Hint: Validation errors respond with 422 status code, not 400 [OK]

Common Mistakes:

• Using 400 instead of 422 status code
• Thinking exc.errors() is invalid
• Believing async is disallowed in handlers

5. How can you customize FastAPI to return a simpler validation error message like {"detail": "Invalid input"} instead of the default detailed errors?

hard

A. Set a global FastAPI config option to simplify validation errors.

B. Modify the Pydantic model to raise simpler errors automatically.

C. Override the default exception handler for RequestValidationError and return a custom JSONResponse with the simpler message.

D. Use middleware to catch validation errors and replace the response.

Solution

1. Step 1: Understand how to customize validation error responses

   FastAPI allows overriding the exception handler for RequestValidationError to customize error responses.

2. Step 2: Evaluate other options

   Pydantic models do not control error response format, no global config exists for this, and middleware is not the recommended way for validation errors.

3. Final Answer:

   Override the default exception handler for RequestValidationError and return a custom JSONResponse with the simpler message. -> Option C

4. Quick Check:

   Custom handler for RequestValidationError = C [OK]

Hint: Use custom exception handler to simplify validation error messages [OK]

Common Mistakes:

• Trying to change Pydantic model error output
• Looking for global config to simplify errors
• Using middleware instead of exception handlers