postman-cli 1.48.0 → 1.50.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-08-19" "v1.48.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-08-27" "v1.50.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -575,6 +575,12 @@ Push local workspace entities (collections, environments, specifications, and mo
 .TP
 .B workspace lint
 Lint the current local Postman workspace: its configuration (.postman/resources.yaml) plus every discovered entity. Use \-\-meta to lint only the configuration.
+.TP
+.B workspace pull
+Pull workspace entities from a Postman workspace into the local git\-native folder.
+.TP
+.B workspace connect-git
+Connect a Postman workspace to a local git repository.
 
 .SS "workspace list"
 List all available Postman Workspaces
@@ -662,6 +668,62 @@ Only lint the workspace configuration (.postman/resources.yaml); skip per\-entit
 .TP
 .B \-\-workspace\-id <value>
 The workspace ID to use for fetching governance rulesets. Defaults to the id in .postman/resources.yaml.
+.TP
+.B \-\-fix
+Apply safe autofixes to repairable workspace lint issues.
+
+.SS "workspace pull"
+Pull workspace entities from a Postman workspace into the local git\-native folder.
+
+.B Usage:
+[options] [workspaceId]
+
+.B Options:
+.TP
+.B \-y, \-\-yes
+Skip all confirmation prompts
+.TP
+.B \-\-source\-workspace <workspaceId>
+Pull from a different source workspace.
+.TP
+.B \-\-verbose
+Show detailed logging
+
+.TP Examples:
+
+Examples:
+  postman workspace pull
+      Pull from the workspace connected to the current directory's git remote
+  postman workspace pull <workspaceId>
+      Connect the workspace to the current directory's git remote and pull
+      from the workspace.
+  postman workspace pull \-\-source\-workspace <workspaceId>
+      Pull from another workspace
+
+
+
+.SS "workspace connect\-git"
+Connect a Postman workspace to a local git repository.
+
+.B Usage:
+[options] <workspaceId> [path]
+
+.B Options:
+.TP
+.B \-\-verbose
+Show detailed logging
+
+.TP Examples:
+
+Examples:
+  postman workspace connect\-git <workspaceId>
+      Register the current directory's git remote with the workspace and write the
+      local .postman/resources.yaml claim. Prerequisite for `pull` and `push`.
+  postman workspace connect\-git <workspaceId> ./services/api
+      Connect a specific folder. A folder below the repo root binds to its subpath,
+      so one repository can back several workspaces.
+
+
 
 .SS "performance"
 Manage performance tests on your collections.
@@ -706,20 +768,14 @@ Use a Postman Dataset as iteration data (with \-\-dataset\-view\-id)
 .B \-\-dataset\-view\-id <id>
 Dataset view to execute for iteration data (requires \-\-dataset\-id)
 .TP
-.B \-\-dataset\-offset <offset>
-Row offset into the view result (optional range)
-.TP
-.B \-\-dataset\-limit <limit>
-Max rows to fetch from the view (optional range)
-.TP
 .B \-\-dataset\-distribution <strategy>
-How rows map to VUs: round\-robin (default), pinned, random
+How rows map to VUs: round\-robin (default), fixed, random
 .TP
 .B \-\-postman\-api\-key <apiKey>
 API Key used to load the resources from the Postman API (Only supported in the US region, use 'postman login \-\-region' to authenticate instead)
 .TP
-.B \-\-cloud
-Execute the performance test on Postman Cloud (beta) (default: false)
+.B \-\-runner <runner>
+Runner to execute the performance test on (local or postman\-cloud) (default: )
 .TP
 .B \-\-pass\-if <condition>
 Pass condition in format: function(metric, value). 
@@ -913,14 +969,14 @@ Set flow inputs from JSON files (e.g. \-\-input\-file ./inputs.json \-\-input\-f
 .B \-s, \-\-scenario <name>
 Use a pre\-built scenario as flow inputs (by scenario name). Can be combined with \-\-input and \-\-input\-file to override values.
 .TP
-.B \-\-iteration\-data\-dataset <path>
-[BETA] Run the flow once per row of a local .dataset.yaml view. Requires \-\-iteration\-data\-view. Dataset columns feed the flow inputs (see \-\-map).
+.B \-\-iteration\-data\-dataset <pathOrId>
+[BETA] Run the flow once per row of a dataset view. Accepts a local .dataset.yaml path or a cloud dataset id (cloud requires login). Requires \-\-iteration\-data\-view. Dataset columns feed the flow inputs (see \-\-map\-column).
 .TP
 .B \-\-iteration\-data\-view <nameOrId>
 [BETA] Name or id of the view (within \-\-iteration\-data\-dataset) whose rows drive the run.
 .TP
-.B \-\-map <input=column>
-[BETA] Bind a flow input to a dataset column (e.g. \-\-map isActive=active). Repeatable. Inputs whose name matches a column bind automatically. (default: )
+.B \-m, \-\-map\-column <input=column>
+[BETA] Bind a flow input to a dataset column (e.g. \-m isActive=active). Repeatable. Inputs whose name matches a column bind automatically. (default: )
 .TP
 .B \-e, \-\-environment <path>
 Specify a path to a Postman Environment file (JSON or YAML)
@@ -928,6 +984,9 @@ Specify a path to a Postman Environment file (JSON or YAML)
 .B \-\-working\-dir <path>
 Specify the path to the working directory
 .TP
+.B \-\-no\-insecure\-file\-read
+Prevent reading dataset files situated outside of the working directory (applies to \-\-iteration\-data\-dataset)
+.TP
 .B \-\-verbose
 Show detailed information of flow run and each request (method, URL, assertions)
 .TP
@@ -965,6 +1024,9 @@ Example:
   postman flows run ./path/to/flow.json \-\-output json
   postman flows run ./path/to/flow.json \-\-reporters html
   postman flows run ./path/to/flow.json \-\-workspace <workspaceId>
+  postman flows run ./path/to/flow.json \-\-iteration\-data\-dataset ./users.dataset.yaml \-\-iteration\-data\-view "active\-users"
+  postman flows run ./path/to/flow.json \-\-iteration\-data\-dataset ./users.dataset.yaml \-\-iteration\-data\-view "active\-users" \-\-map\-column isActive=active
+  postman flows run ./path/to/flow.json \-\-iteration\-data\-dataset ./users.dataset.yaml \-\-iteration\-data\-view "active\-users" \-i region=us\-east
 
 
 
@@ -1766,24 +1828,33 @@ Run and manage local Postman mock servers.
 .B Subcommands:
 .TP
 .B mock generate
-Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected.
+Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint.
 .TP
 .B mock run
-Start a local mock server given a manifest file (JSON or YAML).
+Start a local mock server given a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
+.TP
+.B mock get
+Show a local mock's details and run status.
+.TP
+.B mock list
+List local mocks found under a directory.
+.TP
+.B mock delete
+Permanently remove a local mock artifact.
 
 .SS "mock generate"
-Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected.
+Generate a local, runnable mock from a Postman collection (v2.0/v2.1/v3 file, or a git\-native v3 collection directory) or an OpenAPI 3.0/3.1 spec file. The source type is auto\-detected. Omit the source to scaffold a sample mock with a GET /health endpoint.
 
 .B Usage:
-<sourcePath> [options]
+[sourcePath] [options]
 
 .B Options:
 .TP
 .B \-o, \-\-output <dir>
 Output directory for the mock (default: postman/mocks/<slug>)
 .TP
-.B \-\-name <name>
-Display name for the generated mock
+.B \-n, \-\-name <name>
+Display name for the generated mock. Optional with a source (derived from it); required when generating without a source.
 .TP
 .B \-\-port <port>
 Port the mock server should listen on (default: 4500)
@@ -1800,16 +1871,17 @@ Always exit with code 0, even on failure
 .TP Examples:
 
 Eg. postman mock generate ./my\-collection.json
-    postman mock generate "./postman/collections/My Collection" \-\-port 4010
+    postman mock generate \-\-name "My Mock"                  # sample mock with a GET /health endpoint
+    postman mock generate \-\-name "My Mock" \-\-port 4010      # sample mock, custom port
     postman mock generate ./openapi.yaml \-\-output ./postman/mocks/api \-\-port 4010
     postman mock generate ./my\-collection.json \-\-update ./postman/mocks/orders
 
 
 .SS "mock run"
-Start a local mock server given a manifest file (JSON or YAML).
+Start a local mock server given a manifest file (JSON or YAML), a mock directory (postman/mocks/<slug>), or a .js handler.
 
 .B Usage:
-<manifestPath>
+<pathOrDir>
 
 .B Options:
 .TP
@@ -1823,13 +1895,67 @@ Path to a globals file (JSON or YAML) for pm.globals
 Mock server port, or "auto" for an ephemeral one (default: configured port, falls back to an ephemeral one if busy).
 
 .TP Examples:
-Eg. postman mock run ./postman/mock\-manifest.json
+Eg. postman mock run ./postman/mocks/orders            # a mock directory
+    postman mock run ./postman/mock\-manifest.json
     postman mock run ./postman/mock\-manifest.yaml
     postman mock run ./manifest.json \-\-environment ./postman/environments/dev.yaml
     postman mock run ./manifest.yaml \-\-port auto        # OS\-assigned ephemeral port
     postman mock run ./manifest.yaml \-\-port 4600        # exact port, errors if busy
 
 
+.SS "mock get"
+Show a local mock's details and run status.
+
+.B Usage:
+<pathOrDir> [options]
+
+.B Options:
+.TP
+.B \-\-json
+Output the mock details as JSON instead of a table
+
+.TP Examples:
+
+Eg. postman mock get ./postman/mocks/orders
+    postman mock get ./postman/mocks/orders \-\-json
+
+
+.SS "mock list"
+List local mocks found under a directory.
+
+.B Usage:
+[pathOrDir] [options]
+
+.B Options:
+.TP
+.B \-\-json
+Output the mock list as JSON instead of a table
+
+.TP Examples:
+
+Eg. postman mock list
+    postman mock list ./postman/mocks
+    postman mock list ./postman/mocks \-\-json
+
+
+.SS "mock delete"
+Permanently remove a local mock artifact.
+
+.B Usage:
+<pathOrDir> [options]
+
+.B Options:
+.TP
+.B \-y, \-\-yes
+Skip the confirmation prompt
+
+.TP Examples:
+
+Eg. postman mock delete ./postman/mocks/orders
+    postman mock delete ./postman/mocks/orders \-\-yes
+    postman mock delete ./postman/mocks/orders/config.yaml \-\-yes
+
+
 .SS "application"
 Application\-level commands: initialise config and run tests.
 
@@ -1839,12 +1965,17 @@ Application\-level commands: initialise config and run tests.
 .B Subcommands:
 .TP
 .B application init
+[DEPRECATED] Use `postman app test` instead.
 Initialise a postman.config.cjs file with target collections, environment, and test command.
 .TP
 .B application test
 Run a command first (primary task), then match captured traffic against Postman collections and run assertions.
+.TP
+.B application setup-capture
+Install postman\-playwright and patch playwright.config.* to capture network traffic automatically via withPostman().
 
 .SS "application init"
+[DEPRECATED] Use `postman app test` instead.
 Initialise a postman.config.cjs file with target collections, environment, and test command.
 
 .B Usage:
@@ -1953,6 +2084,34 @@ Examples:
   postman app test \-\-capture\-only \-\-output ./my\-captured\-traffic/
 
 
+.SS "application setup\-capture"
+Install postman\-playwright and patch playwright.config.* to capture network traffic automatically via withPostman().
+
+.B Usage:
+[options]
+
+.B Options:
+.TP
+.B \-\-config <path>
+Path to playwright.config.* to patch (default: auto\-detect)
+
+.TP Examples:
+
+Detects the package manager (npm / yarn / pnpm / bun) from lockfiles,
+installs postman\-playwright as a dev dependency if needed, then
+wraps your Playwright config's default export with withPostman().
+
+If auto\-patching is not possible (unusual config patterns), the
+command prints manual setup steps instead.
+
+Examples:
+    postman app setup\-capture
+    postman app setup\-capture \-\-config apps/api/playwright.config.ts
+
+After setup, run your tests normally:
+    postman app test
+
+
 .SS "simulate"
 Start mock servers with simulated failure scenarios.
 
@@ -2729,6 +2888,9 @@ Show details for a webhook.
 .B webhook requests
 List, inspect, and replay requests received by a webhook.
 .TP
+.B webhook scripts
+Create or update scripts executed by a webhook.
+.TP
 .B webhook forward
 Forward incoming webhook requests to a local port.
 
@@ -2921,11 +3083,15 @@ Postman workspace ID (falls back to .postman/resources.yaml or .postman/config.j
 .TP
 .B \-\-api\-key <key>
 Postman API key
+.TP
+.B \-\-verbose
+Show script execution logs
 
 .TP Examples:
 
 Examples:
   postman webhook requests describe 0123456789abcdefghijklmno 11111111\-1111\-4111\-8111\-111111111111
+  postman webhook requests describe 0123456789abcdefghijklmno 11111111\-1111\-4111\-8111\-111111111111 \-\-verbose
 
 
 
@@ -2950,6 +3116,42 @@ Examples:
 
 
 
+.SS "webhook scripts"
+Create or update scripts executed by a webhook.
+
+.B Usage:
+[options] [command]
+
+.B Subcommands:
+.TP
+.B webhook scripts set
+Create or update a webhook script from a JavaScript or TypeScript file.
+
+.SS "webhook scripts set"
+Create or update a webhook script from a JavaScript or TypeScript file.
+
+.B Usage:
+[options] <webhookId> <scriptPath>
+
+.B Options:
+.TP
+.B \-\-event <event>
+Script event: onEvent or onResponse
+.TP
+.B \-w, \-\-workspace <workspaceId>
+Postman workspace ID (falls back to .postman/resources.yaml or .postman/config.json)
+.TP
+.B \-\-api\-key <key>
+Postman API key
+
+.TP Examples:
+
+Examples:
+  postman webhook scripts set 0123456789abcdefghijklmno ./on\-event.js \-\-event onEvent
+  postman webhook scripts set 0123456789abcdefghijklmno ./on\-response.js \-\-event onResponse
+
+
+
 .SS "webhook forward"
 Forward incoming webhook requests to a local port.
 
@@ -3242,6 +3444,30 @@ DB database name
 .B \-\-table <table>
 DB table name (optional)
 .TP
+.B \-\-ssh\-host <host>
+SSH bastion host
+.TP
+.B \-\-ssh\-port <port>
+SSH bastion port
+.TP
+.B \-\-ssh\-user <user>
+SSH bastion user
+.TP
+.B \-\-ssh\-private\-key <filepath>
+Path to the SSH private key. WARNING: the path is visible in `ps` output and shell history; key contents are read locally at execution time and are not stored in the dataset config.
+.TP
+.B \-\-ssh\-host\-key <publicKey>
+SSH bastion public host key
+.TP
+.B \-\-ssh\-host\-key\-vault\-id <id>
+Shared Vault ID containing the SSH public host key
+.TP
+.B \-\-ssh\-host\-key\-secret\-id <id>
+Shared Vault secret ID containing the SSH public host key
+.TP
+.B \-\-ssh\-insecure\-skip\-host\-key\-verification
+WARNING: disable SSH host\-key verification; use only for trusted local testing
+.TP
 .B \-\-slug <slug>
 Optional slug for the source
 .TP
@@ -3318,6 +3544,30 @@ Update DB database name
 .B \-\-table <table>
 Update DB table name
 .TP
+.B \-\-ssh\-host <host>
+Update SSH bastion host
+.TP
+.B \-\-ssh\-port <port>
+Update SSH bastion port
+.TP
+.B \-\-ssh\-user <user>
+Update SSH bastion user
+.TP
+.B \-\-ssh\-private\-key <filepath>
+Update the SSH private\-key file path. WARNING: the path is visible in `ps` output and shell history; key contents are read locally and are not stored in the dataset config.
+.TP
+.B \-\-ssh\-host\-key <publicKey>
+Update the SSH bastion public host key
+.TP
+.B \-\-ssh\-host\-key\-vault\-id <id>
+Update the Shared Vault ID containing the SSH public host key
+.TP
+.B \-\-ssh\-host\-key\-secret\-id <id>
+Update the Shared Vault secret ID containing the SSH public host key
+.TP
+.B \-\-ssh\-insecure\-skip\-host\-key\-verification
+WARNING: disable SSH host\-key verification; use only for trusted local testing
+.TP
 .B \-\-slug <slug>
 Update slug
 .TP

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.48.0",
+  "version": "1.50.0",
   "description": "Official Postman CLI - Command-line companion for API development, testing, and automation",
   "keywords": [
     "postman",
@@ -58,10 +58,10 @@
     "man/"
   ],
   "optionalDependencies": {
-    "@postman/pm-bin-macos-arm64": "1.48.0",
-    "@postman/pm-bin-macos-x64": "1.48.0",
-    "@postman/pm-bin-linux-x64": "1.48.0",
-    "@postman/pm-bin-linux-arm64": "1.48.0",
-    "@postman/pm-bin-windows-x64": "1.48.0"
+    "@postman/pm-bin-macos-arm64": "1.50.0",
+    "@postman/pm-bin-macos-x64": "1.50.0",
+    "@postman/pm-bin-linux-x64": "1.50.0",
+    "@postman/pm-bin-linux-arm64": "1.50.0",
+    "@postman/pm-bin-windows-x64": "1.50.0"
   }
 }