The same workflow, twenty times, with different inputs
Testing an endpoint against one user tells you it works for one user. Data-driven runs let you keep the collection exactly as it is and vary the inputs instead.
Attach a CSV or JSON file
Open the Runner for a collection, click Select Data File, and pick a CSV or JSON file. Requestly detects the type and shows you a preview of its structure — columns and types for CSV, keys and shape for JSON — so you can confirm it lines up with your requests before anything runs.
Match column names to your variables
The rule is simple: a column name or object key should match the variable you use in your requests. A column named storyId fills {{storyId}}.
city,temperature
Vancouver,10
Austin,24
London,12[
{ "city": "Vancouver", "temperature": 10 },
{ "city": "Austin", "temperature": 24 },
{ "city": "London", "temperature": 12 }
]Either of those produces three iterations, with {{city}} and {{temperature}} resolving differently each time.
Run it — nothing else changes
A data-driven run is an ordinary collection run with values swapped per iteration. Pre-request scripts, post-response assertions, environments and authorization all behave exactly as they do on a single pass — which means your existing tests immediately cover many more cases without being rewritten.
