What this tests
parsing
Point your client at this specimen and find out — before prod does — whether it actually validates what arrives, or just hopes.
Anatomy
A trailing comma. {"a": 1,} — legal in JavaScript, legal in every config file your team has ever touched, and a hard SyntaxError in actual JSON, a specification that was designed in ten days and has held a grudge ever since. This is the signature of a payload assembled by string concatenation rather than a serializer — someone's for-loop appending `field,` until the last one is left standing there like the last guest at a party, holding a comma and nobody's coat. Python's json module rejects it. Go rejects it. Node's JSON.parse rejects it. Only the file's author, reading it in VS Code where it looks completely normal, sees nothing wrong. The parser error message won't say "trailing comma", by the way. It'll say "unexpected token }" at a line number, and let you do the archaeology yourself.
Replay it
curl -i https://faultydata.com/r/FD-2026-012
// response appears hereSignature
{Status:200 Headers:map[] Body: Corrupt:malformed Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-011 — Truncated JSON body FD-2026-013 — Wrong types in a valid envelope FD-2026-014 — Encoding mismatch (claims UTF-8, sends Latin-1) FD-2026-015 — UTF-8 BOM prefix FD-2026-028 — Malformed channel file update (CrowdStrike, Jul 2024) FD-2026-034 — HTTP 200 wrapping an error (GraphQL/SOAP pattern)