Why List and set validation in FastAPI? - Purpose & Use Cases

The Big Idea

What if your API could catch data mistakes before they cause bugs, without extra code?

The Scenario

Imagine you receive user data where you expect a list of unique items, like email addresses or tags, but users send duplicates or wrong types.

Manually checking each item and ensuring uniqueness can be tedious and error-prone.

The Problem

Manually validating lists and sets means writing repetitive code to check each element's type and uniqueness.

This approach is slow, easy to forget, and can cause bugs if validation is inconsistent.

The Solution

FastAPI's list and set validation automatically checks each item's type and ensures uniqueness for sets.

This saves time and prevents errors by handling validation cleanly and consistently.

Before vs After

✗ Before

def validate_emails(data):
    emails = data.get('emails', [])
    for email in emails:
        if not isinstance(email, str):
            raise ValueError('Invalid email')
    if len(emails) != len(set(emails)):
        raise ValueError('Duplicate emails')

✓ After

from pydantic import BaseModel
from typing import Set

class UserData(BaseModel):
    emails: Set[str]

What It Enables

You can trust your data is correct and unique without extra code, making your API safer and easier to maintain.

Real Life Example

When building a signup form API, you want to accept a list of user interests without duplicates and ensure each interest is a string.

FastAPI validates this automatically, so your backend logic stays clean.

Key Takeaways

Manual validation of lists and sets is slow and error-prone.

FastAPI automates type and uniqueness checks for lists and sets.

This leads to safer, cleaner, and easier-to-maintain code.

Practice

1. In FastAPI, when should you use List instead of Set for request data validation?

easy

A. When you want to store only unique items without order

B. When you want to automatically remove duplicates

C. When you want to validate a single item only

D. When the order of items matters and duplicates are allowed

Solution

1. Step 1: Understand List characteristics

   A List keeps the order of items and allows duplicates.

2. Step 2: Compare with Set characteristics

   A Set removes duplicates and does not guarantee order.

3. Final Answer:

   When the order of items matters and duplicates are allowed -> Option D

4. Quick Check:

   List = ordered with duplicates [OK]

Hint: Use List for ordered duplicates, Set for unique unordered [OK]

Common Mistakes:

• Confusing Set with List and expecting order
• Using Set when duplicates are needed
• Thinking List removes duplicates automatically

2. Which of the following is the correct way to declare a FastAPI endpoint expecting a set of integers in the request body?

easy

A. def endpoint(items: List[int]):

B. def endpoint(items: Set[int]):

C. def endpoint(items: dict[int]):

D. def endpoint(items: tuple[int]):

Solution

1. Step 1: Identify the correct type for unique collection

   Set[int] is used to declare a set of integers with unique values.

2. Step 2: Verify other options

   List[int] allows duplicates, dict[int] is invalid syntax, tuple[int] is fixed-length and ordered.

3. Final Answer:

   def endpoint(items: Set[int]): -> Option B

4. Quick Check:

   Set[int] = unique integer collection [OK]

Hint: Use Set[int] for unique integer collections in FastAPI [OK]

Common Mistakes:

• Using dict[int] which is invalid syntax
• Using tuple[int] which expects fixed length
• Confusing List with Set for uniqueness

3. Given this FastAPI endpoint code snippet, what will be the output if the input JSON is {"items": [1, 2, 2, 3]}?

from fastapi import FastAPI
from pydantic import BaseModel
from typing import Set

app = FastAPI()

class Data(BaseModel):
    items: Set[int]

@app.post("/unique")
def unique_items(data: Data):
    return {"unique_items": list(data.items)}

medium

A. {"unique_items": [1, 2, 3]}

B. {"unique_items": [1, 2, 2, 3]}

C. ValidationError due to duplicate items

D. {"unique_items": []}

Solution

1. Step 1: Understand Set validation in Pydantic

   Pydantic converts the input list to a set, removing duplicates automatically.

2. Step 2: Analyze the input and output

   Input has duplicates [1, 2, 2, 3], output converts to unique set [1, 2, 3].

3. Final Answer:

   {"unique_items": [1, 2, 3]} -> Option A

4. Quick Check:

   Set removes duplicates automatically [OK]

Hint: Set input removes duplicates, output shows unique items [OK]

Common Mistakes:

• Expecting ValidationError on duplicates
• Assuming output keeps duplicates
• Confusing List and Set behavior

4. Identify the error in this FastAPI model using List and Set:

from pydantic import BaseModel
from typing import List, Set

class Model(BaseModel):
    names: List[str]
    unique_ids: List[int]

    def __init__(self, **data):
        super().__init__(**data)
        self.unique_ids = set(self.unique_ids)

medium

A. No error, code works fine

B. Using List instead of Set for unique_ids is correct

C. Assigning a set to a List field breaks Pydantic validation

D. Missing type annotation for unique_ids

Solution

1. Step 1: Check field type and assignment

   unique_ids is declared as List[int] but assigned a set in __init__, causing type mismatch.

2. Step 2: Understand Pydantic validation rules

   Pydantic expects unique_ids to be a list; assigning a set breaks validation and type consistency.

3. Final Answer:

   Assigning a set to a List field breaks Pydantic validation -> Option C

4. Quick Check:

   Field type must match assigned value [OK]

Hint: Match field type with assigned value to avoid validation errors [OK]

Common Mistakes:

• Assigning set to List field without changing type
• Ignoring Pydantic's type enforcement
• Assuming __init__ can override field types safely

5. You want to create a FastAPI endpoint that accepts a list of tags but ensures no empty or duplicate tags. Which is the best way to validate this using Pydantic?

hard

A. Use tags: Set[str] and add a validator to reject empty strings

B. Use tags: List[str] and manually check duplicates and empties in the endpoint

C. Use tags: List[str] with a validator that converts to set and removes empties

D. Use tags: Set[str] without any validator

Solution

1. Step 1: Ensure uniqueness with Set

   Using Set[str] automatically removes duplicates.

2. Step 2: Add validator to reject empty strings

   Since Set only ensures uniqueness, a validator is needed to reject empty tags.

3. Final Answer:

   Use tags: Set[str] and add a validator to reject empty strings -> Option A

4. Quick Check:

   Set + validator = unique + no empty tags [OK]

Hint: Use Set for uniqueness and validator for empties [OK]

Common Mistakes:

• Using List without uniqueness enforcement
• Not validating empty strings in Set
• Relying on manual checks in endpoint instead of validators