Performance testing
Your API works. Now see if it handles the load.
Postman Performance Testing turns the collections you already have into load tests with real-world traffic. Ramp to millions of virtual users in the cloud, see exactly where your APIs break, and fail CI when a run slips behind your last good baseline.
Run it in the Postman app, or let your favorite coding agents like Claude Code, Codex, and Cursor run it for you.
Trusted by teams at
Install the Postman plugin in your coding agent
Marketplace
get the Postman plugin
claude plugin marketplace add anthropics/claude-plugins-officialclaude plugin install postman@claude-plugins-officialperformance-testing
Load test any collection, on your machine or in the cloud
ci-integration
Gate every PR on your Postman checks
api-testing
Write the assertions that keep running under load
api-mocking
Load test your scripts against a mock, not production
jmeter-to-postman
Convert a JMeter test plan into a Postman load test
Try these prompts
WHY POSTMAN
Load testing built for the way agents work
Local for every change. Cloud for scale.
Local performance testing is unlimited on every plan. For real scale, the same command runs on Postman's cloud (US, EU, or static IPs on Enterprise), metered by virtual user hour.
Your collection is the load test
The requests and pm.test() assertions your agent already wrote run under load as-is. The Tests vs VU heatmap shows which assertions start failing, and at what load.
Traffic that looks like production
Drive each virtual user from a Dataset backed by Postgres, MySQL, or CSV, so a run at scale sends varied, realistic requests instead of one repeated payload.
Baselines that remember
Every run is saved with its collection, so your agent can pull the last good run and answer "did this change make it slower?" instead of handing you raw numbers.
Gates in CI
Set pass criteria like p95 under 500 ms and error rate under 1%. When a run misses the bar, the build fails and the slowdown never ships.
Safe by default
Before a cloud run, your agent shows you the target, virtual users, duration, and estimated usage, and waits for your go-ahead. It can test against a mock instead of a live backend.
Frequently asked questions
Load testing measures how an API performs when many virtual users send requests at once. It shows response times, throughput, and errors as traffic increases, so you can find bottlenecks before your users do. With Postman, you can reuse your existing collections, run quick smoke tests locally, and scale to hundreds or more virtual users using managed cloud infrastructure.
Functional tests verify that your API behaves as expected, but they don’t tell you how it performs under heavy traffic. An API can pass functional tests and still experience slow response times or errors when many users make requests simultaneously. Postman lets you reuse your existing collections, scripts, and assertions for performance testing without maintaining a separate set of load-test scripts.
Start with an existing Postman collection and configure your virtual users, test duration, and load profile. Run the test in the Postman app or with the Postman CLI. For larger tests, use Postman Cloud to generate load from managed infrastructure, while Postman aggregates metrics such as response times, throughput, and errors into a single report.
Local tests are useful for validating a test setup and catching obvious performance issues, but your machine’s CPU, network, and other resource limits can affect results. Postman Cloud uses managed infrastructure to generate load at greater scale, with aggregated results and shared run history. You can use the same collection and test configuration without rewriting your test.
For more details, read Cloud Performance Testing with Postman: From Laptop to CI.
Yes. With Postman’s plugin, your coding agent can help configure and run performance tests using your existing Postman collections. Ask it to set the load profile, virtual users, and test duration, then run the test locally or in Postman Cloud. You can review the results to understand response times, throughput, and errors under load.
Yes. Use the Postman CLI to run performance tests in your CI/CD pipeline. Add --runner postman-cloud to run load tests on Postman Cloud and generate larger loads with more virtual users. Use --pass-if to set performance thresholds for supported metrics such as latency, error rate, or throughput.
Use Postman static IP egress to run cloud performance tests against beta and staging APIs protected by a firewall. Your security team can allowlist Postman’s fixed egress IP address so Postman Cloud can reach your API.