Karate DSL ↔ REST API Pagination: Unresolved Built‑in Support

Goal

To test a REST endpoint that returns a large collection, we need to bound the number of records returned and iterate over paged responses within Karate.

Constraints & Uncertainty

• The API may use non‑standard pagination parameters (e.g., offset, page, size).
• Karate does not ship a dedicated pagination helper; loops must be written manually.
• Manual loops risk off‑by‑one errors or infinite recursion if the termination condition is incorrect.

Open Questions

1. Will Karate Labs introduce a native pagination API to simplify iterating over large datasets?
2. What is the safest pattern to detect the end of a paged result set when pagination parameters vary?
3. Can karate.filter be combined with a future pagination helper to automatically stop when a page contains no items?