Postman Release Notes

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

Improvements

New options for postman flows run and postman flows trigger

Available on Enterprise plans

Two new options are now available for the Postman CLI flows commands:

Use the -e, --environment option with postman flows run to pass a Postman environment file at runtime, allowing the runner to hydrate environment variable values when executing your flows locally.

Use the -r, --result option with postman flows trigger to display only the response body from a triggered cloud flow run.

To learn more, see Flows commands.

Bug Fixes

Fixed an issue that caused postman workspace push to fail when using API key authentication. The command could fail because the workspace context was lost during the login step.

Fixed an issue where API key login was skipped if the provided key had a falsy value. The Postman CLI now correctly handles all provided API key values.

What’s New

Migrate collections from v2.1 to v3 format

The Postman CLI now supports the postman collection migrate command to migrate collections from v2.1 to v3 format.

Improvements

Sync connected local specifications and collections to the cloud

The postman workspace push command now supports syncing connected local specifications and collections to your workspace in the Postman cloud.

Bug Fixes

Fixed an issue that prevented local mock servers from starting when using postman mock run or postman collection run --mock.

Fixed an issue that caused the --color off option to not work with the postman collection run command.

What’s New

New Postman CLI commands for Flows

Available on Enterprise plans

You can now manage and monitor your flows directly from the Postman CLI with five new commands.

• Use postman flows list to view all flows available in your workspace.

• Use postman flows deploy to deploy a flow to the Postman cloud from the CLI.

• Use postman flows trigger to trigger execution of a deployed flow.

• Use postman flows list-runs to view the run history for a deployed flow. The command displays each run's timestamp, ID, duration, status, and flow name in a table. Use --workspace to specify your workspace (required), --flow to filter by a specific flow, and --range to set the time window for results (default: last 1 hour).

• Use postman flows get-run to inspect a specific run in detail. Use --logs to display the full event log, and --filter to narrow output by block ID.

To learn more, see Postman CLI command options.

Improvements

Improved gRPC schema resolution

Schema resolution for gRPC is now faster and more reliable.

Bug Fixes

Fixed an issue where gRPC schemas could get stuck for up to 30 seconds on some servers.

What’s New

Support for Private API Monitoring with runners

Available on Enterprise plans

With Private API Monitoring, the Postman CLI now supports monitoring your organization’s internal APIs behind a firewall or deployed in a restricted network. This means you can monitor internal APIs without exposing your endpoints to the public internet.

Use the postman runner start command to start a runner with your runner’s ID and key. Once running, the runner polls Postman for upcoming monitor runs. The collection and its tests run in your network and the results are sent back to the Postman cloud.

To learn more, see Monitor internal APIs with runners.

Support for running performance tests

The Postman CLI now supports configuring and running performance tests against collections in your team. Performance tests enable you to simulate real-world traffic to your APIs and automatically surface performance issues before changes reach production.

Use the postman performance run command to integrate performance tests into your CI/CD pipeline and ensure your APIs stay fast and reliable with every release. The Postman CLI sends the results to the Postman cloud to help you debug performance test results.

To learn more, see Run a performance test using the Postman CLI.

Support for mock servers …

What's New

Syntax validation for API specifications

The postman spec lint command now includes dedicated syntax validation. Previously, specs with syntax errors would display a generic message like "Unable to lint. Please check your specification for errors." Now you see the exact syntax errors with file names, line numbers, and clear descriptions—making it much easier to fix issues in your OpenAPI specifications.

New "Issue Type" column in output

Validation results now include an "Issue Type" column that distinguishes between Syntax errors (structural/parsing issues) and Governance violations (rule-based issues). This helps you quickly identify and prioritize what to fix first.

The new column is added at the end of CSV, JSON, and table outputs to maintain backward compatibility with existing CI/CD pipelines.

Fixed collection push failing due to owner ID mismatch

Fixed an issue where postman workspace push would fail to update collections when the resource ID format didn't include the expected owner prefix.

What’s New

Send HTTP requests from the command line.

The Postman CLI now includes a new postman request command that lets you send HTTP requests directly from the command line with full Postman capabilities. Use familiar Postman features like environment variables, authentication methods, pre-request and post-request scripts, and test assertions—all from your terminal.

Send a simple GET request

postman request https://api.example.com/users

Learn more about POST with authentication and environment variables.

What’s New

Private API monitoring with runners

Private API Monitoring is available as a beta feature on all paid plans. Enterprise teams must contact their Postman Customer Success Manager to enable Private API Monitoring.

You can now set up runners using the Postman CLI to monitor internal APIs within your own infrastructure. With runners, you can run monitors on your network without exposing internal endpoints to the public internet.

To start a runner, use the following command:

postman runner start --id <id> --key <key>

Once deployed, runners appear automatically in your monitor configuration and can be used to monitor APIs in restricted networks, isolated VPCs, or private data centers.

To learn more, see Set up a runner with the Postman CLI.