Why Path operation dependencies in FastAPI? - Purpose & Use Cases

The Big Idea

Discover how to stop repeating yourself and make your API smarter with just a few lines!

The Scenario

Imagine building a web API where every route needs to check if a user is logged in, validate tokens, and connect to a database before running the main code.

You write this same code inside every route handler manually.

The Problem

Copying the same checks everywhere makes your code messy and hard to update.

If you want to change the login check, you must edit every route separately, risking mistakes and bugs.

The Solution

Path operation dependencies let you write these common checks once and reuse them automatically in routes.

FastAPI runs these dependencies before your main code, keeping your routes clean and consistent.

Before vs After

✗ Before

def route():
    check_user()
    validate_token()
    connect_db()
    # main logic

✓ After

from fastapi import Depends, FastAPI

app = FastAPI()

def common_checks():
    check_user()
    validate_token()
    connect_db()

@app.get('/items', dependencies=[Depends(common_checks)])
def route():
    # main logic

What It Enables

You can build secure, clean, and maintainable APIs where shared logic runs automatically before each route.

Real Life Example

In a shopping app API, you ensure every request verifies the user's identity and permissions before accessing product or order data.

Key Takeaways

Manual repeated checks clutter code and cause bugs.

Dependencies run shared logic automatically before routes.

This keeps APIs clean, secure, and easy to maintain.

Practice

1. What is the main purpose of using Depends() in FastAPI path operations?

easy

A. To create a new database connection manually

B. To define the HTTP method for the route

C. To specify the response status code

D. To run shared code before handling requests

Solution

1. Step 1: Understand the role of Depends()

   Depends() is used to declare dependencies that run shared code before the main path operation function executes.

2. Step 2: Identify the purpose in FastAPI

   This helps keep code clean by reusing common logic like authentication or database access.

3. Final Answer:

   To run shared code before handling requests -> Option D

4. Quick Check:

   Depends() runs shared code before requests [OK]

Hint: Depends() runs shared code before request handling [OK]

Common Mistakes:

• Thinking Depends() sets HTTP methods
• Confusing Depends() with response status codes
• Assuming Depends() manually creates DB connections

2. Which of the following is the correct way to declare a dependency in a FastAPI path operation function?

easy

A. def read_item(item_id: int, user=Depends[get_current_user]):

B. def read_item(item_id: int, user=Depends):

C. def read_item(item_id: int, user=Depends(get_current_user)):

D. def read_item(item_id: int, user=get_current_user()):

Solution

1. Step 1: Recall the syntax for dependencies

   Dependencies are declared by assigning a parameter to Depends() with the dependency function inside.

2. Step 2: Check each option

   def read_item(item_id: int, user=Depends(get_current_user)): correctly uses user=Depends(get_current_user). Others have syntax errors or call the function directly.

3. Final Answer:

   def read_item(item_id: int, user=Depends(get_current_user)): -> Option C

4. Quick Check:

   Depends() with function inside parentheses [OK]

Hint: Use Depends(function_name) with parentheses [OK]

Common Mistakes:

• Calling the dependency function directly
• Using Depends without parentheses
• Using square brackets instead of parentheses

3. Given the code below, what will be the output when accessing /items/5?

from fastapi import FastAPI, Depends

app = FastAPI()

def get_token():
    return "token123"

@app.get("/items/{item_id}")
def read_item(item_id: int, token: str = Depends(get_token)):
    return {"item_id": item_id, "token": token}

medium

A. {"item_id": 5, "token": "token123"}

B. {"item_id": 5, "token": null}

C. RuntimeError due to missing token parameter

D. SyntaxError in dependency declaration

Solution

1. Step 1: Understand dependency execution

   The get_token function returns "token123" and is injected into token parameter via Depends().

2. Step 2: Check the returned dictionary

   The path operation returns a dictionary with item_id and token keys, so the output includes the token string.

3. Final Answer:

   {"item_id": 5, "token": "token123"} -> Option A

4. Quick Check:

   Dependency injects token value correctly [OK]

Hint: Depends injects return value as parameter [OK]

Common Mistakes:

• Expecting token to be null without dependency
• Thinking dependency causes runtime error
• Confusing syntax with runtime errors

4. Identify the error in the following FastAPI code using dependencies:

from fastapi import FastAPI, Depends

app = FastAPI()

def get_user():
    return "user1"

@app.get("/profile")
def profile(user: str = Depends(get_user)):
    return {"user": user}

@app.get("/dashboard")
def dashboard(user = Depends(get_user)):
    return {"dashboard_user": user}

medium

A. Missing type annotation for 'user' in dashboard function

B. Depends() used incorrectly without parentheses

C. get_user function missing return statement

D. Path operation decorator missing on dashboard function

Solution

1. Step 1: Compare both path operation functions

   The profile function declares user: str = Depends(get_user) with a type annotation.

2. Step 2: Identify the issue in dashboard

   The dashboard function uses user = Depends(get_user) but lacks a type annotation, which FastAPI requires for dependencies.

3. Final Answer:

   Missing type annotation for 'user' in dashboard function -> Option A

4. Quick Check:

   Dependency parameters need type annotations [OK]

Hint: Always add type annotations for Depends parameters [OK]

Common Mistakes:

• Omitting type annotations on dependency parameters
• Forgetting parentheses on Depends()
• Assuming missing decorator causes error

5. You want to reuse a dependency that extracts a user from a token and also check if the user is active before allowing access to multiple routes. How should you combine these checks using FastAPI dependencies?

hard

A. Create two separate dependency functions and use Depends() on both in the path operation

B. Call the user extraction function inside the active check function and use Depends() only on the active check

C. Use a single dependency function that returns user without any checks

D. Use Depends() only on the user extraction function and check active status inside each path operation

Solution

1. Step 1: Understand dependency chaining

   You can call one dependency inside another to reuse logic and combine checks.

2. Step 2: Apply chaining for user extraction and active check

   By calling the user extraction inside the active check dependency, you only need to use Depends() on the active check in routes.

3. Final Answer:

   Call the user extraction function inside the active check function and use Depends() only on the active check -> Option B

4. Quick Check:

   Chain dependencies by calling one inside another [OK]

Hint: Chain dependencies by calling one inside another [OK]

Common Mistakes:

• Using multiple Depends() separately causing repeated calls
• Not chaining dependencies and duplicating code
• Checking user active status outside dependencies