Postman CLI

learning.postman.com ↗

Run saved Postman collection tests from a terminal or CI pipeline, and lint API specifications.

SI Score
75/100
Pricing
Freemium AI reading, not confirmed
Free plan
Not confirmed
Sign-up required
Not confirmed

Ask SI about Postman CLI

Answers use saved listing facts and recorded sources.
Homepage screenshot
Screenshot of the Postman CLI homepage

What it does

Postman CLI brings part of Postman's API workflow to the command line. Developers can run saved collections locally or in a CI/CD job and view results in the terminal, while the CLI also provides API specification linting. It is useful when tests already live in Postman collections and need to run as part of a build. Local collection execution and cloud reporting have different account and plan requirements.

Use Postman CLI when the test cases are already represented as a Postman collection and need to run outside the desktop interface. Install the CLI using one of Postman's documented methods, then point a command at the collection to execute it locally or from a CI job. The terminal reports the collection run, giving a build a command-line check without converting its requests into a separate test library.

The CLI also includes API-spec linting, which lets a team check an API definition as part of its workflow. If results need to be sent to Postman Cloud, the documentation describes sign-in or an API key for the relevant cases; a local run does not automatically mean the result has been uploaded. Keep credentials in the CI secret store rather than in the collection file.

Postman offers a free plan as well as paid plans, and the CLI docs mark some capabilities as plan-dependent. In particular, the reviewed documentation says collection runs for gRPC and GraphQL require a paid plan. The pages checked did not state the CLI's own software license, so this record describes access and plan gates without making an open-source claim.

Strengths

  • Collection runs can be launched from a local terminal or CI/CD pipeline, with results reported in the terminal.
  • The CLI documentation describes API-spec linting as well as collection execution.
  • Official installation guidance covers npm, shell installers for macOS/Linux/WSL, and PowerShell for Windows.

Watch out for

  • Some collection workflows are plan-gated: the reviewed docs say gRPC and GraphQL collection runs require a paid plan.
  • Sending results to Postman Cloud may require a Postman sign-in or API key, so cloud reporting needs a separate credential setup.

Best for

  • Running saved Postman API collections as a build or release check
  • Linting API specifications from a command-line development workflow

Sources