postman-cli 1.66.0 → 1.68.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-10-01" "v1.68.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
@@ -305,6 +305,9 @@ Add, update, or remove requests in a local v3 collection.
 .B collection folder
 Add, update, or remove folders in a local v3 collection.
 .TP
+.B collection import
+Import a cURL or HAR source into a v3 collection (local, or cloud with \-\-workspace).
+.TP
 .B collection list
 List collections: your local project's collections by default, or a Postman cloud workspace's collections with \-\-workspace.
 .TP
@@ -371,53 +374,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 +578,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 +618,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>
@@ -770,6 +790,50 @@ Examples:
 
 
 
+.SS "collection import"
+Import a cURL or HAR source into a v3 collection (local, or cloud with \-\-workspace).
+
+.B Usage:
+[options] <src>
+
+.B Options:
+.TP
+.B \-\-type <format>
+Source format: curl or har. Auto\-detected from the extension/content when omitted.
+.TP
+.B \-\-name <name>
+Collection display name. Defaults to a per\-format fallback.
+.TP
+.B \-o, \-\-output <dir>
+Output directory for the local collection (default: postman/collections/<name>).
+.TP
+.B \-w, \-\-workspace <id>
+Create the collection in a Postman cloud workspace by id (cloud mode).
+.TP
+.B \-\-force
+Overwrite an existing local target directory.
+.TP
+.B \-\-timeout <ms>
+Max time for a cloud import, in milliseconds (default 120000).
+.TP
+.B \-\-verbose
+Verbose output (cloud import diagnostics).
+.TP
+.B \-\-json
+JSON output.
+
+.TP Examples:
+
+<src> is a file path, `\-` for stdin, or an inline cURL command.
+
+Examples:
+  postman collection import ./login.curl
+  postman collection import ./session.har \-\-name "Recorded session"
+  pbpaste | postman collection import \- \-\-type curl \-\-name Users
+  postman collection import ./session.har \-\-name Session \-\-workspace <workspaceId>
+
+
+
 .SS "collection list"
 List collections: your local project's collections by default, or a Postman cloud workspace's collections with \-\-workspace.
 
@@ -821,7 +885,7 @@ Specify an Id or path to a file containing Postman Globals
 Specify the reporters to use for the run: cli,json,junit,html. For multiple reporters, provide their names as a comma\-separated list (E.g., \-r cli,json) (default: cli)
 .TP
 .B    \-\-output <folder>
-Write a YAML\-based run report to the given folder. Creates a paired `<prefix>.collection\-run\-summary.yaml` (refreshed during the run) and streaming `<prefix>.collection\-run\-executions.yaml`, where prefix defaults to `<collection\-slug>\-<timestamp>`. Gotcha: \-\-output streams run data to file and cannot be combined with the built\-in reporters (\-r/\-\-reporter\-*); doing so exits with an error. This keeps large runs from buffering an entire report in memory.
+Write a YAML\-based run report to the given folder. Creates a paired `<prefix>.collection\-run\-summary.yaml` (refreshed during the run) and streaming `<prefix>.collection\-run\-executions.yaml`, where prefix defaults to `<collection\-slug>\-<timestamp>`. Gotcha: \-\-output streams run data to file, which keeps large runs from buffering an entire report in memory.
 .TP
 .B    \-\-reporter\-[reporter]\-export <path>
 [Optional] Specify a path to save the report. By default, reports are saved to the /postman\-cli\-reports directory in your current working directory. If the directory doesn't exist, it will be created automatically. If the specified path is an existing directory, the report file will be saved within it. Supported reporters: json, junit and html.
@@ -854,13 +918,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 +1488,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 +1534,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.
 
@@ -1796,7 +1828,7 @@ Invoke a monitor run and display results.
 Create a collection\-based monitor.
 .TP
 .B monitor update
-Update a monitor's schedule, runner, notifications or run options.
+Update a monitor's schedule, runner, notifications, request selection or run options.
 .TP
 .B monitor delete
 Permanently delete a monitor. Prompts for confirmation unless \-\-yes is passed.
@@ -1874,6 +1906,9 @@ Time zone for \-\-schedule, for example America/New_York (defaults to the host m
 .B \-\-runner <value>
 A Postman region name (see `postman runner regions`) or the id of a self\-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable) (default: )
 .TP
+.B \-i, \-\-item <id>
+Id of a request or folder in the collection to run, in the order given (repeatable; ids only, not names or paths; defaults to every request; list ids with `postman collection get <collection\-id> \-\-json`) (default: )
+.TP
 .B \-\-notify\-email <email>
 Email to notify on a run failure or error (repeatable) (default: )
 .TP
@@ -1928,12 +1963,13 @@ Examples:
   postman monitor create \-\-collection 12345678\-90ab\-cdef\-1234\-567890abcdef
   postman monitor create \-\-collection <id> \-\-schedule "0 9 * * MON" \-\-timezone America/New_York
   postman monitor create \-\-collection <id> \-\-runner us\-east \-\-runner <self\-hosted\-runner\-id>
+  postman monitor create \-\-collection <id> \-\-item <request\-id> \-\-item <folder\-id>
   postman monitor create \-\-collection <id> \-\-workspace 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 
 
 .SS "monitor update"
-Update a monitor's schedule, runner, notifications or run options.
+Update a monitor's schedule, runner, notifications, request selection or run options.
 
 .B Usage:
 [options] <monitorId>
@@ -1952,6 +1988,12 @@ Time zone for \-\-schedule, for example America/New_York (defaults to the host m
 .B \-\-runner <value>
 A Postman region name (see `postman runner regions`) or the id of a self\-hosted runner created in Postman (list existing ones with `postman runner list`) to run from (repeatable; replaces the current set) (default: )
 .TP
+.B \-i, \-\-item <id>
+Id of a request or folder in the collection to run, in the order given (repeatable; ids only, not names or paths; replaces the saved selection; list ids with `postman collection get <collection\-id> \-\-json`) (default: )
+.TP
+.B \-\-clear\-items
+Remove the saved selection so the monitor runs every request in its collection
+.TP
 .B \-\-notify\-email <email>
 Email to notify on a run failure or error (repeatable; replaces the current list) (default: )
 .TP
@@ -2013,6 +2055,8 @@ Examples:
   postman monitor update <id> \-\-notify\-email a@example.com \-\-notify\-email b@example.com
   postman monitor update <id> \-\-clear\-notifications
   postman monitor update <id> \-\-runner us\-east \-\-runner <self\-hosted\-runner\-id>
+  postman monitor update <id> \-\-item <request\-id> \-\-item <folder\-id>
+  postman monitor update <id> \-\-clear\-items
   postman monitor update <id> \-\-environment 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 This command cannot change a monitor's linked collection \-\- that is fixed when the monitor is created, so run a different collection by creating a new monitor. It does not pause or resume a monitor either; use `monitor pause`/`monitor resume` for that.
@@ -2332,6 +2376,9 @@ Filter workspaces by name.
 .B \-t, \-\-type <type>
 Filter workspaces by visibility type: team, public, private, personal.
 .TP
+.B \-\-cursor <cursor>
+Fetch the page of workspaces that follows this cursor.
+.TP
 .B \-\-verbose
 Verbose output
 .TP
@@ -2348,6 +2395,7 @@ Examples:
   postman workspace list \-\-filter "my\-workspace"
   postman workspace list \-\-type team
   postman workspace list \-\-type team \-\-filter "project"
+  postman workspace list \-\-cursor "<cursor>"
 
 
 
@@ -2361,6 +2409,9 @@ Prepare local collections and environments for push by validating and regenerati
 .TP
 .B \-\-verbose
 Show detailed logging
+.TP
+.B \-\-json
+Print the outcome as machine\-readable JSON.
 
 .SS "workspace push"
 Push local workspace entities (collections, environments, specifications, mocks and more) to Postman workspace.
@@ -2379,6 +2430,9 @@ Skip all confirmation prompts
 .B \-\-push\-strategy <strategy>
 Push strategy. "force\-sync": mirror the whole workspace — also DELETE cloud entities that have no local counterpart (destructive). Defaults to "default" (create/update only).
 .TP
+.B \-\-json
+Print the outcome as machine\-readable JSON. Implies non\-interactive: use \-\-yes to actually push.
+.TP
 .B \-\-verbose
 Show detailed logging
 .TP
@@ -2470,6 +2524,9 @@ Create the workspace without binding it to the repository
 .TP
 .B \-\-force
 Create even when a workspace is already recorded for this repo
+.TP
+.B \-\-json
+Print the created workspace as machine\-readable JSON.
 
 .TP Examples:
 
@@ -2531,6 +2588,9 @@ Skip all confirmation prompts
 .B \-\-source\-workspace <workspaceId>
 Pull from a different source workspace.
 .TP
+.B \-\-json
+Print the outcome as machine\-readable JSON. Implies non\-interactive: use \-\-yes to actually pull.
+.TP
 .B \-\-verbose
 Show detailed logging
 
@@ -2557,6 +2617,9 @@ Connect a Postman workspace to a local git repository.
 .TP
 .B \-\-verbose
 Show detailed logging
+.TP
+.B \-\-json
+Print the outcome as machine\-readable JSON.
 
 .TP Examples:
 
@@ -2583,6 +2646,9 @@ Skip all confirmation prompts
 .TP
 .B \-\-verbose
 Show detailed logging
+.TP
+.B \-\-json
+Print the outcome as machine\-readable JSON. Requires \-\-yes to actually disconnect.
 
 .TP Examples:
 
@@ -3228,6 +3294,30 @@ Preserves the original HTTP method when following redirects. By default, redirec
 .B \-\-redirects\-remove\-referrer
 Removes the Referer header when following redirects. By default, Referer header is sent with redirects.
 .TP
+.B \-k, \-\-insecure
+Disable SSL certificate verification.
+.TP
+.B \-\-ssl\-client\-cert\-list <path>
+Specify the path to client certificate configurations (JSON).
+.TP
+.B \-\-ssl\-client\-cert <path>
+Specify the path to a client certificate (PEM).
+.TP
+.B \-\-ssl\-client\-key <path>
+Specify the path to a client certificate private key.
+.TP
+.B \-\-ssl\-client\-passphrase <passphrase>
+Specify the client certificate passphrase (for protected key).
+.TP
+.B \-\-ssl\-extra\-ca\-certs <path>
+Specify additional trusted CA certificates (PEM).
+.TP
+.B \-\-cookie\-jar <path>
+Specify the path to a custom cookie jar (serialized tough\-cookie JSON).
+.TP
+.B \-\-export\-cookie\-jar <path>
+Export the cookie jar to a file after completing the request.
+.TP
 .B \-\-retry <n>
 Number of retry attempts for failed requests (4xx, 5xx, network errors). Useful for flaky endpoints or rate\-limited APIs. (default: 0)
 .TP
@@ -3975,6 +4065,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 +4078,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 +5725,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 +5745,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 +5877,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 +5898,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 +6054,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 +6067,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 +6117,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 +6423,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 +6491,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.68.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.68.0",
+    "@postman/pm-bin-macos-x64": "1.68.0",
+    "@postman/pm-bin-linux-x64": "1.68.0",
+    "@postman/pm-bin-linux-arm64": "1.68.0",
+    "@postman/pm-bin-windows-x64": "1.68.0"
   }
 }