Postman CLI Release Notes

What's New

Syntax validation for API specifications

The postman spec lint command now includes dedicated syntax validation. Previously, specs with syntax errors would display a generic message like "Unable to lint. Please check your specification for errors." Now you see the exact syntax errors with file names, line numbers, and clear descriptions, making it much easier to fix issues in your OpenAPI specifications.

New "Issue Type" column in output

Validation results now include an "Issue Type" column that distinguishes between Syntax errors (structural/parsing issues) and Governance violations (rule-based issues). This helps you quickly identify and prioritize what to fix first.

The new column is added at the end of CSV, JSON, and table outputs to maintain backward compatibility with existing CI/CD pipelines.

Fixed collection push failing due to owner ID mismatch

Fixed an issue where postman workspace push would fail to update collections when the resource ID format didn't include the expected owner prefix.

Private API Monitoring

Private API Monitoring is available as a beta feature on all paid plans. Enterprise teams must contact their Postman Customer Success Manager to enable Private API Monitoring.

You can now set up runners using the Postman CLI to monitor internal APIs within your own infrastructure. With runners, you can run monitors on your network without exposing internal endpoints to the public internet.

To start a runner, use the following command:

postman runner start --id <id> --key <key>

Once deployed, runners appear automatically in your monitor configuration and can be used to monitor APIs in restricted networks, isolated VPCs, or private data centers.

To learn more, see Set up a runner with the Postman CLI.

New workspace management 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 . 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.