Postman CLI release notes

Postman CLI v1.33.2

Bug Fixes

Fixed an issue that caused binary files to become corrupted during collection runs.

Fixed an issue that caused collection runs to complete before all output was fully written.

Postman CLI v1.33.1

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.

Postman CLI v1.33.0

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.

Postman CLI v1.32.0

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.

Postman CLI v1.31.3

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

The Postman CLI now supports using a mock server to run against your collection’s tests. This helps you validate your tests against the mocked responses of external APIs used in your service, both locally and in CI environments. With the Postman CLI, you can integrate a mock server into your CI/CD pipeline with the --mocks option when you run a collection with postman collection run.

You can also use the postman mock run command in your CI/CD pipeline to start a mock server as a dependency for your application or test suite. The mock server runs on the specified port until you stop it. This is useful for simulating an API server for your service or external tests.

To learn more, see Postman CLI command options.

Support for generating SDKs from collections and API specifications

The Postman CLI now supports generating client SDKs directly from your Postman collections or API specifications (such as OpenAPI). Generate production-ready SDKs in TypeScript, Python, and Java, making it easy to provide consumers of your API with idiomatic client libraries.

Use the postman sdk generate command with a collection ID, specification ID, local file, or publicly accessible URL as input. You can generate SDKs for one language at a time, multiple languages, or all supported languages at once using the --all flag. Generated SDKs are written to a configurable output directory (default ./sdks) with a subdirectory per language.

postman sdk generate <collection-or-spec-id> --language typescript python --output-dir ./sdks

To customize SDK generation, use the postman sdk init command to create a .postman/config.json configuration file where you can set the SDK name, version, authentication behavior, retry policies, and per-language options.

Additional SDK management commands are available:

• postman sdk list — List previous SDK builds for a collection or specification.
• postman sdk fetch — Download SDKs from a previous build by its build ID.
• postman sdk connect — Connect a collection to a GitHub repository for automated SDK pull requests. Once connected, use the --pr flag with postman sdk generate to automatically create pull requests with updated SDKs.

Support for running flows locally with the Postman CLI

Available on Enterprise plans

You can use the postman flows run command to run local flows without exposing private APIs and sensitive data to the Postman cloud. The postman flows run command has options to set input values, show run log information, and use values from a scenario.

To learn more, see Postman CLI command options.

Improvements

Support for multi-protocol collection runs

The postman collection run command now supports gRPC and GraphQL collection runs.

To learn more, see Postman CLI command options.

Postman CLI v1.29.5

Improvements

• Various internal enhancements were added in this release.

Postman CLI v1.29.1

Bug Fixes

Fixed an issue that caused the postman workspace push command to time out for large files.

Postman CLI v1.29.0

Improvements

• Internal and beta feature enhancements were added in this release.

Postman CLI v1.28.0

What's New

Support for running performance tests

Running performance tests using the Postman CLI is available as a beta feature.

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. With the Postman CLI, you can 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.

Postman CLI v1.27.0

What's New

Support for Linux ARM64

The Postman CLI now supports Linux ARM64.

Postman CLI v1.26.0

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.

Postman CLI v1.25.0

What’s New

Run saved requests in scripts with runners

Runners now support the pm.execution.runRequest method that enables you to reference and send requests from your collection's scripts.

Postman CLI v1.24.2

What’s New

Improvements to syncing local elements with workspaces

The postman workspace commands now support scanning local collection, environment, and specification directories for elements to sync with the Postman cloud. Collections now regenerate their IDs if there's a mismatch between workspaces.

Postman CLI v1.24.1

Bug Fixes

• Fixed memory stack overflow errors that caused runners to fail during long monitor runs.

Postman CLI v1.24.0

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.

Postman CLI v1.23.1

What’s New

Added support for linting specifications in EU-region.

Learn more about linting API specifications with the Postman CLI.

Postman CLI v1.23.0

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.

Postman CLI v1.22.0

What’s New

[BETA] Workspace Sync Commands

New workspace management commands have been introduced as a public beta to sync locally exported and saved collections and environments with Postman workspaces:

• postman workspace prepare – Prepares and validates local files for a cloud push.

• postman workspace push– Creates, updates, or deletes entities in the target workspace; validates IDs globally; updates local files with server-assigned IDs. (Also runs prepare first.)

Required Configuration

A new declarative config file .postman/config.json defines the workspace ID and entity paths (collections, environments, specs, flows).

For example:

{ "schemaVersion": "1", "workspace": { "id": "your-workspace-id" }, "entities": { "collections": ["./collections/name.postman_collection.json"], "environments": ["./environments/name.postman_environment.json"], "specs": ["./specs/name.yaml"] } }

Flags

• --no-prepare: Skip the prepare step.

• --yes: Bypass all prompts (for CI/CD use).

Postman CLI v1.21.0

What's New

Run saved requests in scripts

The pm.execution.runRequest method is now supported with the Postman CLI. When you use the method to reference a request in your pre-request and post-response scripts, the referenced request now runs when the collection run is triggered by the Postman CLI.

To learn more, see Use scripts to send requests stored in your collections.

Postman CLI v1.20.0

What’s New

Introducing the Postman CLI manual page

The Postman CLI now supports a manual page with a complete list of supported commands and options. Use the man postman command to return the manual page.

Support for linting API specifications by path to the root file

The Postman CLI now supports linting OpenAPI 3.0 specifications using a local file path to the root file. To run the command, use postman spec lint <path-to-root-file>. By default, the command lints specifications against API governance rules applied to all workspaces. Use the --workspace-id option to lint specifications against API governance rules applied to a particular workspace.

Postman CLI v1.19.4

Improvements

Improved welcome banner when signing in

When you sign in with the login command, the Postman CLI now displays your username, email, and team name.

Improved the npm package README file

Updated the README file in the Postman CLI npm package with more documentation to help you get started

Postman CLI v1.19.1

Bug Fixes

• Improved Unix installation script for enhanced portability and robustness.
• Fixed an issue that prevented linting all files in multi-file API specifications in Spec Hub.

Postman CLI v1.19.0

What's New

Support for signing in from the browser

The Postman CLI now supports securely signing in and authenticating with Postman from the browser. Use the postman login command, without the --with-api-key option, and Postman prompts you to sign in from the browser.

Support for running a monitor

The Postman CLI now supports running a monitor in your team. Use the postman monitor run command to run the monitor on the Postman cloud and return the results in the terminal. The results are also sent to your monitor's results in the Postman app.

Note: The Postman CLI now requires access to the https://gateway.postman.com domain. If your network has outbound restrictions, allowlist the domain before upgrading to the latest version.

Postman CLI v1.18.1

Bug Fixes

• Fixed issues with the --silent option during collection runs
• Deprecation warning for the --alias option

Postman CLI v1.18.0

What’s New

Support for specifying the EU region during authentication

The Postman CLI now supports using the --region eu option with the login command to specify that your instance of Postman is hosted in the EU region.

Postman CLI v1.17.2

Bug Fixes

Improved the automated region detection and login process to ensure greater reliability and resilience across diverse environments.

Postman CLI v1.17.1

What's New

Support for linting multi-file OpenAPI 3.0 specifications

Available on Enterprise plans

The Postman CLI now supports linting multi-file OpenAPI 3.0 specifications against your team's configured API governance rules. To run the command, use postman spec lint <spec-id>. Use the --fail-severity option to trigger an exit failure code for rule violations at or higher than the specified severity level: HINT, INFO, WARNING, or ERROR (default). Use the --output option to set the output format to either JSON or CSV.

Learn more about linting API specifications with the Postman CLI.

Postman CLI v1.17.0

What's New

• The Postman CLI now supports targeting the EU region.
• To use the EU region, simply log in with an EU region API key—the Postman CLI will automatically detect and display the current region in its output.
  • For commands that support supplying the API key in the command itself, using a key of the EU region will automatically make the Postman CLI use the EU region’s corresponding resources for that invocation.
• The following commands are currently available on the EU region:
  • postman collection run
    • Please note that the --integration-id option is not supported for this command as integrations are not available on the EU DC yet.

Security patches

• Postman runtime version has been upgraded to version 7.44.1 to address a security vulnerability.

Postman CLI v1.16.0

What's New

• The Postman CLI now supports linting Open API 3.0 API Specifications taking into consideration rules enforced via workspace groups as per the team's API Governance configuration.

• To use, execute: postman spec lint <spec-id>

Command Line Options

• --fail-severity [severity], -f This option allows the command to exit with a failure status if issues at or above the specified severity level are detected.
  Severity levels include: HINT, INFO, WARNING, ERROR (default).

• --output [format], -o This option lets you specify the output format of the linting results. This can be either json or csv.

Postman CLI v1.15.0

What's New

• Postman CLI can now run scripts with external packages – Import packages from npm and JSR in your scripts to enhance your testing and automation workflows.

Bug Fixes

• Improved SSL/TLS support for environments with intercepting proxies.

Postman CLI v1.14.1

Bug Fixes

• Fixed a compatibility issue on Intel-based macOS systems.

• Fixed exit code resolution in api lint and api publish commands.

Postman CLI v1.14.0

Bug Fixes

• api publish command now works on Windows by correcting the Git redirect path.

• The Postman CLI now resolves browser-native globals like crypto and TextEncoder reliably, ensuring scripts behave consistently across both the postman app and the CLI.

Postman CLI v1.13.1

What's New

• Users can now filter iterations and requests in HTML reports, making test result analysis easier. The available filters include options to view iterations with errors or test failures or only test failures as well as options to filter requests with errors or test failures or only errors.

• Users can now trace HTTP request failures in scripts at collection and folder levels in the new JSON reporter.

UI & UX Improvements

• Various design enhancements to make the HTML reports more intuitive, visually appealing, and user-friendly.

Postman CLI v1.13.0

What’s New

• We’re excited to announce that Postman CLI now also supports HTML as a built-in reporter, enabling you to generate local HTML reports for your collection runs seamlessly. Our other available reporters include JSON, JUnit and CLI. postman collection run <collection-id> --reporters html postman collection run <collection-id> -r html

Postman CLI v1.12.0

What’s New

• We’re excited to announce that Postman CLI now supports built-in reporters, enabling you to generate local reports for your collection runs seamlessly. Available reporters: JSON, JUnit and CLI. postman collection run <collection-id> --reporters json,junit,cli postman collection run <collection-id> -r json,junit,cli
• The JSON reporter introduces a new, compact schema that provides key information on the run execution and failures. Additionally, for workflows built around Newman, reports can also be generated with the Newman JSON schema using the following command. postman collection run <collection-id> -r json --reporter-structure newman

Postman CLI v1.11.0

What’s New

• Added support for await in top level scripts.

Postman CLI v1.10.2

Bug Fixes

• Improved reliability in loading packages.

Postman CLI v1.10.1

Bug Fixes

• Improved reliability in loading collections, environments, etc.
• Add additional logging for failures in loading test data and packages.

Postman CLI v1.10.0

Bug Fixes

• Improvements in loading collections, environments, etc, have been made, which will lead to fewer errors while loading them.

Postman CLI v1.9.0

What’s New

• Added support for publishing API versions with API definition files authored outside Postman for privately hosted repositories.
• You can now set the next request using pm.execution.setNextRequest(), instead of using the deprecated function postman.setNextRequest().

Postman CLI v1.8.0

What’s New

• You can now run collections that reuse code in scripts by leveraging Packages.

Postman CLI v1.7.1

Bug Fix

• Fixed a bug that was causing requests sent via pm.sendRequest to override the collection request URL in the run results summary.

Postman CLI v1.7.0

What’s New

• You can now run collections containing requests which use files directly from your Postman team. No more manually passing files back and forth with your teammates!

Postman CLI v1.6.0

What’s New

• You can now stop the execution of a particular request using pm.execution.skipRequest() in the pre-request script - #8929
• You can now access the name of the request, folder, or collection that’s executing the current script using pm.execution.location.current or the entire path using pm.execution.location - #6926

Postman CLI v1.5.0

What's New

• You can now lint AsyncAPI schemas using the Postman CLI.

Postman CLI v1.4.1

Bug Fixes

• We have added some improvements to address an identified vulnerability.

Postman CLI v1.4.0

What’s New

• You can now use JWT authentication and NTLMv2 authentication in requests while running collections on Postman CLI.
• You can now run collections with Promises and async/await statements in pre-requests and test scripts - #4131
• You can now run collections with requests that support comments in the raw body - #12379

Bug Fixes

• Fixed a bug where Postman CLI exits a run with an error in case one or more requests in the custom order of a collection run are not found. Postman CLI now gracefully handles the error, and such requests will fail to execute in the run.

Postman CLI v1.2.1

What's New

• We have added support for linting with Governance Custom Functions - #12191

Postman CLI v1.2.0

What's New

• postman api lint <api-id> now supports linting results taking into consideration rules enforced via workspace groups as per the team's API Governance configuration

Bug Fixes

• Fixed a bug where API publish was not working on Windows OS

Postman CLI v1.1.2

What's New

• Postman CLI now supports API version publish action
  • Running postman api publish <api-id> --name <version-name> will publish API contents

Postman CLI v1.1.1

What's New

• Postman CLI can now work with multiple APIs present in one repository
• Run postman api lint without an <api-id> argument
  • if only one API is present in the repo
    • lints the API and sends the result back to Postman (if the API utilizes Postman’s git integration and integration-id is provided)
  • if multiple APIs are present in the repo
    • lints all the APIs, but does not send the result back to Postman
• Results provided by the postman api lint command only support rules added to the “All workspaces” workspace group in Postman

Bug Fixes

• Fixed an issue with git error leaking in local collection runs - fatal: not a git repository (or any of the parent directories): .git