postman-cli 1.44.0 → 1.46.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-07-22" "v1.44.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-08-11" "v1.46.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -172,14 +172,14 @@ Define the number of iterations to run
 .B \-d, \-\-iteration\-data <path>
 Specify a data file to use for iterations (either JSON or CSV)
 .TP
-.B \-\-iteration\-data\-dataset <path>
-[BETA] Path to a .dataset.yaml whose view drives the iteration data. Mutually exclusive with \-\-iteration\-data. Requires \-\-iteration\-data\-view.
+.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.
 .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.
 .TP
 .B \-\-dataset <pathOrDir>
-[BETA] Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to scripts as pm.datasets(<id>). When provided, auto\-discovery of .dataset.yaml files from the collection's parent repo is disabled. (default: )
+[BETA] Pass \-\-dataset multiple times to load several .dataset.yaml files (or directories containing them). Each is made available to scripts 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: )
@@ -264,7 +264,7 @@ Exports the cookie jar to a file after completing the run
 Show detailed information of collection run and each request sent
 .TP
 .B \-\-mock <path>
-Start a mock server from manifest (.json) file
+Start a mock server from manifest (.json, .yaml or .yml) file
 .TP
 .B \-\-simulate <path>
 Start mock servers with fault\-injection scenarios from a .sim.yaml file
@@ -491,12 +491,48 @@ Manage workspace resources.
 
 .B Subcommands:
 .TP
+.B workspace list
+List all available Postman Workspaces
+.TP
 .B workspace prepare
 Prepare local collections and environments for push by validating and regenerating IDs if needed.
 .TP
 .B workspace push
 Push local workspace entities (collections, environments, specifications, and more) to Postman workspace.
 
+.SS "workspace list"
+List all available Postman Workspaces
+
+.B Usage:
+[options]
+
+.B Options:
+.TP
+.B \-f, \-\-filter <name>
+Filter workspaces by name.
+.TP
+.B \-t, \-\-type <type>
+Filter workspaces by visibility type: team, public, private, personal.
+.TP
+.B \-\-verbose
+Verbose output
+.TP
+.B \-\-debug
+Debug output
+.TP
+.B \-\-json
+JSON output
+
+.TP Examples:
+
+Examples:
+  postman workspace list
+  postman workspace list \-\-filter "my\-workspace"
+  postman workspace list \-\-type team
+  postman workspace list \-\-type team \-\-filter "project"
+
+
+
 .SS "workspace prepare"
 Prepare local collections and environments for push by validating and regenerating IDs if needed.
 
@@ -560,7 +596,7 @@ Specify an Id to a Postman Globals
 Number of virtual users (default: 20)
 .TP
 .B \-d, \-\-duration <minutes>
-Duration of the performance test in minutes (default: 10)
+Duration of the performance test in minutes (default: 1)
 .TP
 .B \-p, \-\-load\-profile <profile>
 Load profile type: fixed, ramp\-up, spike, peak (default: ramp\-up)
@@ -766,6 +802,15 @@ 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).
+.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: )
+.TP
 .B \-e, \-\-environment <path>
 Specify a path to a Postman Environment file (JSON or YAML)
 .TP
@@ -1219,7 +1264,7 @@ Generate and manage your SDKs directly from the command line.
 Create or update .postman/config.json with an SDK configuration stub.
 .TP
 .B sdk generate
-Generate a new SDK from a Postman collection or specification.
+Generate a new SDK from a Postman collection or specification (OpenAPI or AsyncAPI).
 .TP
 .B sdk track
 Enable change tracking for a generated SDK. Adds file hashes to .manifest.json so that the next `sdk generate` can detect your edits and preserve them via 3\-way merge.
@@ -1248,7 +1293,7 @@ Create or update .postman/config.json with an SDK configuration stub.
 Skip prompts and overwrite existing sdk config
 
 .SS "sdk generate"
-Generate a new SDK from a Postman collection or specification.
+Generate a new SDK from a Postman collection or specification (OpenAPI or AsyncAPI).
 
 .B Usage:
 <idOrPath> [options]
@@ -1308,6 +1353,8 @@ Input:
     \- A file path to a collection (.json) or specification (.json, .yaml, .yml) file
     \- A URL to a publicly accessible collection or specification file
   
+  Supported specification formats: OpenAPI (2.0/3.x) and AsyncAPI (2.x/3.x).
+  
   When using an ID, the SDK generation updates the version in Postman Cloud.
   When using a file path or URL, a one\-off build is created that does not update the Postman Cloud.
   
@@ -1327,6 +1374,9 @@ Examples:
   Generate SDK from OpenAPI specification file (one\-off build):
     postman sdk generate ./openapi.yaml \-l typescript \-o ./my\-sdk
 
+  Generate SDK from AsyncAPI specification file (one\-off build):
+    postman sdk generate ./asyncapi.yaml \-l typescript \-o ./my\-sdk
+
   Generate SDK from publicly accessible URL (one\-off build):
     postman sdk generate https://petstore.swagger.io/v2/swagger.json \-l typescript \-o ./my\-sdk
 
@@ -1605,10 +1655,10 @@ Run and manage local Postman mock servers.
 .B Subcommands:
 .TP
 .B mock run
-Start a local mock server given a manifest file.
+Start a local mock server given a manifest file (JSON or YAML).
 
 .SS "mock run"
-Start a local mock server given a manifest file.
+Start a local mock server given a manifest file (JSON or YAML).
 
 .B Usage:
 <manifestPath>
@@ -1623,6 +1673,7 @@ Path to a globals file (JSON or YAML) for pm.globals
 
 .TP Examples:
 Eg. postman mock run ./postman/mock\-manifest.json
+    postman mock run ./postman/mock\-manifest.yaml
     postman mock run ./manifest.json \-\-environment ./postman/environments/dev.yaml
 
 
@@ -2029,7 +2080,7 @@ Quick start:
   postman search requests "auth"
   postman search requests "auth" \-\-filter "method=POST AND visibility=public" \-\-ownership org \-\-limit 10 \-\-output json
 
-Element types: requests, collections, workspaces, flows, specs, environments, mocks
+Element types: requests, collections, workspaces, flows, specs, environments, mocks, documents
 
 Detailed help is split by element type:
   postman search requests \-\-help      Request filters and examples
@@ -2039,6 +2090,7 @@ Detailed help is split by element type:
   postman search specs \-\-help         API spec filters and examples
   postman search mocks \-\-help         Mock filters and examples
   postman search environments \-\-help  Environment filters and examples
+  postman search documents \-\-help     Document filters and examples
 
 Pagination: \-\-limit accepts up to 25 results. Use \-\-cursor from the previous response to paginate.
 
@@ -2065,6 +2117,9 @@ Search for mocks by name or keyword.
 .TP
 .B search environments
 Search for environments by name or keyword.
+.TP
+.B search documents
+Search for documents by name or keyword.
 
 .SS "search requests"
 Search for requests by name or keyword.
@@ -2437,6 +2492,57 @@ Examples:
   postman search environments \-\-filter "environmentId=env\-abc123"
 
 
+.SS "search documents"
+Search for documents by name or keyword.
+
+.B Usage:
+[options] [query]
+
+.TP Examples:
+
+Use \-\-cursor from the previous response to paginate.
+Ownership:
+  organization, org  Search resources owned by your organization
+  external           Search resources outside your organization
+  all                Search both organization and external resources
+
+Output modes:
+  default            Card list including basic overview and web link per result
+  json               Detailed JSON response with search metadata
+
+Filter syntax:
+  Use = or != for single values: workspaceId=ws\-1
+  Use IN or NIN for comma\-separated values: workspaceId IN ws\-1,ws\-2
+  Combine filters with AND. Operators are case\-insensitive.
+  Quote supported values that contain spaces or commas: <field>="value with spaces"
+
+\-\-filter\-json format:
+  {"$and":[{"workspaceId":{"$eq":"ws\-abc123"}}]}
+  Only a top\-level $and array is supported; $or and nested groups are not supported.
+  Each condition maps one field to one operator object ($eq, $ne, $in, $nin).
+
+Shared filter fields:
+  privateNetwork      $eq, $ne  (true/false)
+  publisherIsVerified $eq, $ne  (true/false)
+  visibility          $eq, $ne  (internal, public, partner)
+  workspaceId         $eq, $ne, $in, $nin
+  createdBy           $eq, $ne, $in, $nin  (user ID)
+  organizationId      $eq, $ne, $in, $nin  (organization ID)
+  teamId              $eq, $ne, $in, $nin  (team ID)
+  isGitConnected      $eq, $ne  (true/false)
+
+Document filter fields:
+  documentId          $eq, $ne, $in, $nin
+
+ID filters such as createdBy, organizationId, teamId, workspaceId, and collectionId expect IDs.
+Use \-\-output json on a broader search result to inspect available IDs.
+
+Examples:
+  postman search documents "onboarding guide"
+  postman search documents "api reference" \-\-filter "workspaceId=ws\-abc123"
+  postman search documents \-\-filter "documentId=doc\-abc123"
+
+
 .SS "webhook"
 Create and manage Postman webhooks.
 
@@ -2718,19 +2824,19 @@ Examples:
 .B Subcommands:
 .TP
 .B dataset list
-[BETA] List dataset YAMLs under the given directory, or print summary for a single YAML file.
+[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
 .TP
 .B dataset get
-[BETA] Print a dataset's metadata and structure summary.
+[BETA] Print a dataset's metadata and structure summary (local YAML path or cloud id).
 .TP
 .B dataset query
-[BETA] Run an ad\-hoc SQL query against a dataset.
+[BETA] Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 .TP
 .B dataset create
-[BETA] Scaffold a new empty .dataset.yaml file at <path>.
+[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
 .TP
 .B dataset delete
-[BETA] Permanently remove a dataset's .dataset.yaml file and its .resources/ directory.
+[BETA] Permanently remove a dataset: a local .dataset.yaml (+ .resources/) or a cloud dataset id.
 .TP
 .B dataset source
 [BETA] Inspect and manage a dataset's datasources.
@@ -2739,13 +2845,19 @@ Examples:
 [BETA] Inspect and manage saved views on a dataset.
 
 .SS "dataset list"
-[BETA] List dataset YAMLs under the given directory, or print summary for a single YAML file.
+[BETA] List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
 
 .B Usage:
-[options] <pathOrDir>
+[options] [pathOrDir]
 
 .B Options:
 .TP
+.B \-w, \-\-workspace <id>
+Postman workspace ID (cloud list)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output as JSON instead of a table
 
@@ -2754,32 +2866,40 @@ Output as JSON instead of a table
 Examples:
   postman dataset list ./postman/datasets
   postman dataset list ./postman/datasets/users/users.dataset.yaml
+  postman dataset list \-w 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 
 
 .SS "dataset get"
-[BETA] Print a dataset's metadata and structure summary.
+[BETA] Print a dataset's metadata and structure summary (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
+.B \-\-no\-populate
+Skip fetching datasources/views for a cloud dataset
+.TP
 .B \-\-json
-Output the full parsed YAML as JSON
+Output the full dataset as JSON
 
 .TP Examples:
 
 Examples:
   postman dataset get ./postman/datasets/users/users.dataset.yaml
+  postman dataset get 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
 .SS "dataset query"
-[BETA] Run an ad\-hoc SQL query against a dataset.
+[BETA] Run an ad\-hoc SQL query against a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
@@ -2789,6 +2909,9 @@ SQL query to execute (e.g. "SELECT * FROM source_users LIMIT 10")
 .B \-p, \-\-param <value...>
 Positional parameter values for $1, $2, ... bindings; repeatable
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output rows as JSON instead of a table
 
@@ -2797,14 +2920,15 @@ Output rows as JSON instead of a table
 Examples:
   postman dataset query ./users.dataset.yaml \-q "SELECT * FROM source_users LIMIT 5"
   postman dataset query ./users.dataset.yaml \-q "SELECT * FROM source_users WHERE id = $1" \-p 42
+  postman dataset query 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT * FROM users LIMIT 5"
 
 
 
 .SS "dataset create"
-[BETA] Scaffold a new empty .dataset.yaml file at <path>.
+[BETA] Scaffold a new .dataset.yaml at <path>, or (no path, with \-w) create a cloud dataset.
 
 .B Usage:
-[options] <path>
+[options] [path]
 
 .B Options:
 .TP
@@ -2814,24 +2938,31 @@ Human\-readable name for the dataset
 .B \-d, \-\-description <desc>
 Optional description
 .TP
-.B \-\-id <uuid>
-Override the generated dataset id (defaults to a random v4 UUID)
+.B \-\-dataset\-id <uuid>
+Override the generated dataset id (local only; defaults to a random v4 UUID)
 .TP
 .B \-\-force
 Overwrite an existing file at <path>
+.TP
+.B \-w, \-\-workspace <id>
+Postman workspace ID (create a cloud dataset)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
   postman dataset create ./postman/datasets/users/users.dataset.yaml \-\-name "Users"
+  postman dataset create \-\-name "Users" \-w 12345678\-90ab\-cdef\-1234\-567890abcdef
 
 
 
 .SS "dataset delete"
-[BETA] Permanently remove a dataset's .dataset.yaml file and its .resources/ directory.
+[BETA] Permanently remove a dataset: a local .dataset.yaml (+ .resources/) or a cloud dataset id.
 
 .B Usage:
-[options] <path>
+[options] <datasetPathOrId>
 
 .B Options:
 .TP
@@ -2839,13 +2970,17 @@ Examples:
 Skip the confirmation prompt
 .TP
 .B \-\-keep\-resources
-Delete only the YAML file; leave the .resources/ directory intact
+Delete only the YAML file; leave the .resources/ directory intact (local only)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
   postman dataset delete ./postman/datasets/users/users.dataset.yaml
   postman dataset delete ./postman/datasets/users/users.dataset.yaml \-\-yes
+  postman dataset delete 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-\-yes
 
 
 
@@ -2858,32 +2993,39 @@ Examples:
 .B Subcommands:
 .TP
 .B dataset source list
-[BETA] List the datasources defined on a dataset.
+[BETA] List the datasources defined on a dataset (local YAML path or cloud id).
 .TP
 .B dataset source add
 [BETA] Add a datasource to a dataset.
 .TP
 .B dataset source remove
-[BETA] Remove a datasource from a dataset.
+[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
 .TP
 .B dataset source update
 [BETA] Update fields on an existing datasource. Only the flags you provide are changed.
 
 .SS "dataset source list"
-[BETA] List the datasources defined on a dataset.
+[BETA] List the datasources defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset whose sources to list — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output sources as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset source list ./postman/datasets/users/users.dataset.yaml
+  postman dataset source list \-d ./postman/datasets/users/users.dataset.yaml
+  postman dataset source list \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
@@ -2891,14 +3033,17 @@ Examples:
 [BETA] Add a datasource to a dataset.
 
 .B Usage:
-[options] <pathOrId>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset to add the source to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 Logical name for the source (becomes the SQL table name)
 .TP
-.B \-\-id <uuid>
+.B \-\-source\-id <uuid>
 Override the generated source id
 .TP
 .B \-\-format <csv|json|mysql|postgres>
@@ -2911,10 +3056,13 @@ Source kind; inferred from \-\-file/\-\-url when omitted
 Path to a local CSV/JSON file (absolute or cwd\-relative)
 .TP
 .B \-\-ref\-only
-Reference the file in place; do NOT copy into data_dir
+Reference the file in place; do NOT copy into data_dir (local dataset)
 .TP
 .B \-\-force
-When copying, overwrite an existing file at the destination
+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.
 .TP
 .B \-\-url <url>
 HTTP(S) URL to a remote CSV/JSON file
@@ -2929,7 +3077,7 @@ DB port
 DB user (warning: stored as plaintext in the YAML).
 .TP
 .B \-\-password <password>
-DB password (warning: stored as plaintext in the YAML).
+DB password. WARNING: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.
 .TP
 .B \-\-database <db>
 DB database name
@@ -2939,18 +3087,30 @@ DB table name (optional)
 .TP
 .B \-\-slug <slug>
 Optional slug for the source
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .SS "dataset source remove"
-[BETA] Remove a datasource from a dataset.
+[BETA] Remove a datasource from a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <sourceNameOrId>
+[options] <sourceNameOrId>
+
+.B Options:
+.TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset source remove ./users.dataset.yaml source_people_1
-  postman dataset source remove ./users.dataset.yaml d3e67bc9\-f9a3\-43b5\-b894\-d00f1791258c
+  postman dataset source remove \-d ./users.dataset.yaml source_people_1
+  postman dataset source remove \-d ./users.dataset.yaml d3e67bc9\-f9a3\-43b5\-b894\-d00f1791258c
+  postman dataset source remove \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de source_people_1
 
 
 
@@ -2958,10 +3118,13 @@ Examples:
 [BETA] Update fields on an existing datasource. Only the flags you provide are changed.
 
 .B Usage:
-[options] <pathOrId> <sourceNameOrId>
+[options] <sourceNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the source belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 Rename the source
 .TP
@@ -2990,7 +3153,7 @@ Update DB port
 Update DB user (warning: stored as plaintext in the YAML).
 .TP
 .B \-\-password <password>
-Update DB password (warning: stored as plaintext in the YAML).
+Update DB password. WARNING: passing it here exposes it in `ps` output and shell history, and it is stored as plaintext in the dataset YAML (local) or sent in the request body (cloud). Prefer a restricted DB user; secure input (prompt / stdin / env) is planned.
 .TP
 .B \-\-database <db>
 Update DB database name
@@ -3000,6 +3163,9 @@ Update DB table name
 .TP
 .B \-\-slug <slug>
 Update slug
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .SS "dataset view"
 [BETA] Inspect and manage saved views on a dataset.
@@ -3010,35 +3176,42 @@ Update slug
 .B Subcommands:
 .TP
 .B dataset view list
-[BETA] List the saved views defined on a dataset.
+[BETA] List the saved views defined on a dataset (local YAML path or cloud id).
 .TP
 .B dataset view run
 [BETA] Execute a saved view against a dataset and print the rows.
 .TP
 .B dataset view create
-[BETA] Add a saved view to a dataset.
+[BETA] Add a saved view to a dataset (local YAML path or cloud id).
 .TP
 .B dataset view delete
-[BETA] Remove a saved view from a dataset.
+[BETA] Remove a saved view from a dataset (local YAML path or cloud id).
 .TP
 .B dataset view update
-[BETA] Update name and/or query on an existing view.
+[BETA] Update name and/or query on an existing view (local YAML path or cloud id).
 
 .SS "dataset view list"
-[BETA] List the saved views defined on a dataset.
+[BETA] List the saved views defined on a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset whose views to list — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output views as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset view list ./postman/datasets/users/users.dataset.yaml
+  postman dataset view list \-d ./postman/datasets/users/users.dataset.yaml
+  postman dataset view list \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
@@ -3046,80 +3219,111 @@ Examples:
 [BETA] Execute a saved view against a dataset and print the rows.
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-p, \-\-param <value...>
 Positional parameter values for $1, $2, ... bindings; repeatable
 .TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
 .B \-\-json
 Output rows as JSON instead of a table
 
 .TP Examples:
 
 Examples:
-  postman dataset view run ./users.dataset.yaml "Active Users"
-  postman dataset view run ./users.dataset.yaml ea748a6a\-ed3c\-496d\-b91e\-6ccc8e4d0e9d
+  postman dataset view run "Active Users" \-d ./users.dataset.yaml
+  postman dataset view run ea748a6a\-ed3c\-496d\-b91e\-6ccc8e4d0e9d \-d ./users.dataset.yaml
+  postman dataset view run "Active Users" \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de
 
 
 
 .SS "dataset view create"
-[BETA] Add a saved view to a dataset.
+[BETA] Add a saved view to a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path>
+[options]
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset to add the view to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 View name
 .TP
 .B \-q, \-\-query <sql>
 SQL query the view executes
 .TP
-.B \-\-id <uuid>
-Override the generated view id
+.B \-\-view\-id <uuid>
+Override the generated view id (local only; cloud assigns its own)
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view create ./users.dataset.yaml \e
+  postman dataset view create \-d ./users.dataset.yaml \e
     \-n "Active Users" \-q "SELECT * FROM source_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"
 
 
 
 .SS "dataset view delete"
-[BETA] Remove a saved view from a dataset.
+[BETA] Remove a saved view from a dataset (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
+
+.B Options:
+.TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view delete ./users.dataset.yaml "Active Users"
+  postman dataset view delete \-d ./users.dataset.yaml "Active Users"
+  postman dataset view delete \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de "Active Users"
 
 
 
 .SS "dataset view update"
-[BETA] Update name and/or query on an existing view.
+[BETA] Update name and/or query on an existing view (local YAML path or cloud id).
 
 .B Usage:
-[options] <path> <viewNameOrId>
+[options] <viewNameOrId>
 
 .B Options:
 .TP
+.B \-d, \-\-dataset <datasetPathOrId>
+Dataset the view belongs to — a local .dataset.yaml path or a cloud dataset id
+.TP
 .B \-n, \-\-name <name>
 New view name
 .TP
 .B \-q, \-\-query <sql>
 New SQL query
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
 
 .TP Examples:
 
 Examples:
-  postman dataset view update ./users.dataset.yaml "Active Users" \-q "SELECT ..."
+  postman dataset view update "Active Users" \-d ./users.dataset.yaml \-q "SELECT ..."
+  postman dataset view update "Active Users" \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-q "SELECT ..."
 
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.44.0",
+  "version": "1.46.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.44.0",
-    "@postman/pm-bin-macos-x64": "1.44.0",
-    "@postman/pm-bin-linux-x64": "1.44.0",
-    "@postman/pm-bin-linux-arm64": "1.44.0",
-    "@postman/pm-bin-windows-x64": "1.44.0"
+    "@postman/pm-bin-macos-arm64": "1.46.0",
+    "@postman/pm-bin-macos-x64": "1.46.0",
+    "@postman/pm-bin-linux-x64": "1.46.0",
+    "@postman/pm-bin-linux-arm64": "1.46.0",
+    "@postman/pm-bin-windows-x64": "1.46.0"
   }
 }