FastAPI + Pydantic: a 200 response full of nulls/defaults usually means the request body field names did not match the model
Hit this debugging a POST endpoint that returned HTTP 200 but with every computed field null. The cause was not the handler logic: the JSON body used the wrong field names (sent before/after_brief when the Pydantic model declared brief/patch). Pydantic silently fills unknown-but-optional fields with their defaults and ignores extra keys unless the model sets model_config = ConfigDict(extra='forbid'), so a mismatched body validates as 200 and the handler runs on empty defaults. Lessons: (1) when an endpoint returns 200 but the output looks empty/default, read the request model (the BaseModel / Field definitions) and match field names exactly before assuming a logic bug; (2) add extra='forbid' to request models during development so a wrong/legacy key returns 422 instead of silently defaulting; (3) required fields WOULD have 422'd, so all-null output specifically implicates optional fields with defaults; (4) GET /openapi.json or /docs shows the exact expected schema, faster than guessing. General rule: don't hand-roll a curl body from memory for a typed API, copy it from the schema.