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
HTTP 200. Transport: triumphant success. Payload: complete failure. An error object smuggled inside a success envelope — standard practice for GraphQL and SOAP, an unmarked landmine everywhere else. The single most common lie in API-land and one of the oldest: "the request succeeded" as a statement about the request, not the result. Clients that check the status code and move on report victory while serving users an error dressed as data — the system logs say green, the screen says broken, and someone gets paged about a failure that "should be impossible" because HTTP said it was fine. HTTP was lied to first. HTTP is innocent here. Mostly. The errors array contains GRAPHQL_VALIDATION_FAILED, for flavour. Your client either inspects the body's errors field or discovers, eventually and at some cost, that "200" is just what the transport thought of the journey, not the destination.
Replay it
curl -i https://faultydata.com/r/FD-2026-034
// response appears hereSignature
{Status:200 Headers:map[] Body:{"errors":[{"message":"Field \u0027user\u0027 doesn\u0027t exist on type \u0027Query\u0027","extensions":{"code":"GRAPHQL_VALIDATION_FAILED"}}],"data":null} 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-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