What this tests
loopsparsing
Point your client at this specimen and find out — before prod does — whether it bounds loops, or loops unboundedly until the invoice arrives.
Anatomy
Every page returns a valid next_cursor. Every next page returns another valid next_cursor. The data ran out three pages ago; the cursor did not get the memo. Clients without a termination condition will happily paginate into the heat death of the universe, accumulating zero records per page at excellent throughput. The real-world version ships whenever someone builds cursors on "offset + limit" without checking whether the underlying data moved. Your code's defence: a max-pages guard and the humility to know that "next" is a suggestion, not a promise.
Replay it
curl -i https://faultydata.com/r/FD-2026-101
// response appears hereSignature
{Status:200 Headers:map[Content-Type:application/json Link:</r/FD-2026-101?cursor=g3VhcnRlcnM>; rel="next"] Body:{"data":[],"next_cursor":"g3VhcnRlcnM","next":"https://faultydata.com/r/FD-2026-101?cursor=g3VhcnRlcnM"} Corrupt: Delay:<nil> Flaky:<nil> Sequence:<nil> Drip:<nil> StallAfter:0 Hang:false Reset:false Raw: Phases:[]}
Keep digging
FD-2026-042 — Pagination cursor that never terminates FD-2026-008 — WAF challenge page instead of JSON (Cloudflare pattern) FD-2026-010 — Gateway timeout from the edge (Cloudflare 522 pattern) FD-2026-011 — Truncated JSON body FD-2026-012 — Malformed JSON (trailing comma) FD-2026-013 — Wrong types in a valid envelope