postman-cli 1.59.0 → 1.60.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-09-18" "v1.59.0" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-09-21" "v1.60.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -8,6 +8,13 @@ postman \- Command\-line companion utility for Postman
 The Postman CLI is a command\-line companion utility that brings the power of Postman platform directly to your terminal. It enables you to run collections, lint APIs, manage monitors, and integrate API testing into CI/CD pipelines.
 .br
 Note: All commands support the --help option for more information..
+.SH CLAUDE CODE PLUGIN
+Claude Code users and agents can use the Postman Plugin for Claude Code for full API lifecycle management including documentation, collections, workspaces, environments, mocks, monitors right from your repository.
+.br
+Install it with: claude plugin install postman@claude\-plugins\-official
+.br
+Then start Claude Code and run: /postman:setup
+.br
 .SH OPTIONS
 .TP
 .B \-v, \-\-version
@@ -48,14 +55,8 @@ Sign up to keep the work you created as a guest (claims your guest workspace). W
 
 .B Options:
 .TP
-.B \-\-browser
-Always open the sign\-up URL in a browser here, rather than printing it.
-.TP
-.B \-\-wait
-Wait for the sign\-up to complete even if no local browser is detected.
-.TP
-.B \-\-no\-wait
-Print the sign\-up URL and exit without waiting. Leaves this CLI a guest.
+.B \-\-guest
+Start working as an anonymous guest instead of signing up — no account or browser needed, so it works anywhere. Your work is saved to a temporary workspace you can keep later by running `postman signup`.
 .TP
 .B \-\-json
 Print the sign\-up details as machine\-readable JSON.
@@ -150,6 +151,11 @@ Update Postman CLI using the original installation method.
 .B Usage:
 [options]
 
+.B Options:
+.TP
+.B \-\-check
+Check whether a Postman CLI update is available.
+
 .SS "skills"
 Check and update the agent skills in this repository.
 
@@ -914,7 +920,7 @@ Eg. postman api publish <apiId> \-\-name v1\e
 
 
 .SS "runner"
-Where your monitors execute: run and inspect your own self\-hosted runners, and list the Postman\-operated regions available to your team
+Where your monitors execute: run and inspect your own self\-hosted runners, and list the Postman\-operated regions available to your team.
 
 .B Usage:
 [options] [command]
@@ -922,16 +928,16 @@ Where your monitors execute: run and inspect your own self\-hosted runners, and
 .B Subcommands:
 .TP
 .B runner start
-Start a runner
+Start a self\-hosted runner in your own network.
 .TP
 .B runner list
-List the team's registered self\-hosted runners
+List the team's registered self\-hosted runners.
 .TP
 .B runner regions
-List the region and private\-runner values valid for monitor create/update \-\-runner, including a static IP where configured
+List the region and private\-runner values valid for monitor create/update \-\-runner, with the static IP Postman runs each one from, where your team has access to it.
 
 .SS "runner start"
-Start a runner
+Start a self\-hosted runner in your own network.
 
 .B Usage:
 [options]
@@ -945,10 +951,10 @@ The ID of the runner to execute
 The secret key for the runner
 .TP
 .B \-\-region <region>
-Specify the region for the runner. Use "eu" for EU region.
+Region this runner reports to \-\- use "eu" for the EU region
 .TP
 .B \-\-proxy <url>
-External proxy URL (e.g., http://proxy.com or http://proxy.com:8080)
+External proxy URL, for example http://proxy.com or http://proxy.com:8080
 .TP
 .B \-\-egress\-proxy
 Enable built\-in egress proxy
@@ -959,6 +965,9 @@ Custom egress proxy authorization service base URL
 .B \-\-ssl\-extra\-ca\-certs <path>
 Additional trusted CA certificates (PEM file, can contain multiple certs)
 .TP
+.B \-\-dataset\-jdbc\-driver\-dir <path>
+Folder on this machine holding the JDBC driver .jar files you put there. Required to run a dataset that uses a JDBC source. Drivers are loaded only from this folder and matched by file name; driver paths saved in the dataset are ignored
+.TP
 .B \-\-metrics
 Enable the metrics server for health checks
 .TP
@@ -966,13 +975,13 @@ Enable the metrics server for health checks
 Port for the metrics server (default: 9090)
 .TP
 .B \-\-report\-events
-Accepted for compatibility; analytics are sent by default
+Accepted for compatibility; run events are reported by default
 .TP
 .B \-\-no\-report\-events
-Do not send analytics to Postman
+Do not report run events to Postman
 
 .SS "runner list"
-List the team's registered self\-hosted runners
+List the team's registered self\-hosted runners.
 
 .B Usage:
 [options]
@@ -989,7 +998,7 @@ Filter to runners in this workspace
 Output the runner list as JSON instead of a table
 
 .SS "runner regions"
-List the region and private\-runner values valid for monitor create/update \-\-runner, including a static IP where configured
+List the region and private\-runner values valid for monitor create/update \-\-runner, with the static IP Postman runs each one from, where your team has access to it.
 
 .B Usage:
 [options]
@@ -1349,7 +1358,7 @@ Invoke a monitor run and display results.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
 .TP
 .B \-x, \-\-suppress\-exit\-code
 Specify whether or not to override the default exit code for the current run
@@ -1377,7 +1386,7 @@ Collection to monitor \-\- accepts the id shown in the Postman app, prefixed or
 .B \-\-name <name>
 Monitor name (defaults to the linked collection's own name)
 .TP
-.B \-\-environment <id>
+.B \-e, \-\-environment <id>
 Environment to run the monitored collection with
 .TP
 .B \-w, \-\-workspace <id>
@@ -1387,7 +1396,7 @@ Workspace to create the monitor in (defaults to the workspace named in the local
 Cron expression for the monitor's schedule
 .TP
 .B \-\-timezone <tz>
-Time zone for \-\-schedule, e.g. America/New_York (defaults to the host machine's own zone)
+Time zone for \-\-schedule, for example America/New_York (defaults to the host machine's own zone)
 .TP
 .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: )
@@ -1396,10 +1405,10 @@ A Postman region name (see `postman runner regions`) or the id of a self\-hosted
 Email to notify on a run failure or error (repeatable) (default: )
 .TP
 .B \-\-notification\-limit <n>
-Cap consecutive notifications before they are muted (service range: 1\-99)
+Consecutive failure notifications to send before muting them
 .TP
 .B \-\-retry <n>
-Retries on a failed run (service caps this at 2)
+Times to retry a failed run
 .TP
 .B \-\-timeout <ms>
 Request timeout in milliseconds
@@ -1429,7 +1438,7 @@ Dataset view to iterate (used together with \-\-dataset\-id)
 Number of iterations to run
 .TP
 .B \-\-iteration\-strategy <strategy>
-How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires \-\-iteration\-count, \-\-dataset\-id and \-\-dataset\-view\-id)
+How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires \-\-iteration\-count, \-\-dataset\-id and \-\-dataset\-view\-id)
 .TP
 .B \-\-no\-run\-now
 Do not trigger an immediate run after creating the monitor
@@ -1465,7 +1474,7 @@ New monitor name
 New cron expression for the monitor's schedule
 .TP
 .B \-\-timezone <tz>
-Time zone for \-\-schedule, e.g. America/New_York (defaults to the host machine's own zone)
+Time zone for \-\-schedule, for example America/New_York (defaults to the host machine's own zone)
 .TP
 .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: )
@@ -1476,11 +1485,17 @@ Email to notify on a run failure or error (repeatable; replaces the current list
 .B \-\-clear\-notifications
 Remove every notification recipient
 .TP
+.B \-e, \-\-environment <id>
+Environment to run the monitored collection with (replaces the current one)
+.TP
+.B \-\-clear\-environment
+Run the monitored collection with no environment
+.TP
 .B \-\-notification\-limit <n>
-Cap consecutive notifications before they are muted (service range: 1\-99)
+Consecutive failure notifications to send before muting them
 .TP
 .B \-\-retry <n>
-Retries on a failed run (service caps this at 2)
+Times to retry a failed run
 .TP
 .B \-\-timeout <ms>
 Request timeout in milliseconds
@@ -1510,7 +1525,7 @@ Dataset view to iterate (used together with \-\-dataset\-id)
 Number of iterations to run
 .TP
 .B \-\-iteration\-strategy <strategy>
-How iteration data is consumed, e.g. round_robin, repeat_last, stop_at_end (requires \-\-iteration\-count, \-\-dataset\-id and \-\-dataset\-view\-id)
+How iteration data is consumed, for example round_robin, repeat_last or stop_at_end (requires \-\-iteration\-count, \-\-dataset\-id and \-\-dataset\-view\-id)
 .TP
 .B \-\-api\-key <key>
 Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
@@ -1525,8 +1540,9 @@ 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> \-\-environment 12345678\-90ab\-cdef\-1234\-567890abcdef
 
-This command cannot change a monitor's linked collection or environment \-\- delete and recreate the monitor instead \-\- and does not pause or resume it; use `monitor pause`/`monitor resume` for that.
+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.
 
 
 .SS "monitor delete"
@@ -1578,13 +1594,13 @@ List a monitor's recent jobs.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
 .TP
 .B \-\-result <value>
-Filter by outcome, e.g. success, failure, error, abort (server\-validated, not a fixed list)
+Filter by outcome, for example success, failure, error or abort
 .TP
 .B \-\-trigger <value>
-Filter by trigger, e.g. api, schedule, webhook, postman\-cli (server\-validated, not a fixed list)
+Filter by trigger, for example api, schedule, webhook or postman\-cli
 .TP
 .B \-\-since <dateTime>
 Only jobs that finished at or after this ISO 8601 date\-time
@@ -1607,7 +1623,7 @@ Report one job's terminal state and its per\-region run outcomes.
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1632,10 +1648,10 @@ Report which test assertions ran during one attempt of a run, which failed, and
 .B Options:
 .TP
 .B \-\-api\-key <key>
-Postman API key (defaults to the `postman login` session)
+Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
 .TP
 .B \-\-attempt <n>
-Which attempt of the run to show, counting from 0 (default: the latest)
+Which attempt of the run to show, where 0 is the first (default: the most recent)
 .TP
 .B \-\-failed\-only
 Show only failed assertions
@@ -1660,11 +1676,11 @@ Filter to monitors in this workspace
 .B \-c, \-\-collection <id>
 Filter to monitors on this collection
 .TP
-.B \-\-environment <id>
+.B \-e, \-\-environment <id>
 Filter to monitors on this environment
 .TP
 .B \-\-runner <id>
-Filter to a Self\-Hosted Runner ID (not a Postman Region). Cannot be combined with \-\-workspace, \-\-collection, \-\-environment, \-\-owner, \-\-team or \-\-active.
+Filter to a self\-hosted runner id, not a Postman region. Cannot be combined with \-\-workspace, \-\-collection, \-\-environment, \-\-owner, \-\-team or \-\-active
 .TP
 .B \-\-owner <id>
 Filter to monitors created by this user id (shown in the Owner column)
@@ -1676,16 +1692,13 @@ Filter to monitors owned by your own team
 Filter by active state
 .TP
 .B \-\-limit <n>
-Max monitors to return. The service caps page size and rejects a value above it with its own error.
-.TP
-.B \-\-offset <n>
-Not supported: the service accepts this parameter and silently ignores it. Refused locally. Use \-\-cursor instead.
+Maximum number of monitors to return (Postman caps the page size and rejects a larger value)
 .TP
 .B \-\-cursor <token>
-Pagination cursor from a previous page's response.
+Pagination cursor from a previous page's response
 .TP
 .B \-\-columns <names>
-Comma\-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available: State, Notifications, Environment, Runners.
+Comma\-separated columns to show. Defaults to Name, Status, ID, Schedule, Owner, Collection. Also available: State, Notifications, Environment, Runners
 .TP
 .B \-\-no\-headers
 Omit the header row
@@ -1741,16 +1754,16 @@ Show per\-request latency and outcome history for a monitor.
 Postman API key (defaults to POSTMAN_API_KEY, then the `postman login` session)
 .TP
 .B \-\-since <dateTime>
-Only executions at or after this ISO 8601 date\-time. Defaults to 7 days ago.
+Only executions at or after this ISO 8601 date\-time (defaults to 7 days ago)
 .TP
 .B \-\-until <dateTime>
-Only executions at or before this ISO 8601 date\-time. Defaults to now.
+Only executions at or before this ISO 8601 date\-time (defaults to now)
 .TP
 .B \-f, \-\-filter <text>
 Show only requests whose name contains this text (case\-insensitive)
 .TP
 .B \-\-limit <n>
-Cap the number of rows shown: executions (newest first) under \-\-json, or table rows (worst\-behaving request first) otherwise. Not honoured by the service \-\- there is no server\-side pagination on this route.
+Maximum number of rows to show: executions, newest first, under \-\-json, or requests, worst\-behaving first, in the table. Applied to the results after they are fetched, so it does not make the command faster
 .TP
 .B \-\-json
 Output as JSON instead of a table
@@ -1811,6 +1824,9 @@ Push local workspace entities (collections, environments, specifications, mocks
 .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 get
+Read a workspace's metadata, and optionally the ids of what it holds.
+.TP
 .B workspace create
 Create a Postman workspace and bind it to this git repository.
 .TP
@@ -1916,6 +1932,34 @@ The workspace ID to use for fetching governance rulesets. Defaults to the id in
 .B \-\-fix
 Apply safe autofixes to repairable workspace lint issues.
 
+.SS "workspace get"
+Read a workspace's metadata, and optionally the ids of what it holds.
+
+.B Usage:
+[options] [id]
+
+.B Options:
+.TP
+.B \-\-elements
+Also report the resources the workspace holds.
+.TP
+.B \-\-json
+Print the workspace as machine\-readable JSON.
+.TP
+.B \-\-timeout <ms>
+Milliseconds to wait for the API (default 30000).
+
+.TP Examples:
+
+Examples:
+  postman workspace get 00a50319\-1262\-49d2\-83e5\-551e3c5dba00
+  postman workspace get <id> \-\-elements
+  postman workspace get <id> \-\-json
+
+Exit codes: 0 ok, 1 not found or API failure, 2 bad usage, 3 auth.
+
+
+
 .SS "workspace create"
 Create a Postman workspace and bind it to this git repository.
 
@@ -2057,7 +2101,7 @@ Manage performance tests on your collections.
 .B performance run
 Run a performance test on a collection
 .TP
-.B performance runs
+.B performance list
 List past performance runs for a collection, newest first.
 
 .SS "performance run"
@@ -2126,7 +2170,7 @@ Examples:
   postman performance run 123456\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-runner postman\-cloud\-static\-ip
 
 
-.SS "performance runs"
+.SS "performance list"
 List past performance runs for a collection, newest first.
 
 .B Usage:
@@ -2149,9 +2193,9 @@ Milliseconds to wait for the service before failing (default: 30000)
 .TP Examples:
 
 Examples:
-  postman performance runs \-\-collection\-id 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab
-  postman performance runs \-c 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-json
-  postman performance runs \-c 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-cursor eyJpZCI6...
+  postman performance list \-\-collection\-id 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab
+  postman performance list \-c 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-json
+  postman performance list \-c 1402295\-45159473\-1e45\-1f34\-5678\-1234567890ab \-\-cursor eyJpZCI6...
 
 The newest 25 runs are returned. A `\-` in Duration means the run has not finished yet.
 A page shorter than 25 does not mean the end of the list: use the printed \-\-cursor
@@ -4856,6 +4900,9 @@ Inspect and manage a dataset's datasources.
 .TP
 .B dataset view
 Inspect and manage saved views on a dataset.
+.TP
+.B dataset jdbc
+Inspect JDBC drivers before attaching one to a dataset.
 
 .SS "dataset list"
 List local dataset YAMLs under a path, or (no path) a workspace's cloud datasets.
@@ -5028,6 +5075,9 @@ Remove a datasource from a dataset (local YAML path or cloud id).
 .TP
 .B dataset source update
 Update fields on an existing datasource. Only the flags you provide are changed.
+.TP
+.B dataset source test
+Open and close a real connection using a source's stored configuration.
 
 .SS "dataset source list"
 List the datasources defined on a dataset (local YAML path or cloud id).
@@ -5074,8 +5124,8 @@ Override the generated source id (local dataset only)
 .B \-\-format <csv|json|mysql|postgres|sqlserver>
 Use this format instead of extension/type inference; file contents are not sniffed
 .TP
-.B \-\-type <local|mysql|postgresql|sqlserver>
-Source kind; local is inferred when \-\-file is provided
+.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)
@@ -5089,6 +5139,45 @@ When copying, overwrite an existing file at the destination (local dataset)
 .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 \-\-driver\-jar <path...>
+JDBC driver JAR(s). Repeatable, or pass several after one flag
+.TP
+.B \-\-driver\-class <fqcn>
+Driver class. Auto\-resolved when the JAR contains exactly one
+.TP
+.B \-\-driver\-name <label>
+Label for this driver type (defaults to the JAR filename)
+.TP
+.B \-\-url\-template <template>
+JDBC URL with {{placeholders}}, e.g. jdbc:postgresql://{{host}}:{{port}}/{{database}}
+.TP
+.B \-\-var <name=value...>
+Value for a {{placeholder}}. Repeatable. Use vault:<vaultId>/<secretId> for a secret. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
+.TP
+.B \-\-prop <name=value...>
+Driver connection property. Repeatable. Same vault: syntax as \-\-var
+.TP
+.B \-\-vars\-file <path>
+JSON object of \-\-var values; "\-" reads stdin. Supports {"$vaultId":..,"$secretId":..} objects, and keeps secrets out of argv entirely
+.TP
+.B \-\-from\-source <name>
+Reuse another source's driver JAR, class and URL template
+.TP
+.B \-\-java\-path <path>
+Java runtime to use. Machine\-local only \- never written to the dataset. Also read from POSTMAN_JDBC_JAVA_PATH
+.TP
+.B \-\-no\-test
+Skip the pre\-write connection test. Note that resolving the driver class still starts a JVM — on a machine with no Java, pass \-\-driver\-class (or \-\-from\-source) too
+.TP
+.B \-\-ssh\-target\-host\-variable <name>
+Template variable holding the tunnelled host (inferred when omitted)
+.TP
+.B \-\-ssh\-target\-port\-variable <name>
+Template variable holding the tunnelled port (inferred when omitted)
+.TP
+.B \-\-json
+Emit the result as JSON instead of prose
+.TP
 .B \-\-host <host>
 DB host (mysql/postgresql/sqlserver)
 .TP
@@ -5096,10 +5185,10 @@ DB host (mysql/postgresql/sqlserver)
 DB port (defaults to 1433 for sqlserver)
 .TP
 .B \-\-user <user>
-DB user (warning: stored as plaintext in the YAML).
+DB user. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
 .TP
 .B \-\-password <password>
-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.
+DB password. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
 .TP
 .B \-\-database <db>
 DB database name
@@ -5166,6 +5255,60 @@ Format selection:
 Execution:
   \-\-upload runs file\-backed queries in the cloud service. Without \-\-upload, the local engine reads the file.
 
+JDBC:
+  Start with `postman dataset jdbc inspect <jar>`. Its output maps onto these
+  flags directly: suggestedUrlTemplate \-> \-\-url\-template, templateVariables \->
+  \-\-var, connectionProperties \-> \-\-prop, driverClass \-> \-\-driver\-class.
+
+  postman dataset jdbc inspect ./drivers/postgresql\-42.7.4.jar
+  postman dataset source add \-d ./orders.dataset.yaml \-n orders \-\-type jdbc \e
+    \-\-driver\-jar ./drivers/postgresql\-42.7.4.jar \e
+    \-\-url\-template 'jdbc:postgresql://{{host}}:{{port}}/{{database}}' \e
+    \-\-var host=db.internal \-\-var port=5432 \-\-var database=shop \e
+    \-\-var user=vault:acme/pg\-user \-\-var password=vault:acme/pg\-pass
+
+  Reuse that driver for a second source, no rediscovery needed:
+  postman dataset source add \-d ./orders.dataset.yaml \-n refunds \-\-type jdbc \e
+    \-\-from\-source orders \-\-var host=db.internal \-\-var port=5432 \-\-var database=refunds
+
+Secrets:
+  \-\-var <k>=vault:<vaultId>/<secretId>   reference a Shared Vault secret (preferred)
+  \-\-var <k>=<literal>                    plaintext: visible in `ps` output and shell
+                                         history, and stored in clear text in the
+                                         dataset YAML. Warned about at run time.
+  A secret written directly into \-\-url\-template is rejected: a literal has no
+  {{name}} to route through \-\-var, so it can never be a Vault reference and
+  nothing masks it. Use a placeholder plus \-\-var instead.
+  \-\-vars\-file <path|\->                   JSON object; "\-" reads stdin, keeping
+                                         secrets out of argv entirely. Accepts
+                                         {"$vaultId":..,"$secretId":..} values.
+  Local Vault secrets are not supported by Postman CLI; use a Shared Vault.
+
+Connection test:
+  Runs before the source is written, so a source that cannot connect is never
+  persisted. Needs a local JRE and a loadable driver. Pass \-\-no\-test to skip it.
+  \-\-no\-test alone still needs Java to resolve the driver class; on a machine with
+  no Java at all, add \-\-driver\-class or \-\-from\-source so nothing has to load it.
+
+JSON output (\-\-json):
+  Success: {"ok":true,"source":{"id","name","target","format","driver",
+            "urlTemplate","connectionTest"},"warnings":[...]}
+  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,
+  DRIVER_CLASS_AMBIGUOUS (with candidates[]), URL_TEMPLATE_INVALID,
+  CONFIG_VALUE_MISSING (with missing[]), URL_TEMPLATE_LITERAL_SECRET,
+  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
+  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
+  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.
+
 
 
 .SS "dataset source remove"
@@ -5217,6 +5360,42 @@ With \-\-file, reference in place instead of copying (local dataset only)
 .B \-\-force
 With \-\-file, overwrite the copied destination (local dataset only)
 .TP
+.B \-\-driver\-jar <path...>
+Replace the JDBC driver JAR(s)
+.TP
+.B \-\-driver\-class <fqcn>
+Replace the JDBC driver class
+.TP
+.B \-\-driver\-name <label>
+Rename the JDBC driver type label
+.TP
+.B \-\-url\-template <template>
+Replace the JDBC URL template
+.TP
+.B \-\-var <name=value...>
+Set a JDBC template variable. Merges onto the existing values. Use vault:<vaultId>/<secretId> for a secret. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
+.TP
+.B \-\-prop <name=value...>
+Set a JDBC connection property. Merges, same vault: syntax
+.TP
+.B \-\-unset\-var <name...>
+Remove a JDBC template variable. Merging alone can never remove a key
+.TP
+.B \-\-unset\-prop <name...>
+Remove a JDBC connection property
+.TP
+.B \-\-vars\-file <path>
+JSON object of \-\-var values; "\-" reads stdin
+.TP
+.B \-\-ssh\-target\-host\-variable <name>
+Template variable holding the tunnelled host (JDBC)
+.TP
+.B \-\-ssh\-target\-port\-variable <name>
+Template variable holding the tunnelled port (JDBC)
+.TP
+.B \-\-java\-path <path>
+Java runtime for JDBC operations. Machine\-local only
+.TP
 .B \-\-host <host>
 Update DB host (mysql/postgresql/sqlserver)
 .TP
@@ -5224,10 +5403,10 @@ Update DB host (mysql/postgresql/sqlserver)
 Update DB port
 .TP
 .B \-\-user <user>
-Update DB user (warning: stored as plaintext in the YAML).
+Update DB user. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
 .TP
 .B \-\-password <password>
-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.
+Update DB password. WARNING: a literal value is visible in `ps` output and shell history, and is stored in clear text in the dataset YAML (local) or sent in the request body (cloud). Prefer a Shared Vault reference.
 .TP
 .B \-\-database <db>
 Update DB database name
@@ -5279,6 +5458,9 @@ Update SQL Server minimum TLS version
 .TP
 .B \-\-api\-key <key>
 Postman API key (defaults to the `postman login` session)
+.TP
+.B \-\-json
+Emit the result as JSON instead of prose
 
 .TP Examples:
 
@@ -5288,6 +5470,73 @@ Examples:
   postman dataset source update orders\-db \e
     \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-\-host db.internal.example
 
+JDBC:
+  Rotate one credential, leaving everything else alone:
+  postman dataset source update orders \-d ./orders.dataset.yaml \e
+    \-\-var password=vault:acme/pg\-pass\-2024\-11
+
+  Remove a variable the template no longer uses:
+  postman dataset source update orders \-d ./orders.dataset.yaml \e
+    \-\-url\-template 'jdbc:postgresql://{{host}}:{{port}}/{{database}}' \-\-unset\-var schema
+
+  Merge semantics: \-\-var and \-\-prop add to what is already stored, so you need
+  not restate the whole connection. \-\-unset\-var and \-\-unset\-prop exist because
+  merging alone can never remove a key. The template is validated against the
+  MERGED values, so removing one the URL still needs fails here rather than at
+  connect time.
+
+  Run `postman dataset source test \-d <dataset> \-n <name>` afterwards to check
+  the change actually connects.
+
+
+
+.SS "dataset source test"
+Open and close a real connection using a source's stored configuration.
+
+.B Usage:
+[options]
+
+.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>
+Source to test
+.TP
+.B \-\-java\-path <path>
+Java runtime to use for a JDBC source. Machine\-local only; also read from POSTMAN_JDBC_JAVA_PATH
+.TP
+.B \-\-api\-key <key>
+Postman API key (defaults to the `postman login` session)
+.TP
+.B \-\-json
+Emit the result as JSON instead of prose
+
+.TP Examples:
+
+Examples:
+  postman dataset source test \-d ./orders.dataset.yaml \-n orders
+  postman dataset source test \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \-n orders \-\-json
+
+What it is for:
+  When a query fails, this separates "the source is broken" from "the SQL is
+  wrong". It uses the stored configuration, resolving any Vault references the
+  same way a real query would.
+
+Applies to database and JDBC sources. File and URL sources have no connection
+to test and report SOURCE_NOT_TESTABLE.
+
+JSON output (\-\-json):
+  Success: {"ok":true,"source":{"name","format"},"connectionTest":{"status":"passed"},
+            "warnings":[]}
+  Failure: {"ok":false,"error":{"code","message","remediation"}}
+  Both go to stdout, so `\-\-json 2>/dev/null | jq .` parses either way.
+  Error codes: SOURCE_NOT_FOUND (with available[]), SOURCE_NOT_TESTABLE,
+  SOURCE_NOT_JDBC, SOURCE_CONFIG_UNAVAILABLE, CONNECTION_FAILED,
+  CONN_AUTH_FAILED, CONNECTION_TIMEOUT, JAVA_NOT_FOUND, DRIVER_LOAD_FAILED,
+  HOST_PROTOCOL_ERROR, SECRET_RESOLUTION_FAILED, DATASET_COMMAND_FAILED
+
 
 
 .SS "dataset view"
@@ -5389,9 +5638,15 @@ View name
 .B \-q, \-\-query <sql>
 SQL query the view executes
 .TP
+.B \-s, \-\-source <nameOrIdOrSlug>
+Bind the view to one datasource and run the query natively against it, instead of through the federated SQLite layer. Same reference `dataset query \-s` takes
+.TP
 .B \-\-view\-id <uuid>
 Override the generated view id (local only; cloud assigns its own)
 .TP
+.B \-\-json
+Emit the result as JSON instead of prose
+.TP
 .B \-\-api\-key <key>
 Postman API key (defaults to the `postman login` session)
 
@@ -5403,6 +5658,22 @@ Examples:
   postman dataset view create \-d 14e30f6c\-1234\-1234\-1234\-cafef00dc0de \e
     \-n "Active Users" \-q "SELECT * FROM users WHERE active = true"
 
+  Native view against one source (JDBC, MySQL, Postgres, SQL Server):
+  postman dataset view create \-d ./orders.dataset.yaml \-n recent \e
+    \-\-source orders \-q "SELECT * FROM orders WHERE created_at > now() \- interval '1 day'"
+
+Federated vs native:
+  Without \-\-source the query runs through the federated SQLite layer and can
+  join across sources. With \-\-source it is sent to that one datasource in its
+  own SQL dialect, which is what JDBC sources need. Mirrors `dataset query \-s`.
+
+JSON output (\-\-json):
+  Success: {"ok":true,"view":{"id","name","target","datasourceId","viewType"},
+            "warnings":[]}
+  Failure: {"ok":false,"error":{"code","message","remediation"}}
+  Error codes: SOURCE_NOT_FOUND (with available[]), DATASET_FILE_CHANGED,
+  DATASET_FILE_UNWRITABLE, DATASET_COMMAND_FAILED
+
 
 
 .SS "dataset view delete"
@@ -5457,6 +5728,71 @@ Examples:
 
 
 
+.SS "dataset jdbc"
+Inspect JDBC drivers before attaching one to a dataset.
+
+.B Usage:
+[options] [command]
+
+.B Subcommands:
+.TP
+.B dataset jdbc inspect
+Detect Java, list driver classes, suggest a URL template and read driver properties.
+
+.SS "dataset jdbc inspect"
+Detect Java, list driver classes, suggest a URL template and read driver properties.
+
+.B Usage:
+[options] [jar...]
+
+.B Options:
+.TP
+.B \-\-driver\-class <fqcn>
+Introspect this class instead of auto\-selecting
+.TP
+.B \-\-url\-template <template>
+Use this URL template instead of the one inferred from the JAR filename
+.TP
+.B \-\-java\-path <path>
+Java runtime to use. Machine\-local only — never written to a dataset. Also read from POSTMAN_JDBC_JAVA_PATH.
+.TP
+.B \-\-json
+Emit the discovery result as JSON
+
+.TP Examples:
+
+Examples:
+  postman dataset jdbc inspect ./drivers/postgresql\-42.7.3.jar
+  postman dataset jdbc inspect ./drivers/mysql\-connector\-j\-8.4.0.jar \-\-json
+  postman dataset jdbc inspect ./a.jar ./b.jar \-\-driver\-class com.acme.Driver
+
+What it reports:
+  The Java runtime it found, every java.sql.Driver class in the artifacts,
+  a suggested URL template, that template's {{variables}}, and the
+  connection properties the driver accepts.
+
+Feeding the result into `source add`:
+  suggestedUrlTemplate      \-> \-\-url\-template
+  templateVariables[]       \-> \-\-var <name>=<value>
+  connectionProperties[]    \-> \-\-prop <name>=<value>
+  driverClass               \-> \-\-driver\-class (only needed when ambiguous)
+
+JSON output (\-\-json):
+  Success: {"ok":true,"java":{...},"drivers":[...],"suggestedUrlTemplate":"...",
+            "templateVariables":[...],"connectionProperties":[...],"warnings":[...]}
+  Failure: {"ok":false,"error":{"code":...,"message":...,"remediation":...}}
+  Error codes: JAVA_NOT_FOUND, JAVA_UNSUPPORTED, DRIVER_FILE_NOT_FOUND,
+  DRIVER_FILE_UNREADABLE, DRIVER_INCOMPATIBLE, DRIVER_LOAD_FAILED,
+  DRIVER_CLASS_NOT_FOUND, URL_TEMPLATE_INVALID, HOST_START_FAILED
+  Warning codes: DRIVER_CLASS_AMBIGUOUS, DRIVER_PROPERTIES_EMPTY,
+  DRIVER_PROPERTIES_UNAVAILABLE, URL_TEMPLATE_INVALID
+  `minimumJavaMajorVersion` is present when the artifacts declare one.
+
+Several driver classes in one JAR is reported, not an error. Re\-run with
+\-\-driver\-class to read that driver's connection properties.
+
+
+
 .SS "dependency"
 Manage workspace dependencies (Postman entities reused from other workspaces).
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.59.0",
+  "version": "1.60.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.59.0",
-    "@postman/pm-bin-macos-x64": "1.59.0",
-    "@postman/pm-bin-linux-x64": "1.59.0",
-    "@postman/pm-bin-linux-arm64": "1.59.0",
-    "@postman/pm-bin-windows-x64": "1.59.0"
+    "@postman/pm-bin-macos-arm64": "1.60.0",
+    "@postman/pm-bin-macos-x64": "1.60.0",
+    "@postman/pm-bin-linux-x64": "1.60.0",
+    "@postman/pm-bin-linux-arm64": "1.60.0",
+    "@postman/pm-bin-windows-x64": "1.60.0"
   }
 }