What this tests
headersparsing
Point your client at this specimen and find out — before prod does — whether it reads the headers, or just the status code.
Anatomy
You asked for JSON; the endpoint returned CSV — because the export flag defaulted, the format parameter silently fell through, or a middleware translated the response into a spreadsheet because somewhere in the architecture, a human being once said "can't it just be Excel" and the infrastructure remembered. The body is fine, technically: it's valid CSV, correctly delimited, the data is all there. It's just in a different religion. Your JSON parser will reject the leading header row with an error mentioning a token that isn't in the file, and your data pipeline will either ingest garbage or produce an error that points absolutely nowhere near the actual problem. This is the most common content-negotiation failure in the wild and the most preventable: the Content-Type is right there saying text/csv, and your client ignored it because it was expecting JSON, which is the same error as the person who ordered a coffee and drank the soup.
Replay it
curl -i https://faultydata.com/r/FD-2026-058
// response appears hereSignature
{Status:200 Headers:map[Content-Type:text/csv; charset=utf-8] Body:id,name,email
1,ada,ada@example.com
2,bo,bo@example.com
Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-036 — Content-Encoding lie (gzip header, plain body) FD-2026-039 — XML where JSON was promised FD-2026-052 — JSONP callback wrapper FD-2026-019 — JSON body, text/plain label FD-2026-041 — Retry-After as HTTP-date FD-2026-086 — charset=utf-16 lie on a UTF-8 body