Why Protected routes in FastAPI? - Purpose & Use Cases

The Big Idea

What if one missed check lets strangers see your private data?

The Scenario

Imagine building a web app where some pages should only be seen by logged-in users, like a personal dashboard or settings page.

You try to check user access manually on every page by writing repeated code everywhere.

The Problem

Manually checking user permissions on every route is tiring and easy to forget.

This leads to security holes where unauthorized users can sneak in.

It also makes your code messy and hard to maintain.

The Solution

Protected routes let you define access rules once and apply them automatically to the right pages.

FastAPI helps you secure routes by using dependencies that check user authentication before running the route code.

Before vs After

✗ Before

def dashboard():
    if not user_logged_in():
        return 'Access denied'
    return 'Welcome to your dashboard'

✓ After

@app.get('/dashboard')
async def dashboard(user: User = Depends(get_current_user)):
    return f'Welcome {user.name} to your dashboard'

What It Enables

You can safely build apps where only authorized users see sensitive pages, without repeating security checks everywhere.

Real Life Example

Think of an online bank app where your account info page is protected so only you can see your balance and transactions.

Key Takeaways

Manual access checks are error-prone and repetitive.

Protected routes centralize security logic for cleaner code.

FastAPI dependencies make protecting routes easy and reliable.