Postman CLI Updates & Release Notes

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

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

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

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.

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.

What’s New

AsyncAPI SDK generation from the CLI

You can now generate SDKs from AsyncAPI specifications directly using the Postman CLI. You can only generate SDKs in languages that support AsyncAPI, helping you avoid errors when selecting an output language.

List your workspaces from the CLI

You can now use the postman workspace list command to list all the Postman workspaces you have access to, showing each workspace’s ID, visibility type, and name. Use --filter to narrow results by name. You can add --json to return the results in JSON format.

Improvements

More reliable flow execution when collections are reorganized

The Postman CLI now runs flows correctly even when the requests they reference have been moved or renamed in a collection. Previously these runs failed with an error that the collection items could not be found, which blocked CLI automation and CI/CD workflows. This brings CLI flow runs in line with how the same flows already run in the Postman app. If a flow still reports this error, re-save it in the Postman app to update it to the current format.

Bug Fixes

Fixed an issue where streamed response bodies were dropped during flow capture preloading, which could cause incomplete data to be recorded during flow execution.

Improvements

Control how workspace elements sync to the cloud

The postman workspace push​ command now supports a --push-strategy option that gives you more control over how your local Git repository syncs to the Postman cloud. Use the --push-strategy force-sync option to mirror your local Git repository. This creates and updates elements in the Postman cloud, and also deletes elements from the cloud that have no local counterpart. When running in a CI/CD pipeline, you can pair force-sync with --yes to skip the interactive confirmation.

Scoped traffic filters for application test runs

Available on Solo, Team, and Enterprise plans

The filters configuration in postman.config.cjs now supports scoped array entries. Each entry in the array can target specific tests by file path or Playwright tag. This enables you to exclude different URLs, methods, and headers depending on which tests are running. Filters with no target or tags field apply to all tests.

The filters configuration still supports a single object that's applied to all tests.

Deprecated Features

Path options deprecated for workspace commands

The --collections-dir and --environments-dir options are deprecated for the postman workspace prepare and postman workspace push commands.

What’s New

Raw run data streaming for v3 collections

Available as a beta feature on Enterprise plans

You can now use the postman collection run command with the --output option to stream raw run data to YAML files on disk as each request finishes.

Manage webhook requests with the Postman CLI

The postman webhook requests command is now available to help you manage requests received by a webhook. You can list requests, inspect request details, and replay requests for testing and debugging.

Report CLI events to Postman

The postman collection run and postman spec lint commands now support a --report-events option that uploads run results and governance rule violations to Postman, where you can view them in the API Catalog.

Improvements

Richer Git metadata for application test runs

The postman app test command now automatically captures Git metadata for each test run, including commit information, tags, parent commits, git describe output, Git notes, and whether the working tree has uncommitted changes. This information is included with the run's analytics without requiring any extra configuration.

The captured metadata makes it easier to associate test runs with specific commits and releases. For example, you can identify release builds by tagged commits or use your own tag naming convention to determine which runs correspond to a release. In CI environments, the command also captures Git metadata from supported CI providers when available.

What’s New

Control automatic pull request creation

The postman sdk connect command now supports the --auto-update-pull-requests option to control whether pull requests are created automatically when the source changes or a new version of the SDK Generator is released. When this option is set to false, pull requests are created only when SDK regeneration is triggered manually.

If you don't specify the option, the default behavior depends on your Postman plan. It defaults to true for Enterprise plans and false for Team plans.

Prevent duplicate elements when pushing to a workspace

The postman workspace push command now helps prevent accidental duplicate Postman elements. If an element with the same name already exists in the Postman cloud, you're prompted to update the existing element, keep both, or skip it.

Improvements

Automatic npm publishing for generated SDKs

The postman sdk connect command no longer needs the --enable-publishing option. Generated SDKs now include the npm publishing workflow by default. To publish packages automatically, configure the required GitHub Actions secrets in the connected repository.

Improved logging for workspace commands

The postman workspace prepare and postman workspace push commands now support the --verbose option to display detailed logs, including API requests and responses, internal actions, and additional troubleshooting information. Error messages have also been improved to make issues easier to understand and resolve.

Bug Fixes

Fixed an issue where the postman collection run command could incorrectly skip requests containing valid path variables or query parameters.

Fixed an issue where pm.environment.name and pm.environment.id returned undefined in scripts.