Postman Release Notes

What’s New

View a workspace’s activity feed

The postman workspace activity command shows who changed what in a workspace and when. It reads the workspace bound to the current folder or the workspace ID you pass. Filter the feed with --type, and add --json for machine-readable output.

Improvements

Run application tests in a CI/CD pipeline

The postman app test command doesn’t prompt for setup when there’s no interactive terminal, such as in a CI job. It uses the options you pass instead. When a collection or a test command is missing, the command exits with code 2 and names the options to pass.

Generate a collection from test traffic when you run application tests

The postman app test command accepts the --generate-collection option. It captures traffic from your application tests and generates a collection with a test for each captured API endpoint. The tests assert the status codes and response times observed during the capture, and the shape of each JSON response body. It then runs those tests.

Set up the collection and capture plugin in one step

The postman app test command accepts the --yes option. It generates a collection from test traffic and installs the capture plugin, each only when it isn’t already set up. Passing --generate-collection requests the same collection generation on its own.

Use your Playwright configuration without setting a test command

When you don’t pass the --command option, the postman app test command runs npx playwright test if it finds a Playwright configuration file. Previously you had to pass that command yourself.

Set up application test capture without prompts

The postman app setup-capture command accepts the --yes option to install the postman-playwright capture plugin and patch your Playwright configuration file without asking for confirmation. Outside an interactive terminal, the command makes no changes and exits with code 2 unless you pass --yes.

Preview capture setup before it changes files

The postman app setup-capture command accepts the --dry-run option. It shows the current capture setup and lists what the command would install or patch, and it changes no files.

Get an error exit code when capture setup finds no Playwright configuration

The postman app setup-capture command exits with code 1 when it finds no Playwright configuration file, with or without the --config option.

Use YAML manifests for mocks and simulations

The postman mock and postman simulation commands accept only YAML mock manifests. A .json manifest fails with “JSON mock manifests are not supported.” Convert it to .yaml. Previously both formats worked.

Pass --verbose to keep request detail in mock and simulation logs

The postman mock run and postman simulation run commands print one line for each request, plus any applied scenario or error. Pass --verbose to also print request and response headers and bodies. Previously every request printed that detail.

Pass --verbose to keep headers and bodies in ndjson request events

With --output ndjson, each request event from the postman mock run and postman simulation run commands carries the status code, duration, and any scenario or error. Pass --verbose to also include request and response headers and bodies. Previously every event included them.

Read more detail in ndjson request events

With --output ndjson, the request events from the postman mock run and postman simulation run commands add the responseSize, scenarios, and error fields.

Get a readable default slug when you deploy a mock or simulation

The postman mock deploy and postman simulation deploy commands build the default --slug from the mock’s name, such as orders-3f9c1a. A mock or simulation with no name gets new-mock- and six hexadecimal characters. Previously a nameless mock or simulation got a slug built from its ID.

List runners and regions in a guest session

The postman runner list and postman runner regions commands work in a guest session, which the postman init command creates. Previously, the commands stopped with an "Authentication required" error.

Bug Fixes

Fixed the postman collection publish command returning a documentation URL on an internal host that only resolves inside Postman’s network. The command returns the URL on documenter.getpostman.com.

Fixed the postman performance run command using excessive memory when requests with large bodies fail.

Fixed the postman app test command logging an incorrect outcome message after remote result ingestion.

What’s New

Delete a flow

The postman flows delete command deletes a flow in the Postman Cloud by its flow ID or a local flow by its file path. The command asks for confirmation unless you pass --yes.

Improvements

Lint a specification against a local Spectral ruleset

The postman spec lint command accepts the --ruleset option, so you can lint an OpenAPI or AsyncAPI specification against a Spectral ruleset on your machine. Custom functions are supported. The same sign-in and plan requirements apply as for linting with governance rules.

Generate mocks that keep state

The postman mock generate command accepts the --stateful option. For endpoints that map to create, read, list, update, and delete operations, the command generates handlers that store data with pm.state instead of returning static example responses.

Run performance tests in local mode

The postman performance run command now supports local mode, so you can pass the path to a local collection instead of a cloud collection ID. Whether the run is recorded in Postman depends on whether that collection is linked to a cloud collection in .postman/resources.yaml.

Use a Native Git-linked local collection with cloud runners

The postman performance run command accepts the path to a Native Git-linked local collection with the --runner postman-cloud and --runner postman-cloud-static-ip options.

Check whether a performance run was recorded in ndjson output

With --output ndjson, the postman performance run command adds a recorded field to the summary event, so you can tell whether a run was recorded in Postman.

Show the sign-in notice only when a performance run needs it

Previously, the postman performance run command prompted a logged-out user to sign in even when the run didn’t need a Postman account. The command now prints that notice only when part of the run reaches Postman Cloud.

Push local work automatically when you sign up as a guest

Previously, if you had local work that wasn’t pushed yet, the postman signup command warned you to run postman workspace push yourself. The command now pushes new work under postman/ to your guest workspace for you, so the workspace you keep isn’t empty.

Skip the push when you sign up

The postman signup command accepts the --no-push option to skip pushing local work to your guest workspace.

Protect headers and descriptions when syncing a collection

The postman spec sync collection command stops with exit code 8 and writes nothing when a local sync would remove headers or descriptions that the specification doesn’t generate, as it already did for scripts. Pass --force to overwrite anyway.

Preview a collection sync without writing files

The postman spec sync collection command accepts the --dry-run option, which lists the files a sync would write, marks any content the specification doesn’t generate, and writes nothing.

Write only changed files when syncing a collection

The postman spec sync collection command writes only the collection files that don’t already match the specification.

Save an HTML report for a flow run with a dataset

The postman flows run command accepts --reporters html for dataset runs, saving a report with the results for each row of the dataset view.

End the install script when the installed binary doesn’t run

The install script for macOS and Linux ends with an error when the installed postman binary doesn’t print a version.

Bug Fixes

• Fixed the install script for macOS and Linux writing through an existing bin/postman symlink, which left $HOME/.local/bin/postman as a symlink to itself.
• Fixed the postman performance run command with the cloud runners dropping the --pass-if verdict when only the teardown collection failed the run.
• Fixed the postman signup command reporting unpushed guest work for a fresh guest whose only local files were installed skills.
• Fixed the Claude Code plugin hint printing when you pass --json or --output, or when stdout or stderr isn’t a terminal.

Improvements

Lint a specification’s syntax without governance checks

The postman spec lint command accepts the --issueType option with the value syntax. The option limits linting to syntax checks and skips governance rules, and it works on a local specification file even when you aren’t signed in.

Linting a local specification requires signing in

When you aren’t signed in, the postman spec lint command stops with an error for a local specification file. The error tells you to run postman login, or to use --issueType=syntax to lint syntax only. Previously, the command ran the syntax checks and showed a sign-in notice instead.

Install the Postman CLI to a standard PATH location in CI

The install script for macOS and Linux installs the postman binary to /usr/local/bin when that location is writable without sudo. Otherwise, it installs to $HOME/.local/bin as before, and it never prompts for sudo unless you pass --system. Because /usr/local/bin is on the default PATH of most systems, the postman binary is found in later CI steps and Docker RUN lines.

Find the Postman CLI at a fixed path

After the install script runs, the Postman CLI is always reachable at $HOME/.local/bin/postman. This is because when the script installs the binary to another location, it adds a symlink at $HOME/.local/bin/postman pointing to the binary. This gives callers such as the Postman desktop app one fixed path to check.

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

The postman globals get command reads local workspace globals, or the globals of a workspace in the Postman Cloud when you pass --workspace. The postman globals var get, postman globals var set, and postman globals var unset commands read, set, and remove one global variable.

Improvements

Serve simulation mocks behind a local proxy

The postman simulation run command accepts the --proxy option to serve the mocks behind a local HTTP(S) forward proxy instead of one routed port. Point HTTP_PROXY and HTTPS_PROXY at the proxy to reach each mock by hostname without code changes. Use --proxy-port to set the proxy port.

Redact credentials in simulation request logs

The request log lines that the postman simulation run command prints redact query string values with credential-like names, such as token or api_key.

Enter secret values in a browser form

The postman secret create command opens a one-time browser form on your machine to enter the secret value. The command prints only the secret names and IDs, so an AI agent that runs the command only sees names and IDs. Use --terminal to enter the value in the terminal instead. The --value-stdin option reads the value from stdin and implies --terminal. Use --timeout to set how many seconds the command waits for the form.

Create several secrets in one command

The postman secret create command accepts several secret names when you use the browser form. The form shows one field for each name.

Choose the output format for performance runs

The postman performance list command accepts the --output option with the value table or json. The --json option is an alias for --output json.

Retry on server errors when syncing a workspace

The postman workspace push and postman workspace pull commands retry requests that fail with a server error, using increasing delays and up to two retries. After repeated failures, the command stops the operation instead of retrying.

Send private runner events through your proxy

The postman runner start command sends its usage events through the proxy that you set with --proxy or --egress-proxy.

Bug Fixes

Fixed the postman dataset source add help text implying that every database source needs a table. Without --table, the source connects to the whole database.

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

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

The postman environment new, list, get, and var set commands accept a guest session when you use them with an environment in a Postman Cloud workspace.

List local mocks by default

The postman mock list command now lists the file-backed mocks in your repository by default. To list the same mocks as seen from your cloud workspace, including their deployment status and public URL, pass the --workspace option. Previously, the command listed cloud workspace mocks by default.

Shape load test profiles with segments

The postman performance run command has new options for shaping the load profile. Use --load-segments to set how long each phase lasts, as a comma-separated list in order, such as --load-segments 1m30s,20s,40s. The ramp-up profile takes 2 values, spike takes 3, and peak takes 4. Use --base-vu to set the virtual users the run starts from and --peak-vu to set the peak. Run postman performance run --help to understand more about each profile.

Pull flows into your local workspace folder

The postman workspace pull command now includes flows in what it pulls from a workspace in the Postman Cloud. The Postman CLI rewrites each flow’s references to environments, saved requests, and sub-flows so they resolve against local files, making a pulled flow usable as-is.

Pass several conditions with --pass-if

Pass several conditions with --pass-if

The postman performance run command accepts multiple --pass-if options. The run passes only if every condition passes. Previously, a second --pass-if condition replaced the first.

See how many matched requests have assertions

The postman application test command shows how many matched requests have assertions and how many don’t, such as 5 matched (3 with tests, 2 without). The breakdown appears only when at least one matched request has no assertions. Previously, the output showed only the matched and not matched counts.

Bug Fixes

Fixed the postman collection run command not resolving Postman Shared Vault secrets linked to collection variables.

Fixed the postman flows run command failing to load a flow’s sub-flows when the flow sits inside a Postman workspace.

Fixed the postman application test --capture-only command failing or returning empty results on every run after the first. The command replaces the contents of the output directory on each run.

Fixed the postman performance run command misreading a --duration value that includes a unit. The command ignored the unit and read only the number as minutes, so 30s ran for 30 minutes and 1h ran for 1 minute. The --duration option accepts only a whole number of minutes, such as --duration 30, and the command returns an error for any other value.

Fixed the postman performance run command accepting --vu-count values that aren’t whole numbers. The command refuses them with an error.

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

Collections generated from an OpenAPI specification with the postman spec generate collection command produce repeatable values that respect schema constraints such as minimum, maximum, and enum. Example values were previously randomized on every run, which caused unnecessary file diffs and unreliable mock responses. Regenerating the same specification produces identical files, so drift checks and code reviews stay reliable.

Preserve custom scripts when syncing a specification

The postman spec sync collection command preserves your custom pre-request and post-response scripts, instead of silently overwriting them as before. A sync that would discard a changed script stops and lists the affected files.

Bug Fixes

Fixed an issue where certain CLI commands reported a false network error instead of the actual failure reason, which made problems harder to diagnose.

What’s New

See your team’s credit consumption with credit reports in Flows

Flows Analytics now includes a Credits report button that shows exactly how your credits are being used. Reports surface total credits, total executions, and active users, plus a Credits by Flow table you can filter by trigger type (HTTP, Triggers, Cloud Runs, Local Runs) and a per-user breakdown you can expand for more detail. Reports default to last month but can be switched to month-to-date, and can be downloaded as HTML or PDF. Available on all plans.

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

The

• --json

option is now supported on

• postman workspace push

,

• pull

,

• create

,

• prepare

,

• connect-git

, and

• disconnect-git

. Each command prints a structured result object, making workspace output easier to consume in scripts and CI/CD pipelines.

Bug Fixes

Fixed an issue where

• postman dataset query

exited with code 0 and produced no output when an underlying component couldn’t start. The command now surfaces the failure.

Fixed an issue where

• postman workspace list

didn’t carry the pagination cursor, which could return incomplete results in non-interactive environments.

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

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

The Postman CLI’s install scripts now add a short note to your Claude Code or Codex configuration, if you already use one, so a coding agent on the machine knows the CLI is available. The update preserves any existing instructions and never fails the install.

Bug Fixes

Fixed the postman workspace list command silently ignoring the --type option, returning every workspace.

Fixed the postman request and postman collection run commands resolving a blank YAML environment value to the literal string null instead of an empty string.

Fixed the postman collection run --iteration-data-dataset command printing a misleading "No authorization data found" message for local file-backed datasets, even though the run completed successfully.

Fixed the postman workspace push command to handle Postman collections in the legacy JSON format.

What’s New

Work with Postman using a coding agent

You can now connect Claude Code, Codex, Cursor, or OpenCode directly to Postman with the new Postman plugin. Postman now works wherever your coding agent does. Installing the plugin teaches your agent how to work with Postman the same way a developer would in the Postman app. From there, your agent can build against your API and sync its results to a Postman Workspace, all without opening the Postman app.

The Postman CLI powers this workflow behind the scenes, and the plugin routes to it automatically.

To learn more, see Use the Postman plugin for coding agents.

Improvements

Unified integrations hub

You can now browse, connect, and manage all Postman integrations from the Integrations page. The Integrations directory covers native integrations (Slack, Teams, Jira, GitHub), agent connectors (New Relic, Wiz), and legacy notification integrations (Datadog, PagerDuty, Splunk, Statuspage, webhooks) on the same page. Each integration has a full listing of features, links to documentation, and a media gallery. Existing integrations carry over automatically, nothing needs to be reconnected.

To learn more, see Integrate Postman with third-party solutions.

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

Fixed postman collection list so it defaults to your local project’s collections when you don’t pass --workspace. Previously it errored when no cloud workspace was configured.

Fixed the -o, --output option on the postman request command so it saves the complete response to the JSON file you name.

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

The postman mock run command records a durable start history for eligible runs, so CLI and CI runs appear under Previous starts in Postman alongside runs started from the desktop app. Runs started from a Postman Cloud ID record automatically. For a run started from a local path, pass --workspace <id> to record its history. Use --no-history to opt out. Recording is best-effort and never blocks the mock server.

Setup and teardown lifecycle collections for local performance runs

The --setup-collection and --teardown-collection options on postman performance run now work with --runner local, not only the Postman Cloud runners. Use them to prepare test data before a run and clean up state after it.

Bug Fixes

Fixed an issue where postman workspace diff didn’t show newly created mocks before their first push. Mocks that exist locally but aren’t yet in the Postman Cloud now appear in the diff as pending creation.

Fixed an issue where postman workspace push renamed a specification to index.yaml in the cloud, ignoring the name given to postman spec create -n. The user-specified name is now preserved.

Fixed an issue where mock response bodies contained unresolved type placeholders.

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.
• Fixed postman spec generate collection output so type placeholders resolve to typed default values, headers and parameters use the array shape the v2.1 collection format requires, and example names are sanitized.
• Fixed postman workspace lint reporting a governance API error as a per-specification warning on plans that do not include API Governance. The command now skips governance on those plans.
• Fixed the error a guest session receives when creating a workspace. The postman workspace create command explains that workspace creation requires an account and points to postman signup.
• Fixed postman collection request update --param so query parameters are written in the v3 queryParams shape and the request URL query string stays in sync.
• Fixed postman init refusing to run on a postman/mocks// directory that the CLI generated itself.