Postman CLI Updates & Release Notes

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.

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 Ruby

Introduced support for Ruby in the scope of SDK generation.

To learn more, see SDK CLI commands.

Configure Agent Skills with CLI SDKs

You can control whether Agent Skills are generated with the postman sdk generate command for a CLI SDK. Use the sdk.languageOptions.cli.skills object in your .postman/config.json file.

The skills object has an enabled Boolean field that determines whether Agent Skills are generated. This value defaults to true if not specified or left empty.

To learn more, see SDK CLI commands.

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.

What’s New

Generate CLIs from your Postman Collection or API specification

Available on Team and Enterprise plans

You can now generate a fully-functioning command-line interface (CLI) application based on your Postman collections or OpenAPI specifications. The Postman CLI has been enhanced with two main end-users in mind: Agents (LLMs) and humans.

To learn more, see Generate CLI from your collection or specification.

Specify input data for Postman Flows

You can now use the --scenario option with the postman flows trigger command to specify a named scenario from the flow definition to construct the input payload, headers, and query parameters.

To learn more, see Flows commands.

What’s New

Generate SDKs in PHP, Go, and C#

Introduced support for PHP, Go, and C# in the scope of SDK generation. Previously, the Postman CLI supported SDK generation in Python, Typescript, and Java. Now, you can use CLI to generate SDKs in six languages.

To learn more, see SDK CLI commands.

Validate collections in v3 format

The Postman CLI now supports the postman collection lint command to verify that a collection matches the v3 YAML format.

To learn more, see Collection commands.