Postman Release Notes

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.

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 …

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.

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.

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.

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.

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.

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.