Module 4 of 5 in API Testing
Run one collection many times with different inputs from a CSV or JSON file. You add variables to a Movies API request, run it with a data file in the Collection Runner, then do the same from a Monitor.
- You'll build
- A data-driven Movies API collection that runs once per row in the Collection Runner and in a Monitor.
- Time
- About 25 min · 3 parts · 6 steps · progress saves as you go
- How it works
- You do each step, then click Validate and LiftOff checks your work. 1 of the 6 steps can't be checked automatically, so you click Done for those.
- You'll need
- A free Postman account and API key (connect it below)
- A Postman Solo plan or higher
Connect a Postman API key to check your work
You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.
This module uses Postman features available on the Solo plan and above.
Compare plans →Build a data-driven collection
Before you attach a data file anywhere, your collection has to speak the same language as the file: variable names in the request must match column headers, and your tests should read row values with pm.iterationData. This part builds that foundation in a dedicated workspace.
Run with a data file in the Collection Runner
The Collection Runner executes your collection once per row in the data file. Each row becomes one iteration, and variables from that row resolve in your request and scripts for that iteration only.
Data files in Monitors
Monitors can run your collection once per data row in a single cloud run — the same iteration model as the Collection Runner, on a schedule. Monitor data files are Solo+, limited to 1 MB and 50 rows, and must be uploaded in the monitor configuration. When your needs exceed fixed files — larger data, reuse across CI, or live queries — see Use datasets with a collection run in the next module.