Postman Release Notes

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 <name> 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 …

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 <flow-id> 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.

Specification lint support for the new API Governance experience

The postman spec lint command now also supports the new API Governance experience.

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. …

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.

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. …

What’s New

Edit and regenerate SDKs

You can now edit, add, or delete files in your SDKs and use the postman sdk generate command to regenerate the SDK.

To learn more, see Generate SDKs from collections and API specifications.

Enable change tracking for SDKs

The Postman CLI now supports the postman sdk track command to manage change tracking for SDKs created before the regenerate SDK option was available.

Support for HTTP Request blocks with tests in Flows

The Postman CLI now supports the v2 HTTP Request block when running flows locally with the postman flows command. This block adds tests as first class properties of the request.

Bug Fixes

Fixed an issue with the postman flows command where the Select block failed when passing structured input values using --input, --input-file, or --scenario. Input values are now correctly parsed as structured types, matching the behavior of the Postman canvas runner.

Fixed an issue with the postman flows command where request trigger outputs returned an empty map instead of the expected response data.

What’s New

Generate SDKs in Kotlin

You can now specify kotlin as a supported language when using the -l, --language option with Postman SDK commands. This enables you to generate Kotlin SDKs, and use them across supported workflows like fetching builds and connecting to GitHub.

To learn more, see SDK CLI commands.

Improvements

Specify folders using paths in collection runs

The -i option in the postman collection command now supports specifying folders with paths.

To learn more, see Collection commands.