Postman Release Notes

What’s New

[BETA] Workspace Sync Commands

New workspace management commands have been introduced as a public beta to sync locally exported and saved collections and environments with Postman workspaces:

• postman workspace prepare – Prepares and validates local files for a cloud push.

• postman workspace push– Creates, updates, or deletes entities in the target workspace; validates IDs globally; updates local files with server-assigned IDs. (Also runs prepare first.)

Required Configuration

A new declarative config file .postman/config.json defines the workspace ID and entity paths (collections, environments, specs, flows).

For example:

{ "schemaVersion": "1", "workspace": { "id": "your-workspace-id" }, "entities": { "collections": ["./collections/name.postman_collection.json"], "environments": ["./environments/name.postman_environment.json"], "specs": ["./specs/name.yaml"] } }

Flags

• --no-prepare: Skip the prepare step.

• --yes: Bypass all prompts (for CI/CD use).

What’s New

Introducing the Postman CLI manual page

The Postman CLI now supports a manual page with a complete list of supported commands and options. Use the man postman command to return the manual page.

Support for linting API specifications by path to the root file

The Postman CLI now supports linting OpenAPI 3.0 specifications using a local file path to the root file. To run the command, use postman spec lint <path-to-root-file>. By default, the command lints specifications against API governance rules applied to all workspaces. Use the --workspace-id option to lint specifications against API governance rules applied to a particular workspace.

What's New

Support for signing in from the browser

The Postman CLI now supports securely signing in and authenticating with Postman from the browser. Use the postman login command, without the --with-api-key option, and Postman prompts you to sign in from the browser.

Support for running a monitor

The Postman CLI now supports running a monitor in your team. Use the postman monitor run command to run the monitor on the Postman cloud and return the results in the terminal. The results are also sent to your monitor's results in the Postman app.

Note: The Postman CLI now requires access to the https://gateway.postman.com domain. If your network has outbound restrictions, allowlist the domain before upgrading to the latest version.

What's New

Support for linting multi-file OpenAPI 3.0 specifications

Available on Enterprise plans

The Postman CLI now supports linting multi-file OpenAPI 3.0 specifications against your team's configured API governance rules. To run the command, use postman spec lint <spec-id>. Use the --fail-severity option to trigger an exit failure code for rule violations at or higher than the specified severity level: HINT, INFO, WARNING, or ERROR (default). Use the --output option to set the output format to either JSON or CSV.

Learn more about linting API specifications with the Postman CLI.

What's New

• The Postman CLI now supports targeting the EU region.
• To use the EU region, simply log in with an EU region API key—the Postman CLI will automatically detect and display the current region in its output.
  • For commands that support supplying the API key in the command itself, using a key of the EU region will automatically make the Postman CLI use the EU region’s corresponding resources for that invocation.
• The following commands are currently available on the EU region:
  • postman collection run
    • Please note that the --integration-id option is not supported for this command as integrations are not available on the EU DC yet.

Security patches

• Postman runtime version has been upgraded to version 7.44.1 to address a security vulnerability.

What's New

• The Postman CLI now supports linting OpenAPI 3.0 API Specifications taking into consideration rules enforced via workspace groups as per the team's API Governance configuration.

• To use, execute: postman spec lint <spec-id>

Command Line Options

• --fail-severity [severity], -f This option allows the command to exit with a failure status if issues at or above the specified severity level are detected.
  Severity levels include: HINT, INFO, WARNING, ERROR (default).

• --output [format], -o This option lets you specify the output format of the linting results. This can be either json or csv.

What’s New

• We’re excited to announce that Postman CLI now supports built-in reporters, enabling you to generate local reports for your collection runs seamlessly. Available reporters: JSON, JUnit and CLI. postman collection run <collection-id> --reporters json,junit,cli postman collection run <collection-id> -r json,junit,cli
• The JSON reporter introduces a new, compact schema that provides key information on the run execution and failures. Additionally, for workflows built around Newman, reports can also be generated with the Newman JSON schema using the following command. postman collection run <collection-id> -r json --reporter-structure newman