Postman CLI Updates & Release Notes

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.

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.

What’s New

Create and query datasets with the Postman CLI

Available as a beta feature

The Postman CLI now supports the postman dataset command for creating datasets, managing data sources, running SQL queries, and running saved views. Datasets enable you to work with reusable data from files and databases in local development and automation workflows, including CI/CD pipelines.

You can also use the --iteration-data-dataset , --iteration-data-view , and --dataset options with the postman collection run command to run collections using dataset-backed iteration data or make datasets available to collection scripts.

To learn more, see Dataset commands.

Improvements

Postman Flows cloud runs for non-Enterprise users

Postman Flows cloud runs are now available to non-Enterprise users. Users can run a deployed flow via postman flows run without needing a private runner, with improved error feedback.

Improvements

Automatic SDK version selection

The --sdk-version option is now optional in the postman sdk generate command. If omitted, Postman automatically determines the SDK version based on changes to the API specification, collection, or SDK Generator, and defaults to 1.0.0 for the first generation.

Bug Fixes

Fixed an issue where postman flows run could return a Missing required inputs error when a flow contained unconnected input ports.

Fixed an issue where using pm.environment in scripts would return undefined values incorrectly.

What’s New

Manage webhooks directly from the Postman CLI

You and your agents can now create, manage, and work with Postman webhooks directly from the Postman CLI using the postman webhook commands.

The Postman CLI supports creating, listing, and deleting webhooks in a workspace, along with viewing webhook status and starting or pausing them as needed.

You can also configure forwarding of events received on your webhook to your local server to support development and debugging using the postman webhook [Webhook ID or URL] forward [your-local-port] command.

Search mocks and environments with the Postman CLI

The Postman CLI now supports postman search mocks and postman search environments, making it easier to find and reference mocks and environments in your CI/CD pipelines, automation workflows, scripts, and AI agents.

Improvements

Save Postman Flows test results as an HTML report

When running flows from the CLI, you can now save test results as a self-contained HTML report by passing --reporters html to postman flows run. The report includes a summary of passed, failed, and skipped tests, per-block results, and full details for any failed assertions.

Improvements to reporting test runs in the Application Inventory

The postman app test command now supports the --report-events option for reporting test results and analytics from local test runs to Postman's Application Inventory.

Postman recommends using the --report-events option instead of CI=true.

Run flows that use the Response block's Send/Run input

Flows that use the new Send input on the Response block now run correctly from the Postman CLI. This input lets a Response block trigger a downstream block on a failed or conditional response without adding a separate HTTP Request block.

Bug Fixes

Fixed an issue that caused the postman app test command to return an OOM error when running large test suites.

What’s New

Improved output for Postman Flows test results

When running flows from the CLI, test results are now displayed in a clean, readable format instead of raw JSON.

Analyze specific test run artifacts

The postman app test command now supports passing a Playwright JSON report file directly with the --network-log option. This makes it easier to analyze a specific test run without relying on automatic artifact discovery.

To learn more, see Application commands.

Improved CI context detection for application testing

Application testing now more accurately detects CI context across local environments and GitHub workflows, including pull request and push-triggered runs. This helps ensure test results are correctly associated with the originating branch, commit, and workflow context.

Improvements

Live performance metrics for Postman CLI runs

Available on Solo, Team, and Enterprise plans

When you trigger a performance run using the postman performance run command, you can now stream live performance metrics in the Postman app as the test runs, either locally or from your CI/CD pipeline. This gives you real-time visibility into slow response times, failed assertions, and request errors as they occur. If the API becomes unstable under load, you can stop the test, adjust your configuration or API, and rerun without waiting for the full run to finish. This helps you catch and address issues early, preventing deployments that don't meet your performance requirements.

To learn more, see Configure and validate performance tests using the Postman CLI.

Bug Fixes

Fixed an issue where running postman sdk generate against a v3 Postman Collection could produce an empty items array.

What’s New

Simplified Playwright setup for Application Inventory

You can now enable network capture for Playwright tests with a single configuration change using withPostman in your playwright.config.ts file. This approach works across all pages, contexts, and fixtures without requiring changes to your test files. The Postman CLI automatically processes the resulting network capture output during test runs.

The existing attachNetworkCapture approach remains supported for teams that prefer test-level setup.

To learn more, see Integrate your test suite with the Application Inventory.

What’s New

Integrate your SDK generation with your GitHub repo

Available on Team and Enterprise plans

Use the updated postman sdk connect command to connect Postman SDK generation with your GitHub repo and automate subsequent SDK updates. Use postman sdk connections list and postman sdk connections delete to list and remove your GitHub connections, respectively. Automation is available on Enterprise plans only.

Bug fixes

Fixed an issue in Application Inventory where request matching didn't respect environment variables.

Fixed an issue where UI tests without network traffic were not being recorded in Application Inventory.

Improvements

Application testing improvements

The postman app test command includes several improvements:

Configuration is now validated before a run begins, and analytics are reliably sent when a run completes.

Network request failures captured during a run are propagated through the pipeline instead of being silently dropped.

The error message shown when no network traffic is captured is clearer.

Long request names are safely truncated to prevent filesystem errors.

To learn more, see Application commands.

Support for connector blocks when running flows

The postman flows run command now requires the --workspace option when your flow includes a connector block. Use the --workspace [workspace-id] option to specify the workspace by its ID.

To learn more, see Flows commands.

Improvements

Environment variable resolution for flows

The postman flows run command now resolves {{varName}} environment variables in scenario input values and configuration entries at runtime. Pass a Postman environment file using the --environment option and any variables referenced in your flow are substituted with their values. If a variable is referenced but missing from the environment file, the CLI returns an error identifying the unresolved variable by name.

To learn more, see Flows commands.

What’s New

Application testing and Playwright Integration

Available on Solo, Team, and Enterprise plans

Turn your existing Playwright tests into API contract validation with the new postman app commands. Use the postman app init command to initialize your project and configure your test command, collections, and environments. Use the postman app test command, paired with the postman-playwright plugin, to observe API traffic during Playwright runs, match each call to requests in your collections, and run your pm.test assertions against live responses. Results, unmatched calls, and coverage gaps are pushed to the Application Inventory in a single report.

To learn more, see Application commands.

Improvements

Improved output options for flows runs

The postman flows run command has two new options for controlling output. Use --output json to save execution results, including outputs and logs, to a timestamped JSON file in the current directory. This makes it easier to capture structured output for CI/CD pipelines and scripts. Use --no-truncate to display response bodies and payloads in full in the terminal. By default, truncation remains enabled so the terminal experience stays readable.

The --json option is no longer supported. Use --output json instead.

To learn more, see Flows commands.