Postman CLI release notes

Postman CLI v1.56.0

What’s New

Check and update agent skills

The new postman skills status and postman skills update commands keep an existing project’s agent skills current. The postman init command installs these skills, and they can fall behind the latest published version over time. Run postman skills status to check whether yours are behind, and postman skills update to refetch them, without having to re-run postman init.

Improvements

Redirect requests to a mock in performance tests

The postman performance run command now supports --use-mock, which redirects a variable or host to a local code mock or a cloud mock server during a run.

Supply Postman Local Vault secrets through environment variables

When you run postman collection run and a secret from your local vault can’t be resolved (for example, in CI), the CLI now reads that secret from a POSTMAN_VAULT_<key> environment variable, if you’ve set one.

Initialize your Native Git API project with the latest agent skills

The postman init command now fetches the agent skills it installs from the Postman skills repository instead of using copies built into the CLI. Use --no-fetch to install the built-in copies instead.

Have your AI agent build your API specification

The postman init command no longer generates an API specification from your source code. Instead, the installed SKILL.md guides your AI agent to build the specification from your code.

Connect a workspace during application test setup

When you run postman app test with result reporting (--report-events) enabled (the default) but no workspace is connected, the command now walks you through connecting one. In CI or non-interactive environments, it prints setup instructions and exits.

Postman CLI v1.55.0

What’s New

Sync flows with postman workspace push

The postman workspace push command now syncs flows to the linked Postman workspace, alongside your other workspace elements.

Improvements

Stronger SSRF protections in the monitoring runner

The postman runner start command now has stronger protections against server-side request forgery (SSRF). Addresses on your own internal network remain reachable.

Flat environment files for postman mock run

Thepostman mock run command now accepts flat key: value environment files (with -e), in addition to the Postman environment format.

Bug Fixes

• Fixed silent failures when loading an environment file with postman mock run -e. Loading a missing file, a parse error, or an unexpected shape now returns a clear, specific error.
• Fixed postman mock deploy resetting a redeployed mock server’s visibility and auto-deploy settings. If you didn’t pass --public, it would set visibility to private. If you didn’t pass --auto-deploy, it would set auto-deploy to off. It now keeps the existing settings and shows the current values and what changed.
• Fixed a newly created cloud mock showing a "source not available" placeholder in the editor. It now includes a default scenario and handler.
• Fixed API key validation for deployments that set POSTMAN_API_BASE_URL, so the CLI validates your key against your deployment’s base URL instead of the public region URLs.

Postman CLI v1.54.0

What’s New

Set up an AI-ready API project with postman init

The new postman init command sets up a Postman Native Git API project on your machine in one step. It can generate a starting API specification from your code and adds a SKILL.md that teaches agents how to build and test APIs with the Postman CLI. If you’re signed in, postman init offers to create a new Postman workspace and connect your project to it so you can collaborate with your team.

Create a Postman workspace with postman workspace create

The new postman workspace create command creates a Postman workspace and connects your local Git repository to it. You can then push your project to the workspace and pull updates back, so your team can collaborate on it in Postman. By default, it names the workspace after your Git remote and connects the current directory.

Run GraphQL and gRPC request blocks in Postman Flows

Available on Enterprise plans

The postman flows run command now runs GraphQL and gRPC request blocks, in addition to HTTP, using your existing authentication and environment settings. GraphQL request blocks support queries and mutations, but not subscriptions. gRPC request blocks support unary methods, but not streaming methods.

Improvements

Sync code mocks and simulations with postman workspace push

The postman workspace push command now syncs code mocks and simulations to the linked Postman workspace, matching the app’s Git sync.

Postman CLI v1.53.0

What’s New

Lint AsyncAPI specifications

The postman spec lint command now supports AsyncAPI specifications (versions 2.x and 3.x), in addition to OpenAPI. Provide an AsyncAPI document to validate it and identify any issues.

Manage cloud mocks

The postman mock commands now work with cloud mocks as well as local ones. Pass a mock’s ID to the get, run, or delete command to act on a cloud mock (a file path still targets a local mock). The list and generate commands accept a new --workspace option to list and create mocks in a Postman workspace.

Deploy a cloud mock to a mock server

Available on Solo, Team, and Enterprise plans

The new postman mock deploy <mockId> command publishes a cloud mock to a mock server. Run it interactively to set the mock server’s name, slug, and visibility, or pass those as options to deploy from a script.

Browse a mock server’s request history

Available on Solo, Team, and Enterprise plans

The new postman mock log <mockServerId> command shows a deployed mock server’s request and response history, newest first. Filter the entries by method, status, path, or time window with --method, --status, --path, --since, and --until. Use --limit to cap how many entries appear, or --json for machine-readable output. You can find the mock server ID with postman mock get.

Run setup and teardown collections in cloud performance tests

Available on Solo and Team plans

The postman performance run command accepts --setup-collection <id> and --teardown-collection <id> to run a collection before and after a performance test. These apply to Postman Cloud performance tests (--runner postman-cloud).

Postman CLI v1.52.0

Improvements

Analytics reporting is on by default

The Postman CLI now reports usage analytics to Postman by default across the commands that emit them. To opt out, pass --report-events=false.

Get syntax results even when governance rules can’t be applied

The postman spec lint command now returns syntax results even when it can’t apply governance rules, such as when you’re not signed in or the governance rulesets can’t be retrieved.

Postman CLI v1.51.1

What’s New

Work with datasets in the Postman CLI

Available on Solo, Team, and Enterprise plans

With the postman dataset commands, you can manage reusable test data, from static files to live databases, and use it to drive data-driven collection and performance runs from the Postman CLI, including in CI/CD.

Redirect requests to a mock during a collection run

The postman collection run command now supports a --use-mock option that redirects requests to a mock while the collection runs. Each mapping points a URL to a local mock (mock:<path or id>) or a deployed mock server (mock-server:<id>), and you can pass --use-mock more than once to redirect multiple URLs. When a mapping points to a local mock, the Postman CLI starts it for you.

Postman CLI v1.51.0

Bug Fixes

Fixed a regression in v1.50.0 that caused postman spec lint to fail for API Governance users migrated to the new experience.

Postman CLI v1.50.0

What’s New

Run performance tests in the Postman Cloud

Available on Solo and Team plans

The postman performance run command now supports a --runner option that selects where a performance test’s load originates. By default, load originates from the machine that invokes the command. Use --runner postman-cloud to generate load from Postman’s managed cloud infrastructure instead.

Use datasets in performance tests

Available on Solo, Team, and Enterprise plans

The postman performance run command now supports datasets as a test data source. Use --dataset-id and --dataset-view-id to select a dataset and view, and --dataset-distribution to control how rows are assigned to virtual users (round-robin, fixed, or random).

Connect a workspace to a Git repository

The new postman workspace connect-git command binds a Postman workspace to a Git repository on your machine. Connect the repository first, then use postman workspace push and postman workspace pull.

Pull a workspace to your local folder

The new postman workspace pull command pulls a workspace’s collections, environments, specifications, and other elements into your local Git repository. It is the counterpart to postman workspace push. If the Git repository isn’t already connected to the workspace, Postman creates the connection before pulling.

More ways to work with local mocks

You can now list, inspect, and delete local mocks with the new postman mock list, postman mock get, and postman mock delete commands. The postman mock generate command now generates a sample mock with a GET /health endpoint when you run it without a collection or specification file, providing a runnable starting point for you to edit.

Set up Playwright network capture automatically

The new postman app setup-capture command sets up Playwright network capture for you. It finds your Playwright config, installs the postman-playwright package, and wraps your config with withPostman(). The postman app test command also runs this as an interactive preflight check.

Improvements

Autofix workspace lint issues

The postman workspace lint command now has a --fix option that applies safe autofixes to repairable lint issues.

Bug Fixes

Fixed an issue where the JSON and HTML reports were missing run timings (run.meta.duration was null). Run timings are included again.

Postman CLI v1.49.0

What’s New

Lint your workspace before pushing

The postman workspace push command now runs a lint check before pushing. It blocks the push if your workspace configuration has lint errors, and skips any entity that has lint errors while still pushing the clean ones.

Set up application tests interactively

If you run postman app test without a configuration file or collections, the command now guides you through an interactive setup instead of exiting. You can select existing collections or generate a new collection from your test traffic, complete with auto-generated test scripts.

Author scripts and inspect script outcomes for webhooks

You can now author and update a webhook’s scripts with the new postman webhook scripts set command. The postman webhook requests describe command now includes a test report, and adding the --verbose option streams the script execution logs.

Improvements

Install-aware update instructions

When an update is available, the Postman CLI now detects whether it was installed with npm or as a direct download, and shows the matching update instructions.

Postman CLI v1.48.0

What’s New

Lint your entire local workspace

The postman workspace lint command lints your whole local workspace in one report: the workspace configuration plus every collection, spec, environment, and globals file. Use --meta to lint only the workspace configuration.

Track the deployed version in application tests

The postman app test command can now record which deployed version of your application each test run exercised, so you can correlate results with specific deployments. Provide the version with the --deployed-version option, or from your Playwright report metadata.

Bug Fixes

• Fixed an unclear error when a cloud performance run requested fewer virtual users than the minimum allowed. The postman performance run command now explains the minimum virtual-user requirement.
• Fixed an issue where a worker crash could stop a Private API Monitoring runner from processing runs. The runner now recovers automatically.

Postman CLI v1.47.2

What’s New

Generate API mocks from a Native Git collection directory

The postman mock generate command now accepts a directory containing a Native Git v3 collection, not just a single collection file. You can generate example-rich mocks straight from a Git-synced workspace.

Improvements

Push documents to your workspace

The postman workspace push command now syncs documents (Markdown files under postman/documents/), in addition to the collections, environments, specifications, and globals it already supported.

Faster, more secure installs

The macOS and Linux installers now prompt for your password once instead of several times. All three installers (macOS, Linux, and Windows) now verify the downloaded binary’s signature before installing.

Control the port for mock servers

The postman mock run command now supports a --port option. Pass a specific port, or use --port auto for a port assigned automatically. If you don’t set a port, the mock uses its configured port and falls back to an available one if that port is busy.

Bug Fixes

Fixed an issue where the postman mock run command served v3 example bodies as a raw { type, content } object instead of the example’s actual payload.

Postman CLI v1.47.0

What’s New

Generate a local code mock from a collection or spec

You can now generate a local code mock from a Postman collection or an OpenAPI spec with the new postman mock generate command. It needs no Postman account or network access to generate or run, so you can use it in CI/CD. Run the generated mock with postman mock run.

Improvements

Code mock responses now match the Postman app

Code mock examples now serve their actual response headers and content types instead of always using application/json. Simulated fault responses, such as chaos and error conditions, also return the same status code and body as the app.

Expanded Private API Monitoring runner support for collections

Private API Monitoring runners can now monitor collections that contain not just HTTP requests, but gRPC and GraphQL requests as well. Runners now also prefetch vault secrets in bulk at the start of a run for faster execution.

Postman CLI v1.46.1

What’s New

Generate Swift SDKs

You can now generate Swift SDKs with the Postman CLI, using postman sdk generate.

Lint local environment and globals files

You can now validate your environment and globals files with the new postman environment lint and postman globals lint commands.

Improvements

Push global variables to your workspace

Thepostman workspace push command now pushes your workspace’s global variables, in addition to the collections, environments, and specifications it already supported.

Bug Fixes

Fixed an issue where TypeScript code in flow Evaluate, If, and Condition blocks failed to run from the CLI. Scripts authored in TypeScript are now transpiled to JavaScript before they run, so type annotations no longer cause errors.

Postman CLI v1.46.0

Improvements

Better performance run links and output

Performance run links now point to the correct regional web host, so users in the EU are taken to the EU app instead of the US app. The CLI no longer opens a browser automatically for the live view. It prints the link instead, so you stay in the terminal. Performance runs now default to a one-minute duration, and the output includes hints for the default options.

YAML support for code mock configuration files

Support for writing code mock configuration files in YAML (.yaml or .yml) has been added to the CLI. Existing JSON configuration files continue to work without changes.

Search workspace documents

You can now search workspace documents from the CLI with the postman search command.

Bug Fixes

• Fixed an issue where webhook commands did not recognize API key authentication.
• Fixed an issue where postman workspace push could not resolve a spec’s path to its cloud ID and skipped the spec-to-collection link.

Postman CLI v1.45.0

What’s New

AsyncAPI SDK generation from the CLI

You can now generate SDKs from AsyncAPI specifications directly using the Postman CLI. You can only generate SDKs in languages that support AsyncAPI, helping you avoid errors when selecting an output language.

List your workspaces from the CLI

You can now use the postman workspace list command to list all the Postman workspaces you have access to, showing each workspace’s ID, visibility type, and name. Use --filter <name> to narrow results by name. You can add --json to return the results in JSON format.

Improvements

More reliable flow execution when collections are reorganized

The Postman CLI now runs flows correctly even when the requests they reference have been moved or renamed in a collection. Previously these runs failed with an error that the collection items could not be found, which blocked CLI automation and CI/CD workflows. This brings CLI flow runs in line with how the same flows already run in the Postman app. If a flow still reports this error, re-save it in the Postman app to update it to the current format.

Bug Fixes

Fixed an issue where streamed response bodies were dropped during flow capture preloading, which could cause incomplete data to be recorded during flow execution.

Postman CLI v1.44.0

Improvements

Control how workspace elements sync to the cloud

The postman workspace push​ command now supports a --push-strategy option that gives you more control over how your local Git repository syncs to the Postman cloud. Use the --push-strategy force-sync option to mirror your local Git repository. This creates and updates elements in the Postman cloud, and also deletes elements from the cloud that have no local counterpart. When running in a CI/CD pipeline, you can pair force-sync with --yes to skip the interactive confirmation.

Scoped traffic filters for application test runs

Available on Solo, Team, and Enterprise plans

The filters configuration in postman.config.cjs now supports scoped array entries. Each entry in the array can target specific tests by file path or Playwright tag. This enables you to exclude different URLs, methods, and headers depending on which tests are running. Filters with no target or tags field apply to all tests.

The filters configuration still supports a single object that's applied to all tests.

Deprecated Features

Path options deprecated for workspace commands

The --collections-dir and --environments-dir options are deprecated for the postman workspace prepare and postman workspace push commands.

Postman CLI v1.43.0

What’s New

Raw run data streaming for v3 collections

Available as a beta feature on Enterprise plans

You can now use the postman collection run command with the --output option to stream raw run data to YAML files on disk as each request finishes.

Manage webhook requests with the Postman CLI

The postman webhook requests command is now available to help you manage requests received by a webhook. You can list requests, inspect request details, and replay requests for testing and debugging.

Report CLI events to Postman

The postman collection run and postman spec lint commands now support a --report-events option that uploads run results and governance rule violations to Postman, where you can view them in the API Catalog.

Postman CLI v1.41.2

Improvements

Improved CLI error output for application test runs

The postman app test command now displays clearer, more informative error messages in the CLI output to help you identify and resolve issues more quickly.

Postman CLI v1.41.1

Improvements

Richer Git metadata for application test runs

The postman app test command now automatically captures Git metadata for each test run, including commit information, tags, parent commits, git describe output, Git notes, and whether the working tree has uncommitted changes. This information is included with the run's analytics without requiring any extra configuration.

The captured metadata makes it easier to associate test runs with specific commits and releases. For example, you can identify release builds by tagged commits or use your own tag naming convention to determine which runs correspond to a release. In CI environments, the command also captures Git metadata from supported CI providers when available.

Postman CLI v1.41.0

What’s New

Control automatic pull request creation

The postman sdk connect command now supports the --auto-update-pull-requests option to control whether pull requests are created automatically when the source changes or a new version of the SDK Generator is released. When this option is set to false, pull requests are created only when SDK regeneration is triggered manually.

If you don't specify the option, the default behavior depends on your Postman plan. It defaults to true for Enterprise plans and false for Team plans.

Prevent duplicate elements when pushing to a workspace

The postman workspace push command now helps prevent accidental duplicate Postman elements. If an element with the same name already exists in the Postman cloud, you're prompted to update the existing element, keep both, or skip it.

Improvements

Automatic npm publishing for generated SDKs

The postman sdk connect command no longer needs the --enable-publishing option. Generated SDKs now include the npm publishing workflow by default. To publish packages automatically, configure the required GitHub Actions secrets in the connected repository.

Improved logging for workspace commands

The postman workspace prepare and postman workspace push commands now support the --verbose option to display detailed logs, including API requests and responses, internal actions, and additional troubleshooting information. Error messages have also been improved to make issues easier to understand and resolve.

Bug Fixes

• Fixed an issue where the postman collection run command could incorrectly skip requests containing valid path variables or query parameters.

• Fixed an issue where pm.environment.name and pm.environment.id returned undefined in scripts.

Postman CLI v1.40.0

What’s New

Create and query datasets with the Postman CLI

Available as a beta feature

The Postman CLI now supports the postman dataset command for creating datasets, managing data sources, running SQL queries, and running saved views. Datasets enable you to work with reusable data from files and databases in local development and automation workflows, including CI/CD pipelines.

You can also use the --iteration-data-dataset, --iteration-data-view, and --dataset options with the postman collection run command to run collections using dataset-backed iteration data or make datasets available to collection scripts.

To learn more, see Dataset commands.

Improvements

Postman Flows cloud runs for non-Enterprise users

Postman Flows cloud runs are now available to non-Enterprise users. Users can run a deployed flow via postman flows run <flow-id> without needing a private runner, with improved error feedback.

Postman CLI v1.39.1

Improvements

Automatic SDK version selection

The --sdk-version option is now optional in the postman sdk generate command. If omitted, Postman automatically determines the SDK version based on changes to the API specification, collection, or SDK Generator, and defaults to 1.0.0 for the first generation.

Specification lint support for the new API Governance experience

The postman spec lint command now also supports the new API Governance experience.

Bug Fixes

• Fixed an issue where postman flows run could return a Missing required inputs error when a flow contained unconnected input ports.

• Fixed an issue where using pm.environment in scripts would return undefined values incorrectly.

Postman CLI v1.39.0

What’s New

Manage webhooks directly from the Postman CLI

You and your agents can now create, manage, and work with Postman webhooks directly from the Postman CLI using the postman webhook commands.

The Postman CLI supports creating, listing, and deleting webhooks in a workspace, along with viewing webhook status and starting or pausing them as needed.

You can also configure forwarding of events received on your webhook to your local server to support development and debugging using the postman webhook [Webhook ID or URL] forward [your-local-port] command.

Search mocks and environments with the Postman CLI

The Postman CLI now supports postman search mocks and postman search environments, making it easier to find and reference mocks and environments in your CI/CD pipelines, automation workflows, scripts, and AI agents.

Improvements

Save Postman Flows test results as an HTML report

When running flows from the CLI, you can now save test results as a self-contained HTML report by passing --reporters html to postman flows run. The report includes a summary of passed, failed, and skipped tests, per-block results, and full details for any failed assertions.

Improvements to reporting test runs in the Application Inventory

The postman app test command now supports the --report-events option for reporting test results and analytics from local test runs to Postman's Application Inventory.

Postman recommends using the --report-events option instead of CI=true.

Run flows that use the Response block's Send/Run input

Flows that use the new Send input on the Response block now run correctly from the Postman CLI. This input lets a Response block trigger a downstream block on a failed or conditional response without adding a separate HTTP Request block.

Bug Fixes

Fixed an issue that caused the postman app test command to return an OOM error when running large test suites.

Postman CLI v1.38.1

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.

Postman CLI v1.38.0

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.

Postman CLI v1.37.0

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.

Postman CLI v1.36.0

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.

Postman CLI v1.35.2

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.

Postman CLI v1.35.1

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.

Postman CLI v1.35.0

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.

Postman CLI v1.34.5

Bug Fixes

Fixed an issue in the postman flows run command where environment variables were overriding request variables defined in the HTTP Request block.

Postman CLI v1.34.4

Bug Fixes

Fixed an issue that caused postman workspace push --yes to create new collections or environments when an update request returned a transient 404, instead of failing safely.

Fixed an issue where environment IDs in .postman/resources.yaml were rewritten from the canonical <owner>-<uuid> format to a bare UUID, causing subsequent pushes to fail.

Fixed an issue where pushing collections could result in an "invalid mode" error.

Postman CLI v1.34.3

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.

Postman CLI v1.34.1

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.

Postman CLI v1.34.0

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.

Postman CLI v1.33.6

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.

Postman CLI v1.33.4

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.

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