Your progress is only saved in this browser. to protect it and pick up on any device.

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.

0 of 1 steps0%

Practice reading load charts in a safe simulation before you spend a minute generating real traffic from your machine.

1

Find a tipping point in the load lab

The Load lab below is a simulation inside LiftOff — not Postman, and not real traffic to Sample APIs. That’s intentional.

Why practice here first? Real Performance runs take time, use your machine (or cloud VU hours), and are awkward to replay while you’re still learning what a healthy chart vs a breaking chart looks like. The lab lets you turn virtual users up and down until you can see a tipping point — avg staying relatively calm while p95 and errors climb. That pattern is exactly what you’ll look for in Postman’s live metrics next.

The lab is tuned so the simulated API stays healthy until roughly 80 concurrent users, then degrades.

  1. Set virtual users low (~20) and click Run test. Confirm avg and p95 look calm.
  2. Raise virtual users past 80 and run again.
  3. When the breakpoint badge appears, read the summary chips — notice how p95 and errors move relative to the average.

Expected outcome: You’ve found the knee near 80 VU and can describe what changed on the chart.

Load lab

Practice reading load charts here first — simulated Fixed load, no traffic leaves this browser. Then you'll look for the same patterns in Postman.

Tip: start low, then push past ~80 VU. Watch p95 and errors, not only the average.

Run a test to see avg latency, p95, and error rate over time