postman-cli 1.66.0 → 1.67.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-09-28" "v1.66.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-29" "v1.67.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -287,12 +287,12 @@ Migrate a v2.1 collection to the v3 format
 .B collection lint
 Run linting on a local v3 collection at the given file or directory path.
 .TP
-.B collection ai-readiness
-Score a Postman collection for AI readiness by ID, local file path, or local\-mode directory.
-.TP
 .B collection get
 Fetch a Postman collection in the V3 format and print it.
 .TP
+.B collection publish
+Publish a cloud collection's documentation (or request Community Manager approval).
+.TP
 .B collection generate
 Generate artifacts from a collection.
 .TP
@@ -371,53 +371,65 @@ Exit with failure if diagnostics at this level or above are present. [choices: "
 .B \-r, \-\-reporter <value>
 Output format: cli (human\-readable) or json. (default: cli)
 
-.SS "collection ai\-readiness"
-Score a Postman collection for AI readiness by ID, local file path, or local\-mode directory.
+.SS "collection get"
+Fetch a Postman collection in the V3 format and print it.
 
 .B Usage:
-<collectionId/Path> [options]
+[options] <id>
 
 .B Options:
 .TP
-.B \-o, \-\-output <value>
-Output format for the results. [choices: "cli", "json", "html"]
-.TP
-.B \-\-export <path>
-Write the report to this file instead of stdout. A directory receives the report under a name derived from the collection. Requires \-\-output html.
+.B \-\-api\-key <key>
+Postman API key (defaults to your `postman login` session)
 .TP
-.B \-\-min\-score <n>
-Exit with a non\-zero code if the overall score is below this threshold (0\-100).
+.B \-\-json
+Print the collection as machine\-readable V3 JSON instead of a table
 
 .TP Examples:
 
-Examples:
-  $ postman collection ai\-readiness ./postman/collections/My\e API
-  $ postman collection ai\-readiness ./my\-collection.json
-  $ postman collection ai\-readiness 631643\-f695cab7\-... \-\-output json
-  $ postman collection ai\-readiness ./my\-collection.json \-\-output html > report.html
-  $ postman collection ai\-readiness ./my\-collection.json \-\-min\-score 70
-
-Resolving a collection by ID requires authentication. Use `postman login` before running this command with a UID.
+Eg. postman collection get 12345\-33823532ab9e41c9b6fd12d0fd459b8b
+    postman collection get 0123456789abcdef01234567 \-\-json
 
 
-.SS "collection get"
-Fetch a Postman collection in the V3 format and print it.
+.SS "collection publish"
+Publish a cloud collection's documentation (or request Community Manager approval).
 
 .B Usage:
-[options] <id>
+[options] <collection\-id>
 
 .B Options:
 .TP
+.B \-\-target <name>
+Where to publish (default: documentation) (default: documentation)
+.TP
+.B \-\-environment <environment\-id>
+Cloud environment UID to bind to the docs
+.TP
+.B \-\-title <seo\-title>
+SEO title meta tag (max 120 characters)
+.TP
+.B \-\-description <seo\-description>
+SEO description meta tag (max 320 characters)
+.TP
+.B \-\-note <text>
+Note for Community Managers (request\-to\-publish only)
+.TP
 .B \-\-api\-key <key>
 Postman API key (defaults to your `postman login` session)
 .TP
 .B \-\-json
-Print the collection as machine\-readable V3 JSON instead of a table
+Machine\-readable JSON on stdout (errors on stderr)
 
 .TP Examples:
 
-Eg. postman collection get 12345\-33823532ab9e41c9b6fd12d0fd459b8b
-    postman collection get 0123456789abcdef01234567 \-\-json
+Cloud only — pass a collection UID, not a local path or name.
+
+Examples:
+  postman collection publish 12345\-33823532\-ab9e\-41c9\-b6fd\-12d0fd459b8b
+  postman collection publish <collection\-id> \-\-title "Orders API" \-\-description "Public Orders reference"
+  postman collection publish <collection\-id> \-\-note "Ready for Q3 review."
+  postman collection publish <collection\-id> \-\-json
+
 
 
 .SS "collection generate"
@@ -563,13 +575,16 @@ Folder to scope the request selector, e.g. "Users/Admin" (local: name/path; clou
 Rename the request (moves its file). Any request type.
 .TP
 .B \-\-url <url>
-Request URL. Any request type.
+Request URL; its query string becomes the query parameters. Any request type.
 .TP
 .B \-\-method <method>
 HTTP method (http requests only).
 .TP
 .B \-\-param <key:value>
-Replace query parameters. Repeatable (http requests only). (default: )
+Replace all query parameters and the url query string. Repeatable (http requests only). (default: )
+.TP
+.B \-\-clear\-params
+Remove all query parameters and the url query string (http requests only).
 .TP
 .B \-d, \-\-body <body>
 Request payload (inline, @file, or \- for stdin), interpreted by request type. For http, an optional "<type>:" prefix picks the content type: json/text/xml/html/javascript, file:<path>, urlencoded:key=v&k2=v2, or formdata:key=v&file=@path.
@@ -600,10 +615,12 @@ JSON output.
 
 .TP Examples:
 
-Works on any request type; \-\-rename/\-\-url/\-\-description/\-\-headers/\-\-auth/\-\-scripts apply to all, while \-\-method/\-\-param/\-\-body are http\-only. Select the request by the <request> selector: local — a name or "Folder/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a request id, with \-\-collection an id too.
+Works on any request type; \-\-rename/\-\-url/\-\-description/\-\-headers/\-\-auth/\-\-scripts apply to all, while \-\-method/\-\-param/\-\-clear\-params are http\-only and \-\-body is interpreted per type. \-\-param and \-\-clear\-params apply after \-\-url. Select the request by the <request> selector: local — a name or "Folder/Name" path (or \-\-folder to scope a bare name); cloud (\-\-workspace) — a request id, with \-\-collection an id too.
 
 Examples:
   postman collection request update "Get user" \-\-collection "My API" \-\-url "{{baseUrl}}/users/:id"
+  postman collection request update "List" \-\-collection "My API" \-\-url "{{baseUrl}}/orders?limit=99"
+  postman collection request update "List" \-\-collection "My API" \-\-clear\-params
   postman collection request update "Get user" \-\-collection "My API" \-\-folder Users \-\-rename "Fetch user"
   postman collection request update "Get user" \-\-collection "My API" \-\-headers "Authorization:Bearer x" \-\-auth bearer:TOKEN \-\-scripts "test:@check.js"
   postman collection request update <requestId> \-\-collection <collectionId> \-\-url "..." \-w <workspaceId>
@@ -854,13 +871,13 @@ Define the number of iterations to run
 Specify a data file to use for iterations (either JSON or CSV)
 .TP
 .B \-\-iteration\-data\-dataset <pathOrId>
-[BETA] Path to a .dataset.yaml (local collection) or a cloud dataset id (cloud collection) whose view drives the iteration data. Mutually exclusive with \-\-iteration\-data. Requires \-\-iteration\-data\-view.
+Path to a .dataset.yaml (local collection) or a cloud dataset id (cloud collection) whose view drives the iteration data. Mutually exclusive with \-\-iteration\-data. Requires \-\-iteration\-data\-view.
 .TP
 .B \-\-iteration\-data\-view <nameOrId>
-[BETA] Name or id of the view to execute (within \-\-iteration\-data\-dataset). The view's result set drives one iteration per row.
+Name or id of the view to execute (within \-\-iteration\-data\-dataset). The view's result set drives one iteration per row.
 .TP
 .B \-\-dataset <pathOrDir>
-[BETA] Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to collection scripts and local mock handlers as pm.datasets(<id>). When provided, auto\-discovery of .dataset.yaml files from the collection's parent repo is disabled. For a cloud collection, scripts address cloud datasets by id via pm.datasets(<id>) (resolved from your `postman login` session). SECURITY: for a cloud collection this does NOT scope access — a script can pm.datasets(<anyId>) for any dataset your session can read. Only run collections you trust against a logged\-in cloud session. (default: )
+Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to collection scripts and local mock handlers as pm.datasets(<id>). When provided, auto\-discovery of .dataset.yaml files from the collection's parent repo is disabled. For a cloud collection, scripts address cloud datasets by id via pm.datasets(<id>) (resolved from your `postman login` session). SECURITY: for a cloud collection this does NOT scope access — a script can pm.datasets(<anyId>) for any dataset your session can read. Only run collections you trust against a logged\-in cloud session. (default: )
 .TP
 .B \-i <id>
 Specify the request/folder id, name, or path to run from the collection. Use a path (e.g. "FolderName/RequestName") to disambiguate items with the same name. Can be specified multiple times to run multiple items (default: )
@@ -1424,10 +1441,6 @@ Lint and validate Specifications from the command line
 .B spec lint
 Run linting on the given specification by ID or local file path.
 
-.TP
-.B spec ai-readiness
-Score an OpenAPI specification for AI readiness by ID or local file path.
-
 .TP
 .B spec list
 List local spec files under a path, or (no path) a workspace's cloud specs.
@@ -1474,34 +1487,6 @@ Accepted for compatibility; analytics are sent by default
 .B \-\-no\-report\-events
 Do not send analytics to Postman
 
-.SS "spec ai\-readiness"
-Score an OpenAPI specification for AI readiness by ID or local file path.
-
-
-.B Usage:
-<spec> [options]
-
-.B Options:
-.TP
-.B \-o, \-\-output <value>
-Output format for the results. [choices: "cli", "json", "html"]
-.TP
-.B \-\-export <path>
-Write the report to this file instead of stdout. A directory receives the report under a name derived from the specification. Requires \-\-output html.
-.TP
-.B \-\-min\-score <n>
-Exit with a non\-zero code if the overall score is below this threshold (0\-100).
-
-.TP Examples:
-
-Examples:
-  $ postman spec ai\-readiness ./openapi.yaml
-  $ postman spec ai\-readiness 6e2e5b3e\-...  \-\-output json
-  $ postman spec ai\-readiness ./openapi.yaml \-\-output html > report.html
-  $ postman spec ai\-readiness ./openapi.yaml \-\-output html \-\-export ./report.html
-  $ postman spec ai\-readiness ./openapi.yaml \-\-min\-score 70
-
-
 .SS "spec list"
 List local spec files under a path, or (no path) a workspace's cloud specs.
 
@@ -3975,6 +3960,9 @@ Workspace that owns the run, for recording its start history. Auto\-resolved for
 .B \-\-no\-history
 Do not record this run in the mock's start history.
 .TP
+.B \-\-output <format>
+Live output format: auto (default, human\-readable logs) or ndjson (one JSON event per line on stdout, ending with a "summary" event — for CI or other non\-interactive use) (default: auto)
+.TP
 .B \-\-dataset <pathOrDir>
 Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to the mock's handlers as pm.datasets(<id>). (default: )
 
@@ -3985,6 +3973,7 @@ Eg. postman mock run 12345678\-90ab\-cdef\-1234\-567890abcdef  # by id, from Pos
     postman mock run ./postman/mocks/orders \-\-environment ./postman/environments/dev.environment.yaml
     postman mock run ./postman/mocks/orders \-\-port auto    # pick any free port
     postman mock run ./postman/mocks/orders \-\-port 4600    # use port 4600 (fails if it is in use)
+    postman mock run ./postman/mocks/orders \-\-output ndjson # stream machine\-readable events
     postman mock run ./postman/mocks/orders \-\-workspace <id>  # record start history for a path run
     postman mock run ./postman/mocks/orders \-\-dataset ./postman/datasets/Orders
 
@@ -5631,7 +5620,7 @@ Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 .B Options:
 .TP
 .B \-q, \-\-query <sql>
-SQL query to execute (e.g. "SELECT * FROM source_users LIMIT 10")
+SQL query to execute (e.g. "SELECT * FROM users LIMIT 10")
 .TP
 .B \-s, \-\-source <nameOrIdOrSlug>
 Execute directly against a database datasource; without \-\-source, use federated SQLite
@@ -5651,10 +5640,10 @@ Include safe classified dataset diagnostics
 .TP Examples:
 
 Examples:
-  postman dataset query ./users.dataset.yaml \-q "SELECT * FROM source_users LIMIT 5"
+  postman dataset query ./users.dataset.yaml \-q "SELECT * FROM users LIMIT 5"
   postman dataset query ./users.dataset.yaml \-\-source warehouse \-q "SELECT * FROM users LIMIT 5"
   postman dataset query ./users.dataset.yaml \e
-    \-q 'SELECT * FROM source_users WHERE id = $1 AND active = $2' \-p 42 true
+    \-q 'SELECT * FROM users WHERE id = $1 AND active = $2' \-p 42 true
   postman dataset query 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT * FROM users LIMIT 5"
 
 
@@ -5783,19 +5772,19 @@ Add a datasource to a dataset.
 Dataset to add the source to; positional target is also accepted for v1.45 compatibility
 .TP
 .B \-n, \-\-name <name>
-Logical name for the source (becomes the SQL table name)
+Logical name for the source (becomes the SQL table name). Required for every source except a spreadsheet, whose worksheets are each named source_<worksheet>
 .TP
 .B \-\-source\-id <uuid>
 Override the generated source id (local dataset only)
 .TP
-.B \-\-format <csv|json|mysql|postgres|sqlserver>
-Use this format instead of extension/type inference; file contents are not sniffed
+.B \-\-format <csv|json|xlsx|xls|ods|jdbc|mysql|postgres|sqlserver>
+Use this format instead of extension/type inference; file contents are not sniffed. A spreadsheet (xlsx/xls/ods) is added as one source per worksheet, each named source_<worksheet>
 .TP
 .B \-\-type <local|mysql|postgresql|sqlserver|jdbc>
 Source kind; local is inferred from \-\-file, jdbc from \-\-driver\-jar
 .TP
 .B \-\-file <path>
-Path to a local CSV/JSON file (absolute or cwd\-relative)
+Path to a local CSV/JSON/spreadsheet file (absolute or cwd\-relative)
 .TP
 .B \-\-ref\-only
 Reference the file in place; do NOT copy into data_dir (local dataset)
@@ -5804,7 +5793,7 @@ Reference the file in place; do NOT copy into data_dir (local dataset)
 When copying, overwrite an existing file at the destination (local dataset)
 .TP
 .B \-\-upload
-Cloud dataset only: upload \-\-file as a postmancloudfile source (runs via /exec). Without \-\-upload, \-\-file is registered as a local_filesystem csv/json source read by the local engine.
+Cloud dataset only: upload \-\-file as a postmancloudfile source (runs via /exec). Without \-\-upload, \-\-file is registered as a local_filesystem source read by the local engine. Either way a cloud dataset takes csv/json only — add a spreadsheet to a local .dataset.yaml, where each worksheet becomes its own source.
 .TP
 .B \-\-driver\-jar <path...>
 JDBC driver JAR(s). Repeatable, or pass several after one flag
@@ -5960,6 +5949,11 @@ Connection test:
 JSON output (\-\-json):
   Success: {"ok":true,"source":{"id","name","target","format","driver",
             "urlTemplate","connectionTest"},"warnings":[...]}
+  Spreadsheet: also "sources":[{"id","name","worksheet","table"}] — one entry
+            per worksheet, however many there are, with "source" set to the
+            first. "table" is the identifier to query: the engine collapses
+            "_" runs and drops leading and trailing "_", so it can differ
+            from "name".
   Failure: {"ok":false,"error":{"code","message","remediation",...context}}
   Both go to stdout, so `\-\-json 2>/dev/null | jq .` parses either way.
   Error codes: DRIVER_FILE_NOT_FOUND, DRIVER_CLASS_NOT_FOUND,
@@ -5968,10 +5962,13 @@ JSON output (\-\-json):
   VAULT_REFERENCE_INVALID,
   VARS_FILE_UNREADABLE, VARS_FILE_INVALID, SOURCE_NOT_FOUND, SOURCE_NOT_JDBC,
   JAVA_NOT_FOUND, JAVA_UNSUPPORTED, DRIVER_LOAD_FAILED, CONNECTION_FAILED,
-  CONNECTION_TIMEOUT, SECRET_RESOLUTION_FAILED, INVALID_ARGUMENT
+  CONNECTION_TIMEOUT, SECRET_RESOLUTION_FAILED, INVALID_ARGUMENT,
+  SPREADSHEET_DESCRIBE_FAILED, SPREADSHEET_NO_WORKSHEETS,
+  SPREADSHEET_UNIT_NOT_PINNED, SOURCE_ID_AMBIGUOUS,
+  SPREADSHEET_CLOUD_UNSUPPORTED, WORKBOOK_FORMAT_UNSUPPORTED
   Warning codes: PLAINTEXT_SECRET, CONNECTION_NOT_TESTED, NO_VARIABLES,
-  EMPTY_VARIABLE_VALUE, NAME_NOT_SQL_SAFE, TRUST_SERVER_CERTIFICATE,
-  SSH_VALUES_IN_ARGV, SSH_HOST_KEY_UNVERIFIED
+  EMPTY_VARIABLE_VALUE, NAME_NOT_SQL_SAFE, NAME_UNUSED_FOR_SPREADSHEET,
+  TRUST_SERVER_CERTIFICATE, SSH_VALUES_IN_ARGV, SSH_HOST_KEY_UNVERIFIED
   LOCAL_VAULT_UNSUPPORTED, SOURCE_NAME_CONFLICT, SOURCE_ID_CONFLICT and
   DATASET_FILE_CHANGED are also possible; DATASET_COMMAND_FAILED is the
   fallback for anything unclassified.
@@ -6015,8 +6012,8 @@ Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset
 .B \-n, \-\-name <name>
 Rename the source
 .TP
-.B \-\-format <csv|json|mysql|postgres|sqlserver>
-Change the format (local dataset only; cloud source formats are immutable)
+.B \-\-format <csv|json|jdbc|mysql|postgres|sqlserver>
+Change the format (local dataset only; cloud source formats are immutable). A spreadsheet format is not offered here: this command changes the format field alone and cannot pin a worksheet, so the source would not compile. Add the workbook with `dataset source add` instead, which makes one worksheet\-pinned source per sheet
 .TP
 .B \-\-file <path>
 Replace the source file (local dataset only; cloud file replacement is unsupported)
@@ -6321,7 +6318,7 @@ Postman API key (defaults to the `postman login` session)
 
 Examples:
   postman dataset view create \-d ./users.dataset.yaml \e
-    \-n "Active Users" \-q "SELECT * FROM source_users WHERE active = true"
+    \-n "Active Users" \-q "SELECT * FROM users WHERE active = true"
   postman dataset view create \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \e
     \-n "Active Users" \-q "SELECT * FROM users WHERE active = true"
 
@@ -6389,7 +6386,7 @@ Postman API key (defaults to the `postman login` session)
 
 Examples:
   postman dataset view update "Active Users" \e
-    \-d ./users.dataset.yaml \-q "SELECT * FROM source_users"
+    \-d ./users.dataset.yaml \-q "SELECT * FROM users"
   postman dataset view update "Active Users" \e
     \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT * FROM users"
 

package/package.json

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