Postman Release Notes

Improvements

Run setup and teardown collections for performance tests in the Postman desktop app

You can now add setup and teardown collections to a performance test that runs from the Postman desktop app. The setup collection runs once before the test starts, so you can prepare what the test needs, such as creating an account or requesting an access token. The teardown collection runs once after the test ends, so you can clean up afterward, such as deleting the data the test created.

To learn more, see

Run a performance test with setup and teardown collections
.

Keep Flow blocks up to date with the latest snapshot

Flow blocks now make it easier to see when they’re using an older snapshot. If a
Flow
block isn’t using the latest snapshot, a warning appears with an
Update to latest
action.

You can also turn on
Always use latest
to automatically pin the
Flow
block to the newest reusable snapshot whenever one is published. Selecting an older snapshot turns off
Always use latest
and surfaces the update warning.

What’s New

Work with datasets in the Postman CLI

Available on Solo, Team, and Enterprise plans

With the postman dataset commands, you can manage reusable test data, from static files to live databases, and use it to drive data-driven collection and performance runs from the Postman CLI, including in CI/CD.

Redirect requests to a mock during a collection run

The postman collection run command now supports a --use-mock option that redirects requests to a mock while the collection runs. Each mapping points a URL to a local mock (mock:) or a deployed mock server (mock-server:), and you can pass --use-mock more than once to redirect multiple URLs. When a mapping points to a local mock, the Postman CLI starts it for you.

What’s New

Evaluate AI-generated output in Postman Flows

Postman Flows now supports AI evals for automatically grading AI-generated output against qualitative criteria. In the
AI Agent
block, you can enable built-in evals for friendliness, safety, non-toxicity, correctness, and relevance, or create your own custom evals.

You can also use
pm.eval
in the
Evaluate
block to define preset or custom evals with options such as thresholds, reference answers, context, and judge models. After your flow runs, you can review eval scores and reasons on the block, from the
Evals
output, and in the
All Evals
tab in the run log.

What’s New

Run performance tests in the Postman Cloud

Available on Solo and Team plans

The postman performance run command now supports a --runner option that selects where a performance test’s load originates. By default, load originates from the machine that invokes the command. Use --runner postman-cloud to generate load from Postman’s managed cloud infrastructure instead.

Use datasets in performance tests

Available on Solo, Team, and Enterprise plans

The postman performance run command now supports datasets as a test data source. Use --dataset-id and --dataset-view-id to select a dataset and view, and --dataset-distribution to control how rows are assigned to virtual users (round-robin, fixed, or random).

Connect a workspace to a Git repository

The new postman workspace connect-git command binds a Postman workspace to a Git repository on your machine. Connect the repository first, then use postman workspace push and postman workspace pull.

Pull a workspace to your local folder

The new postman workspace pull command pulls a workspace’s collections, environments, specifications, and other elements into your local Git repository. It is the counterpart to postman workspace push. If the Git repository isn’t already connected to the workspace, Postman creates the connection before pulling.

More ways to work with local mocks

You can now list, inspect, and delete local mocks with the new postman mock list, postman mock get, and postman mock delete commands. The postman mock generate command now generates a sample mock with a GET /health endpoint when you run it without a collection or specification file, providing a runnable starting point for you to edit.

Set up Playwright network capture automatically

The new postman app setup-capture command sets up Playwright network capture for you. It finds your Playwright config, installs the postman-playwright package, and wraps your config with withPostman(). The postman app test command also runs this as an interactive preflight check.

Improvements

Autofix workspace lint issues

The postman workspace lint command now has a --fix option that applies safe autofixes to repairable lint issues.

Bug Fixes

Fixed an issue where the JSON and HTML reports were missing run timings (run.meta.duration was null). Run timings are included again.

What’s New

Introducing Postman Datasets

Available on Solo, Team, and Enterprise plans

Postman Datasets are managed groups of structured data that live inside your workspace, designed to power realistic, repeatable, and scalable API testing. Create a dataset once and reuse it across collection runs, monitors, performance tests, mock servers, scripts, and Flows. It works in the Postman app, the Postman CLI, and CI environments.

Each dataset pulls from one or more sources and exposes views: saved SQL queries that select, filter, join, and transform fields for a specific test. Solo plans support CSV, JSON, and Excel file sources, including AI-assisted generation. Team and Enterprise plans can also connect to live databases, like MySQL and PostgreSQL. Enterprise plans additionally support custom JDBC drivers for many JDBC-compatible databases. Databases that aren’t publicly exposed are reachable over an SSH tunnel, and connection details can be stored as vault secrets in Postman Vault.

Agent Mode understands the datasets and views in your workspace. It uses your real field names when writing requests, tests, and scripts. You can describe the data you need so Agent Mode generates realistic test data for you.

To learn more, see

Test APIs with datasets in Postman
.

Run performance tests in the Postman Cloud

Available on Solo and Team plans

Run performance tests in the Postman Cloud to scale beyond the limits of a single machine, keep tests running after you close your computer, and persist detailed performance data for later review. Postman distributes the load across managed workers and streams metrics, errors, and test assertions live while the run is in progress, using the same collection and scripts you already test with. You can compare past runs and share results with your team.

You can also add setup and teardown collections to a cloud performance test, to prepare what the test needs before it starts and clean up once it ends.

To learn more, see

Test API performance
.

Pay-as-you-go for performance test VU hours

Available on Solo and Team plans

Cloud performance test runs now consume virtual user (VU) hours, based on the number of virtual users in a run and the test’s duration. Team Admins can view a detailed breakdown of VU hour usage by run, including the run name, source, collection, VU hours consumed, who created the run, and when it finished.

To learn more, see

About resource usage
.

Migrate your small team to Postman Organizations using a self-serve option

Available on Enterprise plans

You can now migrate your small team to organizations yourself directly from the Postman app.

To learn more, see

Migrate your Enterprise team to an organization
.

What’s New

Lint your workspace before pushing

The postman workspace push command now runs a lint check before pushing. It blocks the push if your workspace configuration has lint errors, and skips any entity that has lint errors while still pushing the clean ones.

Set up application tests interactively

If you run postman app test without a configuration file or collections, the command now guides you through an interactive setup instead of exiting. You can select existing collections or generate a new collection from your test traffic, complete with auto-generated test scripts.

Author scripts and inspect script outcomes for webhooks

You can now author and update a webhook’s scripts with the new postman webhook scripts set command. The postman webhook requests describe command now includes a test report, and adding the --verbose option streams the script execution logs.

Improvements

Install-aware update instructions

When an update is available, the Postman CLI now detects whether it was installed with npm or as a direct download, and shows the matching update instructions.

What’s New

Lint your entire local workspace

The postman workspace lint command lints your whole local workspace in one report: the workspace configuration plus every collection, spec, environment, and globals file. Use --meta to lint only the workspace configuration.

Track the deployed version in application tests

The postman app test command can now record which deployed version of your application each test run exercised, so you can correlate results with specific deployments. Provide the version with the --deployed-version option, or from your Playwright report metadata.

Bug Fixes

Fixed an unclear error when a cloud performance run requested fewer virtual users than the minimum allowed. The postman performance run command now explains the minimum virtual-user requirement.

Fixed an issue where a worker crash could stop a Private API Monitoring runner from processing runs. The runner now recovers automatically.

What’s New

Generate API mocks from a Native Git collection directory

The postman mock generate command now accepts a directory containing a Native Git v3 collection, not just a single collection file. You can generate example-rich mocks straight from a Git-synced workspace.

Improvements

Push documents to your workspace

The postman workspace push command now syncs documents (Markdown files under postman/documents/), in addition to the collections, environments, specifications, and globals it already supported.

Faster, more secure installs

The macOS and Linux installers now prompt for your password once instead of several times. All three installers (macOS, Linux, and Windows) now verify the downloaded binary’s signature before installing.

Control the port for mock servers

The postman mock run command now supports a --port option. Pass a specific port, or use --port auto for a port assigned automatically. If you don’t set a port, the mock uses its configured port and falls back to an available one if that port is busy.

Bug Fixes

Fixed an issue where the postman mock run command served v3 example bodies as a raw { type, content } object instead of the example’s actual payload.

What’s New

Mocks are now available in Cloud View

Available on Solo, Team, and Enterprise plans

Mocks let you simulate APIs using custom JavaScript request handlers. In Cloud View, each mock receives a unique URL and is always available to handle requests.

You can also deploy a mock as a mock server, giving your team a cloud-hosted service they can send requests to at any time. By default, mock servers deployed from a mock are private and require workspace access or a valid Postman API key.

To learn more, see

Build API mocks with JavaScript

.

Postman Flows now available in the EU region

Available on Enterprise plans

Postman Flows is now available on the Postman EU Data Residency plan.

To learn more, see

Postman EU Data Residency

.

What’s New

Generate a local code mock from a collection or spec

You can now generate a local code mock from a Postman collection or an OpenAPI spec with the new postman mock generate command. It needs no Postman account or network access to generate or run, so you can use it in CI/CD. Run the generated mock with postman mock run.

Improvements

Code mock responses now match the Postman app

Code mock examples now serve their actual response headers and content types instead of always using application/json. Simulated fault responses, such as chaos and error conditions, also return the same status code and body as the app.

Expanded Private API Monitoring runner support for collections

Private API Monitoring runners can now monitor collections that contain not just HTTP requests, but gRPC and GraphQL requests as well. Runners now also prefetch vault secrets in bulk at the start of a run for faster execution.

What’s New

Generate Swift SDKs

You can now generate Swift SDKs with the Postman CLI, using postman sdk generate.

Lint local environment and globals files

You can now validate your environment and globals files with the new postman environment lint and postman globals lint commands.

Improvements

Push global variables to your workspace

The postman workspace push command now pushes your workspace’s global variables, in addition to the collections, environments, and specifications it already supported.

Bug Fixes

Fixed an issue where TypeScript code in flow Evaluate, If, and Condition blocks failed to run from the CLI. Scripts authored in TypeScript are now transpiled to JavaScript before they run, so type annotations no longer cause errors.

What’s New

Buy Postman from AWS Marketplace

You can now purchase Postman Team and Enterprise plans directly through the AWS Marketplace, consolidating Postman within your existing AWS billing.

There are two ways to get started:

• Subscribe from the AWS Marketplace listing and complete setup on a Postman-hosted page.
• In the Postman app, click Buy with AWS to purchase without leaving Postman.

Both flows support purchasing for your own team or on behalf of another team in your organization. All subscription changes are managed through the AWS Marketplace console.

Available for net-new Team and Enterprise plans.

To learn more, see

Purchase AWS from AWS Marketplace.

Improvements

Better performance run links and output

Performance run links now point to the correct regional web host, so users in the EU are taken to the EU app instead of the US app. The CLI no longer opens a browser automatically for the live view. It prints the link instead, so you stay in the terminal. Performance runs now default to a one-minute duration, and the output includes hints for the default options.

YAML support for code mock configuration files

Support for writing code mock configuration files in YAML (.yaml or .yml) has been added to the CLI. Existing JSON configuration files continue to work without changes.

Search workspace documents

You can now search workspace documents from the CLI with the postman search command.

Bug Fixes

Fixed an issue where webhook commands did not recognize API key authentication.

Fixed an issue where postman workspace push could not resolve a spec’s path to its cloud ID and skipped the spec-to-collection link.