Postman Release Notes

Improvements

Test results HTML report in Postman Flows

In Postman Flows you can now download your test results as an HTML report from the All Tests tab (in Run Logs and Analytics), alongside the existing formats.

New input added to Response blocks in Postman Flows

The Response block now has a Send input, letting a fail or conditional path trigger a response directly. This new Send input works both in the app and when running flows from the Postman CLI.

New Start block options in Postman Flows

When you create a new flow, the Start block gives you two new ways to jump right in:

• API example: instantly loads a ready-to-run flow that shows a request, a test, and the results displayed on the canvas, so you can see Flows in action right away.
• Create a Flow from collection: pick one of your collections and Flows automatically builds out the blocks for you, no manual setup needed.

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

Introducing service account identities for automation and integrations

Available on Enterprise plans

System service accounts give your team a dedicated, non-human identity for automation, integrations, and system-to-system interactions. Instead of tying CI/CD pipelines or backend services to a person's credentials, you can create a service account that represents the system itself with its own access controls, credentials, and audit trail.

To learn more, see

Manage service account identities for automation and integrations
.

Improvements

Improved visibility for syntax errors and governance issues in Spec Hub

Spec Hub now has a unified

Issues
tab below the specification editor, making it easier to view and navigate validation results. Syntax errors and governance rule violations are organized into expandable sections, with details and direct links to their location in your specification.

To learn more, see

Validate an API specification
.

Bug Fixes

Fixed an issue that prevented the Postman desktop app from booting properly on Windows machines.

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.