What this tests

parsingsemantics

Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.

Anatomy

The schema said number. The wire sent a string. "id": "12345" — same digits, different species, and your typed client just attempted to stuff a word into an integer field with predictable consequences. This happens constantly in the wild because the upstream was written in a language where the difference between 42 and "42" is a theological position rather than a type error. PHP's loose typing is the usual suspect, but honestly any system that's ever passed a value through a spreadsheet — the data pipeline equivalent of laundering money — is capable of this. Weakly-typed clients shrug and carry on, storing a string where a number should be until something downstream tries to do arithmetic on it. Strongly-typed clients die at the boundary, loudly, which is ruder but considerably more honest.

Replay it

curl -i https://faultydata.com/r/FD-2026-013

// response appears here

Signature

{Status:200 Headers:map[] Body: Corrupt:wrong-types Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern) FD-2026-035 — Stack trace in the error body FD-2026-053 — SSO login page instead of your API response FD-2026-062 — Migration returns other customers' data (TSB, Apr 2018) FD-2026-072 — Success response confirming the wrong values FD-2026-087 — 200 OK, body never arrived