Interface & Contract
Field/parameter name mismatch
Last updated: 4 Mar 2026
Definition
Different names/casing used for the same value across boundaries, so inputs are ignored or misrouted.
How to fix Field/parameter name mismatch?
Standardize naming; validate via request/response schema; align OpenAPI and handlers; add serialization tests for arrays/objects
Symptoms
Observable signs that may indicate Field/parameter name mismatch:
- API receives parameter but handler reads a differently named field.
- Form submits succeed but server ignores the intended value.
- OpenAPI doc shows field casing that differs from implementation.
Example Errors:
- Unrecognized parameter 'user_id'; did you mean 'userId'?
- 422 Unprocessable Entity: field required
- Request validation failed: additionalProperties 'foo'