Validation error responses in FastAPI - Step-by-Step Execution

Concept Flow - Validation error responses

Client sends request with data

↓

FastAPI receives request

↓

Validate data against Pydantic model

↓

Valid data

↓

Process request

↓

Send success

FastAPI checks incoming data against rules. If data is good, it processes. If not, it sends back a clear error message.

Execution Sample

FastAPI

from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class Item(BaseModel):
    name: str
    price: float

@app.post("/items/")
async def create_item(item: Item):
    return item

This code defines a data model and an endpoint that expects data matching the model. FastAPI validates input automatically.

Execution Table

Step	Action	Input Data	Validation Result	Response Sent
1	Receive POST /items/ with JSON	{"name": "Book", "price": 12.5}	Valid	200 OK with item data
2	Receive POST /items/ with JSON	{"name": "Pen", "price": "cheap"}	Invalid: price not float	422 Unprocessable Entity with error details
3	Receive POST /items/ with JSON	{"price": 5.0}	Invalid: name missing	422 Unprocessable Entity with error details
4	Receive POST /items/ with JSON	{"name": "Notebook", "price": -3}	Valid (negative price allowed)	200 OK with item data
5	Receive POST /items/ with JSON	{"name": 123, "price": 10}	Invalid: name not string	422 Unprocessable Entity with error details
6	Exit	-	-	No more requests

💡 No more requests to process

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
input_data	-	{"name": "Book", "price": 12.5}	{"name": "Pen", "price": "cheap"}	{"price": 5.0}	{"name": "Notebook", "price": -3}	{"name": 123, "price": 10}	-
validation_result	-	Valid	Invalid: price not float	Invalid: name missing	Valid (negative price allowed)	Invalid: name not string	-
response_sent	-	200 OK with item data	422 Unprocessable Entity with error details	422 Unprocessable Entity with error details	200 OK with item data	422 Unprocessable Entity with error details	-

Key Moments - 3 Insights

Why does FastAPI return a 422 error instead of 400 when validation fails?

FastAPI uses 422 Unprocessable Entity to indicate the request format is correct but the data is invalid, as shown in execution_table rows 2, 3, and 5.

What happens if a required field is missing in the input data?

FastAPI detects missing required fields during validation and returns a 422 error with details, as seen in execution_table row 3.

Can validation allow unexpected values like negative numbers?

Yes, unless explicitly restricted, validation accepts values like negative numbers, shown in execution_table row 4 where price is -3 but still valid.

Visual Quiz - 3 Questions

Look at the execution table, what is the validation result at step 2?

A Invalid: name missing

B Valid

C Invalid: price not float

D Valid with warnings

💡 Hint

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

At which step does the input data miss a required field?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look for 'Invalid: name missing' in the 'Validation Result' column.

If the 'price' field was a string 'cheap' at step 5, what would the validation result be?

A Invalid: price not float

B Valid

C Invalid: name missing

D Valid with warnings

💡 Hint

Compare step 2 and step 5 validation results for price field errors.

Concept Snapshot

FastAPI auto-validates request data using Pydantic models.
If data matches model, request proceeds.
If data is invalid or missing fields, FastAPI returns 422 error with details.
Validation errors include field name, error type, and location.
Use this to build reliable APIs that guide users to fix input.

Full Transcript

When a client sends data to a FastAPI endpoint, FastAPI checks the data against the expected Pydantic model. If the data is correct, the endpoint runs and returns the data or result. If the data is wrong, like missing fields or wrong types, FastAPI sends back a 422 error with details about what is wrong. This helps clients fix their requests. For example, if the price should be a number but is a word, FastAPI will say 'price not float'. If a required field like name is missing, it will say so. Negative numbers are allowed unless you add extra rules. This automatic validation makes APIs safer and easier to use.