Custom request validation in FastAPI - Performance & Optimization

Performance: Custom request validation

MEDIUM IMPACT

This affects the server response time and user experience by adding processing before sending responses.

Validating incoming request data in FastAPI

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 {"message": "Item created"}

Using Pydantic models leverages built-in efficient validation and parsing, reducing manual CPU work.

📈 Performance GainFaster validation with less code, non-blocking async response, improves INP

Validating incoming request data in FastAPI

FastAPI

from fastapi import FastAPI, Request
app = FastAPI()

@app.post("/items")
async def create_item(request: Request):
    data = await request.json()
    if 'name' not in data or not isinstance(data['name'], str):
        return {"error": "Invalid name"}
    # manual validation for each field
    if 'price' not in data or not isinstance(data['price'], (float, int)):
        return {"error": "Invalid price"}
    return {"message": "Item created"}

Manual validation requires parsing and checking each field, causing extra CPU work and delaying response.

📉 Performance CostBlocks response for each request due to synchronous manual checks

Performance Comparison

Pattern	CPU Usage	Response Delay	Code Complexity	Verdict
Manual field checks in endpoint	High CPU per request	Delays response by ms to 10s	High, repetitive code	[X] Bad
Pydantic model validation	Low CPU, optimized C code	Minimal delay, async friendly	Low, declarative code	[OK] Good

Rendering Pipeline

Custom validation runs on the server before sending the response, affecting server processing time and thus the time until the browser receives data to render.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing due to synchronous or complex validation logic

Core Web Vital Affected

INP

This affects the server response time and user experience by adding processing before sending responses.

Optimization Tips

1Use Pydantic models for declarative and efficient validation.

2Avoid heavy synchronous computations during validation.

3Check server response times in DevTools Network tab to monitor validation impact.

Performance Quiz - 3 Questions

Which validation method in FastAPI generally leads to faster server response?

A Using Pydantic models for request validation

B Manually parsing and checking JSON fields in the endpoint

C Validating data on the client side only

D Skipping validation entirely

DevTools: Network

How to check: Open DevTools, go to Network tab, send a request to the API endpoint, and check the Time column for server response time.

What to look for: Look for long waiting (TTFB) times indicating slow server validation processing.

Practice

1. What is the main purpose of custom request validation in FastAPI?

easy

A. To handle database connections

B. To speed up the API response time

C. To check and enforce rules on incoming data before processing

D. To automatically generate API documentation

Solution

1. Step 1: Understand the role of validation

   Validation ensures data meets expected rules before using it.

2. Step 2: Identify FastAPI's validation purpose

   FastAPI uses validation to keep data clean and safe, preventing bad data.

3. Final Answer:

   To check and enforce rules on incoming data before processing -> Option C

4. Quick Check:

   Validation = Data rules check [OK]

Hint: Validation means checking data correctness before use [OK]

Common Mistakes:

• Confusing validation with performance optimization
• Thinking validation manages database connections
• Mixing validation with documentation generation

2. Which of the following is the correct way to add a custom validator in a Pydantic model for FastAPI?

easy

A. Override the __init__ method of the model

B. Use @validator decorator inside the model class

C. Add a method named validate() outside the model

D. Use @app.validator decorator in the FastAPI app

Solution

1. Step 1: Recall Pydantic validation method

   Pydantic uses @validator decorator inside model classes for custom checks.

2. Step 2: Check other options

   Overriding __init__ or external validate() methods are not standard; @app.validator does not exist.

3. Final Answer:

   Use @validator decorator inside the model class -> Option B

4. Quick Check:

   @validator = Custom check inside model [OK]

Hint: Custom validators use @validator inside Pydantic models [OK]

Common Mistakes:

• Trying to override __init__ for validation
• Using decorators outside the model class
• Confusing FastAPI app decorators with Pydantic validators

3. Given this Pydantic model with a custom validator:

from pydantic import BaseModel, validator

class User(BaseModel):
    age: int

    @validator('age')
    def age_must_be_positive(cls, v):
        if v <= 0:
            raise ValueError('Age must be positive')
        return v

What happens if a request sends {"age": -5} to a FastAPI endpoint using this model?

medium

A. The endpoint accepts the data and processes it

B. FastAPI ignores the validator and accepts the data

C. The server crashes with an unhandled exception

D. FastAPI returns a 422 error with validation details

Solution

1. Step 1: Understand the validator logic

   The validator raises ValueError if age is not positive.

2. Step 2: Know FastAPI's error handling

   FastAPI catches validation errors and returns a 422 response with details.

3. Final Answer:

   FastAPI returns a 422 error with validation details -> Option D

4. Quick Check:

   Invalid data triggers 422 error [OK]

Hint: Invalid data triggers 422 error in FastAPI [OK]

Common Mistakes:

• Assuming server crashes on validation error
• Thinking FastAPI accepts invalid data silently
• Confusing 422 with 500 server error

4. Identify the error in this FastAPI custom validation code:

from pydantic import BaseModel, validator

class Item(BaseModel):
    price: float

    @validator('price')
    def check_price(cls, value):
        if value < 0:
            return ValueError('Price must be non-negative')
        return value

medium

A. The validator should raise ValueError, not return it

B. The validator must be a staticmethod, not classmethod

C. The field price should be an int, not float

D. The validator name must start with 'validate_'

Solution

1. Step 1: Check validator error handling

   Validators must raise exceptions, not return them.

2. Step 2: Verify other parts

   Validator is correctly a classmethod; price type float is valid; no naming rule requires 'validate_' prefix.

3. Final Answer:

   The validator should raise ValueError, not return it -> Option A

4. Quick Check:

   Raise errors in validators, don't return [OK]

Hint: Raise exceptions in validators, don't return them [OK]

Common Mistakes:

• Returning exceptions instead of raising
• Confusing @validator with staticmethod
• Changing field types unnecessarily

5. You want to validate a request body in FastAPI where a user can submit either an email or a phone number, but not both. How can you implement this custom validation in a Pydantic model?

hard

A. Use a root_validator to check that exactly one of email or phone is provided

B. Add separate @validator for email and phone fields to check presence

C. Use FastAPI dependency to validate after model parsing

D. Make both fields required and let FastAPI handle conflicts automatically

Solution

1. Step 1: Understand the validation requirement

   We need to ensure exactly one of two fields is present, a cross-field check.

2. Step 2: Choose validation method

   root_validator runs after all fields are parsed and can check multiple fields together.

3. Step 3: Evaluate other options

   Field validators cannot check other fields; dependency validation is after parsing; making both required contradicts the rule.

4. Final Answer:

   Use a root_validator to check that exactly one of email or phone is provided -> Option A

5. Quick Check:

   Cross-field checks use root_validator [OK]

Hint: Use root_validator for checks involving multiple fields [OK]

Common Mistakes:

• Trying to check multiple fields in single field validators
• Relying on FastAPI dependencies for core validation
• Making both fields required when only one should be