postman-cli 1.35.2 → 1.36.0

package/man/postman.1

@@ -1,4 +1,4 @@
-.TH POSTMAN 1 "2026-05-08" "v1.35.2" "Postman CLI Manual"
+.TH POSTMAN 1 "2026-05-14" "v1.36.0" "Postman CLI Manual"
 .SH NAME
 postman \- Command\-line companion utility for Postman
 .SH SYNOPSIS
@@ -1160,7 +1160,10 @@ List SDK builds for a collection, extensible collection, or specification.
 Download SDKs from a build by its ID.
 .TP
 .B sdk connect
-Connect a collection or specification to a Git repository for automated SDK PRs
+Connect a collection or specification to a GitHub repository for automatic SDK pull requests
+.TP
+.B sdk connections
+Manage GitHub connections that drive automatic SDK pull requests
 
 .SS "sdk init"
 Create or update .postman/config.json with an SDK configuration stub.
@@ -1211,9 +1214,6 @@ Show detailed generation progress and logs
 .B \-\-log\-level <level>
 Set build log detail level. "warn" (default) shows errors/warnings inline and collapses info notes; "info" expands all log entries (default: warn)
 .TP
-.B \-\-pr
-Create pull requests to configured GitHub repositories after SDK generation
-.TP
 .B \-\-no\-track\-changes
 Disable change tracking. By default, file hashes are written into .manifest.json to enable edit detection on the next regeneration.
 .TP
@@ -1222,6 +1222,12 @@ Skip custom code merge even if user edits are detected. Forces a fresh generatio
 .TP
 .B \-\-conflict\-strategy <strategy>
 Strategy for handling merge conflicts: "mark" inserts conflict markers (default), "ours" keeps user edits, "theirs" keeps generated code
+.TP
+.B \-\-no\-emit
+Skip downloading and saving SDK artifacts to disk. Useful in CI when the build only needs to trigger server\-side pull requests.
+.TP
+.B \-\-pr
+[DEPRECATED]
 
 .TP Examples:
 
@@ -1387,7 +1393,7 @@ Examples:
 
 
 .SS "sdk connect"
-Connect a collection or specification to a Git repository for automated SDK PRs
+Connect a collection or specification to a GitHub repository for automatic SDK pull requests
 
 .B Usage:
 <provider> <id> [options]
@@ -1397,22 +1403,122 @@ Connect a collection or specification to a Git repository for automated SDK PRs
 .B \-l, \-\-language <language>
 SDK language (required) [choices: typescript, python, java, go, csharp, php, ruby, cli, kotlin, rust]
 .TP
+.B \-r, \-\-repo <owner/name>
+GitHub repository in <owner>/<name> form (alternative to \-\-repo\-owner + \-\-repo\-name)
+.TP
+.B \-\-repo\-owner <owner>
+GitHub repository owner (user or org)
+.TP
+.B \-\-repo\-name <name>
+GitHub repository name
+.TP
+.B \-b, \-\-branch <branch>
+Target branch for SDK pull requests (default: main)
+.TP
+.B \-\-push\-to\-base
+Push SDK updates directly to the base branch instead of opening a pull request (default: false)
+.TP
+.B \-\-enable\-npm\-publishing
+Inject a GitHub Actions workflow that publishes to npm on merge (TypeScript only) (default: false)
+.TP
+.B \-\-auth\-provider <provider>
+OAuth provider used by the server when pushing (choices: githubapp, github) (default: githubapp)
+.TP
+.B \-\-verbose
+Show extra logging
+.TP
 .B \-w, \-\-workspace <workspaceId>
-Workspace ID (optional)
+[DEPRECATED]
 
 .TP Examples:
 
 Providers:
-  github \- Connect to GitHub repository
+  github \- Connect to a GitHub repository
 
-Note: Currently only collections are supported for GitHub integrations. Specification support is being worked on and may be available in a future release.
+Authentication:
+  By default the server uses the installed Postman GitHub App (\-\-auth\-provider githubapp).
+  Pass \-\-auth\-provider github to use a previously\-granted user OAuth token instead.
+  If the server returns an auth error, install the GitHub App from your Postman workspace settings.
 
 Examples:
-  Connect a collection for TypeScript SDK output:
-    postman sdk connect github 12345\-abcde\-67890 \-\-language typescript
+  Connect a collection to a GitHub repo for TypeScript SDK PRs:
+    postman sdk connect github 12345\-abcde\-67890 \-\-language typescript \-\-repo my\-org/my\-sdk
+
+  Connect a specification using a non\-default branch:
+    postman sdk connect github 67890\-fghij\-12345 \-l python \-\-repo my\-org/python\-sdk \-\-branch develop
+
+  Push SDK updates straight to base instead of opening a pull request:
+    postman sdk connect github 12345\-abcde\-67890 \-l java \-\-repo my\-org/java\-sdk \-\-push\-to\-base
 
-  Connect with specific workspace:
-    postman sdk connect github 12345\-abcde\-67890 \-l python \-w my\-workspace\-id
+
+
+.SS "sdk connections"
+Manage GitHub connections that drive automatic SDK pull requests
+
+.B Usage:
+[options] [command]
+
+.B Subcommands:
+.TP
+.B sdk connections list
+List GitHub connections for a collection or specification
+.TP
+.B sdk connections delete
+Delete a GitHub connection for a collection or specification
+
+.SS "sdk connections list"
+List GitHub connections for a collection or specification
+
+.B Usage:
+[options] <id>
+
+.B Options:
+.TP
+.B \-\-refresh
+Refresh PR statuses from GitHub before listing (slower) (default: false)
+.TP
+.B \-\-json
+Output raw JSON instead of formatted text (default: false)
+.TP
+.B \-\-verbose
+Show extra logging
+
+.TP Examples:
+
+Examples:
+  List connections for a collection:
+    postman sdk connections list 12345\-abcde\-67890
+
+  Refresh PR statuses from GitHub before listing:
+    postman sdk connections list 12345\-abcde\-67890 \-\-refresh
+
+  Output raw JSON for scripting:
+    postman sdk connections list 12345\-abcde\-67890 \-\-json
+
+
+
+.SS "sdk connections delete"
+Delete a GitHub connection for a collection or specification
+
+.B Usage:
+[options] <id> <connectionId>
+
+.B Options:
+.TP
+.B \-y, \-\-yes
+Skip the confirmation prompt (default: false)
+.TP
+.B \-\-verbose
+Show extra logging
+
+.TP Examples:
+
+Examples:
+  Delete connection 42 from a collection (with confirmation):
+    postman sdk connections delete 12345\-abcde\-67890 42
+
+  Skip the confirmation prompt:
+    postman sdk connections delete 12345\-abcde\-67890 42 \-\-yes
 
 
 
@@ -1582,6 +1688,340 @@ Start mocks with fault\-injection scenarios defined in a .sim.yaml file
 .B Usage:
 [options] <filepath>
 
+.SS "search"
+Search for Postman element types (requests, collections, workspaces, and more).
+
+.B Usage:
+[command] [options]
+
+.B Options:
+.TP
+.B \-\-ownership <ownership>
+Ownership: organization (or org), external, all (default: organization)
+.TP
+.B \-n, \-\-limit <limit>
+Max results per page. Max allowed limit: 25 (default: 10)
+.TP
+.B \-\-cursor <cursor>
+Cursor for pagination
+.TP
+.B \-o, \-\-output <format>
+Output format: default (card list), json (detailed JSON) (default: default)
+.TP
+.B \-\-filter <expression>
+Filter expression (e.g. "workspaceId=ws\-123 AND visibility=public")
+.TP
+.B \-\-filter\-json <json>
+Filter as raw JSON.
+    Only a top\-level "$and" list of condition objects is supported.
+    "$or" and nested groups are not supported in \-\-filter\-json.
+    Each condition: { "<property>": { "<operator>": <value> } }.
+    If both \-\-filter and \-\-filter\-json are provided, \-\-filter\-json takes precedence.
+
+.TP Examples:
+
+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
+
+Detailed help is split by element type:
+  postman search requests \-\-help      Request filters and examples
+  postman search collections \-\-help   Collection filters and examples
+  postman search workspaces \-\-help    Workspace filters and examples
+  postman search flows \-\-help         Flow filters and examples
+  postman search specs \-\-help         API spec filters and examples
+
+Pagination: \-\-limit accepts up to 25 results. Use \-\-cursor from the previous response to paginate.
+
+
+.B Subcommands:
+.TP
+.B search requests
+Search for requests by name or keyword.
+.TP
+.B search collections
+Search for collections by name or keyword.
+.TP
+.B search workspaces
+Search for workspaces by name or keyword.
+.TP
+.B search flows
+Search for flows by name or keyword.
+.TP
+.B search specs
+Search for API specs by name or keyword.
+
+.SS "search requests"
+Search for requests 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)
+
+Request\-only filter fields:
+  collectionId        $eq, $ne, $in, $nin
+  method              $eq, $ne, $in, $nin  (GET, POST, PUT, PATCH, DELETE, etc.)
+  requestId           $eq, $ne, $in, $nin
+  type                $eq, $ne, $in, $nin
+                      Values can be like: http\-request, graphql\-request, grpc\-request, ws\-raw\-request,
+                      ws\-socketio\-request, mqtt\-request, llm\-request
+
+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 requests "login"
+  postman search requests "auth" \-\-filter "method=POST AND collectionId=collection\-uid\-1"
+  postman search requests "upload" \-\-filter "method IN POST,PUT AND workspaceId=ws\-abc123"
+  postman search requests "internal api" \-\-filter "method=POST AND privateNetwork=true"
+  postman search requests "payment" \-\-ownership external \-\-limit 5 \-\-filter "visibility=public"
+  postman search requests "auth" \-\-filter "method NIN GET" \-\-ownership org \-\-limit 10 \-\-output json
+
+
+.SS "search collections"
+Search for collections 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)
+
+Collection filter fields:
+  collectionId        $eq, $ne, $in, $nin
+  tags                $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 collections "payments"
+  postman search collections "postman" \-\-filter "visibility=public"
+  postman search collections "payments" \-\-ownership external \-\-limit 10 \-\-filter "visibility=public"
+  postman search collections "internal" \-\-filter "workspaceId IN ws\-1,ws\-2"
+  postman search collections "apis" \-\-filter "tags IN public,team\-api" \-\-output json
+
+
+.SS "search workspaces"
+Search for workspaces 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)
+
+Workspace filter fields:
+  tags                $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 workspaces "team"
+  postman search workspaces "platform" \-\-ownership organization
+  postman search workspaces "public apis" \-\-ownership external \-\-filter "visibility=public"
+  postman search workspaces "trusted workspace" \-\-filter "privateNetwork=true"
+
+
+.SS "search flows"
+Search for flows 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)
+
+Flow filter fields:
+  flowId              $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 flows "onboarding"
+  postman search flows "checkout" \-\-ownership organization \-\-limit 20
+  postman search flows "billing" \-\-filter "workspaceId=ws\-abc123"
+  postman search flows "internal" \-\-filter "flowId IN flow\-1,flow\-2"
+
+
+.SS "search specs"
+Search for API specs 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)
+
+API spec filter fields:
+  specificationId     $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 specs "openapi"
+  postman search specs "my api spec" \-\-filter "specificationId=spec\-abc123"
+  postman search specs "billing" \-\-ownership external
+  postman search specs "payments" \-\-ownership external \-\-filter "publisherIsVerified=true AND visibility=public"
+
+
 .SH SEE ALSO
 Full documentation: https://learning.postman.com/docs/postman\-cli/postman\-cli\-overview/
 .SH AUTHOR

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "postman-cli",
-  "version": "1.35.2",
+  "version": "1.36.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.35.2",
-    "@postman/pm-bin-macos-x64": "1.35.2",
-    "@postman/pm-bin-linux-x64": "1.35.2",
-    "@postman/pm-bin-linux-arm64": "1.35.2",
-    "@postman/pm-bin-windows-x64": "1.35.2"
+    "@postman/pm-bin-macos-arm64": "1.36.0",
+    "@postman/pm-bin-macos-x64": "1.36.0",
+    "@postman/pm-bin-linux-x64": "1.36.0",
+    "@postman/pm-bin-linux-arm64": "1.36.0",
+    "@postman/pm-bin-windows-x64": "1.36.0"
   }
 }