Module 5 of 5 in API Testing
Learn to tell when an API slows down under traffic. You build a coffee API collection, practice reading average and p95 response times in a simulator, run a real load test in Postman, and set a pass/fail threshold.
- You'll build
- A load-tested coffee API collection and a pass/fail performance threshold you can use in CI.
- Time
- About 35 min · 6 parts · 8 steps · progress saves as you go
- How it works
- You do each step, then click Validate and LiftOff checks your work. 4 of the 8 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 few setup steps, shown below before you start
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.
What you'll practice
- Build a collection that can run under load (requests + tests + environment)
- Learn why averages mislead — and what p95 / errors tell you
- Train your eye in the in-browser load lab (safe simulation)
- Run the same collection in Postman’s Performance tab
- Read assertions under load, then pick a CLI-ready
--pass-ifbar
Build a collection worth loading
A performance test doesn’t invent its own requests — it loops a collection you already have. Build that foundation first.
Learn what the numbers mean
One fast Send doesn’t prove an API is healthy under traffic. Use a short Functional runner pass, then learn why avg vs p95 change the decision — before you open the Performance tab.
Train your eye in the load lab
Practice reading load charts in a safe simulation before you spend a minute generating real traffic from your machine.
Run it in Postman
This is the only step where you use Postman’s real Performance feature — configure a calm Fixed App run, skim the other knobs, then watch the live graph.
Assert under load
After the live graph, dig into per-request metrics and whether pm.test() assertions stayed green under concurrency.
Take the bar to CI
Teams usually want the same performance check in a pipeline — with an explicit threshold that fails the build when it’s missed.