Postman CLI Updates & Release Notes

What’s New

List the secrets in a workspace’s Shared Vault

The postman secret list command lists the secrets in a workspace’s Postman Shared Vault. It shows each secret’s key, secret ID, vault ID, and allowed domains, and never shows the secret’s value. Pass the secret ID and vault ID to postman environment var set to link an environment variable to a secret.

Delete a collection

The postman collection delete command deletes a collection by its collection ID or a local collection by its directory path. The command asks for confirmation unless you pass --yes.

Delete an environment

The postman environment delete command deletes an environment by its environment ID or local environment file path. The command asks for confirmation unless you pass --yes.

View a workspace dependency

The postman dependency get command shows a workspace dependency declared in .postman/resources.yaml. Use --type to match only collection, environment, or mock dependencies.

Get a performance run by its run ID

The postman performance get command shows one performance run by its run ID. Use --output to choose the format. It accepts table, which is the default, or json. The --json option is an alias for --output json.

Read and update global variables …

What’s New

Create, run, and manage simulations with a new command

The postman simulation command replaces the postman simulate command. Use the new command family to create, list, get, run, push, deploy, and delete simulations. The postman simulation run command serves all the mocks on one port. The now deprecated postman simulate run command used to open a port for each mock.

Improvements

Install Postman CLI without sudo

The install script for macOS and Linux installs to $HOME/.local/bin by default and doesn’t prompt for sudo. Use --prefix to choose another location or --system to install system-wide. Previously, the script installed to /usr/local and used sudo when that location wasn’t writable.

Run postman init without prompts

The postman init command accepts the --yes option to take the default for every question instead of asking or stopping. The command also creates and binds a workspace with personal visibility unless you set another value with the --visibility option. When used in CI, the command doesn’t create a workspace.

Use guest sessions with specification commands

The postman spec list, get, create, and delete commands and the postman spec file commands accept the guest session that the postman init command creates.

Use guest sessions with environment commands …

What’s New

Read requests and folders in a collection without exporting it

The postman collection request get and postman collection folder get commands print a single request or folder from a collection, either locally or from the cloud. You can inspect an item before changing it instead of reading collection files by hand.

View a single specification file

The postman spec file get command prints the contents of one file from a specification without reading the whole specification. This helps you review contract details from the terminal.

Create a secret in your team’s Shared Vault

The postman secret create command adds a secret to your team’s Postman Shared Vault. This streamlines secure credential management as part of your automation and CI workflows.

Create and manage examples under a request

The postman collection example command family lets you add, update, get, list, and remove examples (saved responses) under a request. It works on local v3 collections or cloud collections.

Improvements

Schema-valid values when generating collections from OpenAPI …

What’s New

Run a subset of requests in a monitor

You can configure a monitor to run a subset of its collection’s requests instead of the full collection. Pass -i, --item <id> (repeatable) to postman monitor create or postman monitor update to list the requests or folders to include, in the order you want them to run. On postman monitor update, --clear-items resets the selection so the monitor runs every request again.

Import a collection from a curl command or HAR file

The new postman collection import <src> command creates a Postman Collection from a curl command or a HAR file.

Improvements

View a scenario’s endpoints for a mock

The postman mock get command now lists the endpoints for every scenario associated with a mock, not only the default one. This enables you to discover and use non-default scenario endpoints without leaving the CLI.

SSL options and a cookie jar for a request

The postman request command now accepts SSL configuration and cookie jar options. This gives you more control over request behavior when working with secured endpoints or session-based APIs.

Lint warning for request file names

The postman collection lint command warns when a .yaml or .yml request file in a collection folder doesn’t use the required .request.yaml suffix. This helps you catch misnamed request files before you run the collection.

JSON output for more workspace commands …

What’s New

Publish collection documentation to the cloud

The postman collection publish command publishes a cloud collection’s public documentation, making it visible to anyone, or requests Community Manager approval when your workspace requires it. Configure the publish with --environment, --title, --description, and --note, and add --json for machine-readable output.

Improvements

See full request and response details while a mock runs

The postman mock run command now streams the same detailed request and response log as postman mock log, with secrets redacted. Pass --output ndjson for a machine-readable event stream instead.

Every worksheet in a spreadsheet becomes its own dataset source

The postman dataset source add command now adds every worksheet in a spreadsheet (xlsx, xls, ods) as its own queryable datasource, named source_<worksheet>.

Keep a request’s URL and query parameters in sync

The postman collection request update command now updates a request’s stored query parameters to match whenever you pass the --url option with a new query string. The postman collection lint command now flags a request whose query parameters and URL don’t match.

Installers add Postman CLI awareness for coding agents …

What’s New

Delete a specification

The postman spec delete command removes a specification by its cloud ID or local file path. Pass -y or --yes to skip the confirmation prompt, and --api-key to authenticate when you delete by cloud ID. Deleting a specification can’t be undone.

Remove a workspace dependency

The postman dependency remove command removes a workspace dependency and deletes its local files. Identify the dependency by its cloud ID, display name, or on-disk name from the postman dependency list command. Removing a collection also removes the environments pinned to it, unless another collection pins them too.

Improvements

Protect an existing collection from being overwritten

The postman spec generate collection command no longer overwrites an existing local collection, so it can’t erase the test scripts you added to it. To regenerate and replace that collection on purpose, pass --force.

Use datasets in a mock’s request handlers

The postman mock run command accepts a --dataset option that loads one or more local .dataset.yaml files, or directories of them. The mock’s request handlers can then read them with pm.datasets(<id>). Pass --dataset more than once to load several.

Bug Fixes

• Fixed the postman request command so a response with a non-2xx or non-3xx status code exits with code 1. …

What’s New

Delete a workspace from the CLI

The postman workspace delete <workspaceId> command permanently deletes a workspace and everything in it.

Disconnect a workspace from Git

The postman workspace disconnect-git [workspaceId] command removes the Git integration from a workspace without leaving the CLI. It disconnects the workspace in Postman and clears the connection in .postman/resources.yaml. No local files are deleted. With no ID, it disconnects the workspace this folder’s connected to. Pass --yes to skip the confirmation prompt in CI.

Two-way sync between specifications and collections

You can now keep a specification and its generated collection linked and regenerate either side on demand. The postman spec generate collection <spec> command creates a collection from a specification and records the link. The postman spec sync collection <spec> command regenerates the collection from its linked specification. In the other direction, postman collection generate spec <collection> creates an OpenAPI specification from a collection, and postman collection sync spec <collection> regenerates the specification from its linked collection. Both directions work in local and cloud modes.

Improvements

Mock run history is recorded …

What’s New

Add, update, and remove collection folders

The postman collection folder add, postman collection folder update, and postman collection folder rm commands manage folders inside a collection, both locally and in the Postman Cloud. Pass the collection with --collection <id|name> and scope to a subfolder with --folder. The add command creates an empty folder. The update command changes a folder’s name, description, auth, or scripts. The rm command removes a folder. Add --workspace to edit a cloud collection, or work against local git-native files by default. All three support --json.

Improvements

Run collection commands in a guest session

The postman collection list and postman collection get commands run in a guest session.

Bug Fixes

• Fixed the postman init --json command exiting with a success code when the requested workspace was not created. It now exits non-zero and runs the workspace step when --visibility asks for one.
• Fixed the missing interactive header and preflight error output on postman performance run. The Live view link and the --data-file validation error are restored on the default --output auto path.
• Fixed postman spec create --spec-version rejecting full versions such as 3.0.3. Patch versions are accepted for OpenAPI and AsyncAPI, and Swagger 2.0 reports a clear message because it defines only 2.0. …

What’s New

Add, update, and remove a collection’s requests

The new postman collection request commands let you add, update, and delete the requests in a local v3 collection. Pass --workspace to work on a collection in the Postman Cloud instead.

List the teams in your organization

The new postman team list command lists the teams inside your organization. For example, you can use it to find a team’s ID for a command like postman workspace create.

Send feedback about the Postman CLI

The new postman feedback command lets you, or an agent, submit feedback about CLI usability, gaps, and suggestions.

postman context is now postman describe

Available as a beta feature

The postman context command has been renamed to postman describe. The command does the same thing as before, fetching API context for AI coding agents. The rename is designed to avoid potential human and agent confusion with the unrelated postman context-graph command. Please update any scripts or automation that call postman context to use postman describe instead.

Improvements

See a new project’s layout as a file tree

The postman init command now prints the files it generates as a file tree. This means you can see the project’s shape at a glance instead of a flat list of paths. Machine-readable output (--json) is unchanged.

Clearer reminder when you’re working as a guest …

What’s New

Ask natural-language questions about your team’s APIs

The postman context-graph ask and status commands let you ask natural-language questions about the APIs and dependencies indexed in your team’s Context Graph. Run ask with --wait to get the answer inline, or without it to get an ID you check later with status. For example, postman context-graph ask "What depends on billing-api?" --wait submits a question, and postman context-graph status <id> checks on a question you asked earlier. Add --json to either command for machine-readable output.

Change or remove a monitor’s environment

The postman monitor update command accepts -e, --environment <id> to set or replace the environment a monitor runs its collection with. You can use --clear-environment to run it with no environment. Previously, you could choose the environment only when creating the monitor.

Get details for a single workspace

The new postman workspace get command fetches one workspace by ID and prints its details, such as its visibility, the team that owns it, and its timestamps. It’s read-only, so it’s a safe way to inspect workspace metadata in scripts and automation.

List a collection’s past performance runs

The new postman performance list command lists a collection’s past performance test runs, newest first, so you can review history and track trends. Specify the collection with its ID.

Create and manage JDBC dataset sources …

What’s New

See per-request latency history for a monitor

The new postman monitor metrics command shows a monitor’s per-request latency and outcomes, grouped by request and region. Use it to see which request is slow or failing and how its behavior has trended over time.

Preview local workspace changes before pushing

The new postman workspace diff command shows the differences between your local workspace and your Postman Cloud workspace, so you can preview what a postman workspace push would change. Use this read-only command to review drift before you push.

Generate a collection from a specification

The new postman spec generate collection command creates a Postman collection from an OpenAPI specification. Use --folder-strategy to group endpoints into folders by Paths (default) or Tags. Pass a local file path to generate the collection on disk, or a cloud spec ID to generate it in the Postman Cloud.

Scaffold collections and environments

The new postman collection new and postman environment new commands create an empty collection or environment locally. You can pass --workspace to create the element in a Postman Cloud workspace instead.

Get and list collections …

What’s New

Create, schedule, and manage monitors

New postman monitor and postman runner commands let you manage monitors from the command line, not just run them. Create a collection-based monitor with a cron schedule and time zone, choose where it runs, and set failure notifications, retries, and run options. Update, pause, resume, delete, list, and get monitors, and inspect a monitor’s jobs and runs. The postman monitor run command gains --async, which returns the run’s job ID and Postman URL without waiting for the run to finish. The postman runner list and regions commands show your self-hosted runners and the valid region and runner values.

List, install, and update dependencies

New postman dependency list, install, and update commands inspect and materialize your project’s declared dependencies: list shows the dependencies in .postman/resources.yaml, install materializes them into postman/.dependencies/, and update refreshes them to the latest content.

Create and edit API specifications …

What’s New

Manage environments

New postman environment commands let you work with Postman environments from the command line: list environments, read an environment, and set, read, or remove individual variables. The commands work with local environment files and cloud environments referenced by ID. Add --json for machine-readable output.

List your API specifications

The postman spec list command lists API specifications. Pass a path to scan local specification files (OpenAPI or AsyncAPI) on disk, or run it without a path to list the specifications in your Postman workspace. The output includes specification names, IDs, types, and root files. Add --json for machine-readable output.

Get a full API specification

The postman spec get <spec> command reads a specification’s full definition by ID or local file path, including every file in a multi-file specification. It prints a summary of the specification, including its name, type, file count, and root file. It also lists each file the specification contains, showing its path, type (root or supporting file), size, and content. Add --json for machine-readable output.

Add workspace dependencies …

What’s New

Check and update agent skills

The agent skills that postman init installs can fall behind the latest published version over time. The new postman skills status and postman skills update commands check for newer versions and fetch them, without re-running postman init. When you work with an AI agent, the installed SKILL.md instructs the agent to keep the skills current for you, updating them with your approval.

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.

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 …

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.

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.

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 …

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.