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
The body is a JSON string. Inside the string is JSON. The first parse hands you a quoted blob; the second hands you the actual object — the payload was serialized twice because someone passed a dict through a template that had already been through a serializer, like a letter sealed inside an envelope inside a second, identical envelope addressed to the first envelope. Signature move of APIs assembled entirely from other APIs, which is to say, most of them. Somewhere in the chain, json.dumps() met a payload that was already a string and simply did its job. The bug is nobody's. It's everyone's. It's the architecture. Clients that parse once and expect an object get a string and explode. Clients that parse until they get an object survive but must now answer the question "how many times is too many", which is a philosophical position as much as a loop bound.
Replay it
curl -i https://faultydata.com/r/FD-2026-040
// response appears hereSignature
{Status:200 Headers:map[] Body:"{\"user\": {\"id\": 12345, \"name\": \"ada\"}, \"ok\": true}" Corrupt: 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-012 — Malformed JSON (trailing comma) 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)