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 docs said the response is an object. The response is a JSON array. Both are "valid JSON," both unmarshal without error into their respective types, and only one of them is what your client declared in its structs. Strongly-typed clients die immediately; JavaScript clients store the array, treat it as truthy, and render [object Object] into someone's dashboard. Ships in production every time someone "fixes" a search endpoint to return multiple results and forgets the envelope. Schema validation exists; this is the specimen that makes you use it.

Replay it

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

// response appears here

Signature

{Status:200 Headers:map[Content-Type:application/json] Body:[{"id":1,"name":"the response is an array","docs_said":"object","unmarshal":"good luck"}] Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}

Keep digging

FD-2026-013 — Wrong types in a valid envelope 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