Functional testing

Your API returns a 200. Now prove it returns the right thing.

Postman Functional Testing checks that each endpoint returns the right status, schema, and field values, using the collections you already have, so developers, QA teams, and coding agents catch broken responses before they ship.

Run it in the Collection Runner in the Postman app, or let your favorite coding agents like Claude Code, Codex, and Cursor run it for you with the Postman CLI.

Get Started for Free

エージェント向けにインストール

npm install -g postman-cli
Get started with
Example run with illustrative numbers: Claude Code in a terminal. Asked to test a new refunds endpoint before a pull request, it adds Postman tests for the success path, the response schema, and an over-refund error case, then runs the Refunds folder with the Postman CLI. One test fails because an over-refund returns 201 instead of 422. The agent adds the missing check to the handler and reruns the tests, which pass, and links the run in Postman for reviewers.

世界中の導入企業

PayPal社のロゴ
Moneris社のロゴ
Autodesk社のロゴ
Kroger社のロゴ
Cover Genius社のロゴ
Siemens社のロゴ
ZEISS社のロゴ

Install the Postman plugin in your coding agent

Install the Postman plugin and your agent gets testing workflows it can run on its own: writing assertions from your spec or code, running one request or a whole collection, and gating CI on failed tests. Your agent can also test against a mock when the live backend isn't ready.

Every command runs through the Postman CLI, the same tool your CI pipeline uses.

get the Postman plugin

ステップ 1
claude plugin marketplace add anthropics/claude-plugins-official
ステップ 2
claude plugin install postman@claude-plugins-official
See all Postman skills

Try these prompts

WHY POSTMAN

Functional testing in Postman

Postman Functional Testing runs the pm.test assertions saved in your collections against each response's status, schema, and field values. The same tests run in the Collection Runner, in your coding agent's terminal, and in CI, so there's no new framework to learn. A 200 only says the server answered. A failed assertion fails the run anyway.

  • Tests for more than a 200 OK

    Check status codes, field values, and headers, validate the body against a JSON Schema, and send incomplete data or wrong parameters to confirm the endpoint fails the way it should.

  • Your collection is the test suite

    Assertions live at the request, folder, or collection level, so every run checks the same things: in your agent's terminal, in CI, and in the Postman app.

  • Output your agent can act on

    A failed assertion exits non-zero, even when the API returned a 200. Add --output for a YAML run report your agent can read back to see which tests failed.

  • Gates in CI

    Add the Postman CLI GitHub Action, or copy a CI config for your provider from the Postman app. A failing test fails the job. JUnit, JSON, and HTML reports are available for v2 JSON collections.

  • One collection, three jobs

    The collection your agent tests with also runs as a performance test with the same pm.test assertions, and as a scheduled monitor that alerts you when a test fails.

  • Agent Mode in the Postman app

    Working in the app instead of your editor? Ask Agent Mode to add new tests to a request or fix the ones that fail.

Animated example with illustrative data: a Postman Collection Runner functional run of the Fleet Logistics API collection against the Fleet - Production environment. Six requests run one after another (Get Vehicles, Create Vehicle, Get Vehicle, Create Shipment, Create Shipment without auth, and Delete Vehicle), and each request's tests appear beneath it as they pass, including a request sent without auth that correctly returns 401. All 20 tests pass, with 0 failed and 0 errors.

How it works

Step 1

Write the tests

Add pm.test assertions to a request, folder, or collection. Check the status, validate the body against a JSON Schema, and confirm bad input fails the way it should.

Step 2

Run the collection

Run it in the Collection Runner, or let your agent run postman collection run from its terminal.

Step 3

Fix what failed

A failed assertion exits non-zero, even when the API returned a 200, so your agent knows which test broke, fixes the code, and reruns.

Step 4

Gate CI

Run the same command in your pipeline with the Postman CLI GitHub Action or your provider's config. A failing test fails the job.

Postman Collections have transformed API testing, enabling us to experiment quickly and efficiently when developing new features or implementing changes.”
NetDocuments logo

Benny Yamagata

Senior Software Engineer, NetDocuments

Read the NetDocuments story

Frequently asked questions

Trusted by over 50 million developers and 500,000 companies.

Install for your agents

npm install -g postman-cli
Get started with

Install for desktop

Sign up for free