Postman Release Notes

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

Validate API dependencies from your Playwright tests

Available on Solo, Team, and Enterprise plans

You can now use the Application Inventory to track the applications you build, the external APIs they depend on, and the test coverage validating those dependencies. The Application Inventory integrates with your existing Playwright test suite to automatically capture API interactions and validate them against your Postman Collections. This catches issues UI assertions alone miss, like contract drift, silent backend errors, and missing or incorrect API calls.

To learn more, see Application Inventory overview.

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.

Improvements

Tag changelog entries with versions

You can now add version tags to your changelog to label and organize updates to your API specification. Tag the latest set of changes to group them under a specific version, view those changes in read-only mode, and share a direct link with your team.

To learn more, see Add a version tag to the changelog.

Bug Fixes

Fixed a regression introduced in app v12.7.6 where Evaluate, If, and Condition blocks stopped working in the Postman desktop and web app. Cloud-based flow runs were not affected.

Fixed an issue where Evaluate blocks would not execute with a ‘Result is undefined’ error message.

Fixed an issue in the HTTP Request block where input variables were being stripped when a path parameter used colon syntax (:resourceId) with a {{resourceId}} value, causing broken variable injection in flows.

What’s New

Introducing new SDK Generator languages: Kotlin, Ruby, and Rust

Available on Team and Enterprise plans

The Postman SDK Generator now supports three additional languages: Kotlin, Ruby, and Rust. Combined with existing support for TypeScript, Java, Python, C#, Go, PHP, and CLIs, you can now generate SDKs for your APIs in ten languages.

To learn more, see Generate SDKs in Postman.

Share API health with published monitor reports

Available on Solo, Team, and Enterprise plans

You can now publish read-only monitor reports that provide visibility into your API's uptime, performance, and recent run results. Anyone with the link can view the report in a browser without needing a Postman account or workspace access. This makes it easy to communicate API reliability to external stakeholders.

Published monitor reports show the last 30 monitor runs. Reports include the overall health status, success rate, and request-level details such as response times, status codes, and the number of test assertion failures. Monitor Editors can publish reports for monitors they have access to. On Enterprise plans, a Team Admin must approve requests to publish. Each monitor can have one published report at a time.

To learn more, see Share API health using monitor reports in Postman.

Bug Fixes

Fixed an issue where HTTP requests using form data would lose their Content-Type header when run in Flows local mode, causing different behavior from cloud mode.

When using Postman Flows with Native Git (Local) mode, the "Allow scripts to update environment variables" option is now available, closing a gap with Cloud mode where this setting already existed.

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.