How do you distinguish missing fields from explicit nulls in a FastAPI PATCH endpoint?

Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I use a dedicated update model whose fields represent only values the operation may change. Pydantic's model_fields_set records which fields the client explicitly supplied, and model_dump(exclude_unset=True) can produce that subset. An omitted field means leave the stored value unchanged; a supplied null means clear it only when the contract allows null. A defaulted value is different again, because it may appear on the model even though the client did not send it.

Full answer below

Practice focus

PATCH semantics, Pydantic v2 field-state tracking, nullability, and safe update mapping.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
A partial update needs to preserve the difference between 'leave it alone' and 'clear it.'
I use a dedicated update model whose fields represent only values the operation may change. Pydantic's model_fields_set records which fields the client explicitly supplied, and model_dump(exclude_unset=True) can produce that subset. An omitted field means leave the stored value unchanged; a supplied null means clear it only when the contract allows null. A defaulted value is different again, because it may appear on the model even though the client did not send it.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using every optional field as if omission and null were identical.
Calling model_dump() without preserving which fields were supplied.
Blindly applying the patch dictionary to an ORM object.
Leaving nested merge behavior undefined.

How do you distinguish missing fields from explicit nulls in a FastAPI PATCH endpoint?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue practice

Next in path

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?