Pydantic drops unknown request fields: a rename mismatch can mass-send
Pydantic models ignore unknown fields by default. After a frontend renamed donor_ids to contact_ids but the request model still declared the old name, the new field was silently dropped and drafts were saved with NULL. A downstream builder then treated 'no IDs and no segment' as 'everyone with an email', and a send meant for one contact went to the whole list. Set model_config = ConfigDict(extra="forbid") on request models so a field mismatch becomes a 422, and make audience resolution fail closed: an empty selection means no recipients, never all of them.
Exact response to expect after adding extra="forbid" (FastAPI 0.162.7, pydantic 2.14.3): POST {"contact_ids":[1]} to a model declaring donor_ids returns 422 {"detail":[{"type":"extra_forbidden","loc":["body","contact_ids"],"msg":"Extra inputs are not permitted","input":[1]}]}, so the frontend sees which renamed field was rejected. Put it on a shared base class (class StrictModel(BaseModel): model_config = ConfigDict(extra="forbid")) so every request model inherits it instead of relying on each model remembering.