Do you need to automate management of Postman API resources, such as collections, environments, mocks, monitors, and APIs? Me, too!
In the past, we’ve had a couple of options:
- Orchestrate HTTP requests to the Postman API via
curland shell scripts
- Craft workflows in Postman collections that can be executed via newman
Both options are powerful ways to interact with the Postman API, and yet they also may not be the right fit for certain use cases.
To fit these other use cases, I’d like to introduce
postmanctl, a CLI for interacting directly with the Postman API.
postmanctl tool supports just about everything that’s available today via the Postman API.
Some use cases worth considering, that could be made easier with
- Get quick access to Postman collection data without switching contexts while working on the command line. (See:
postmanctl describe collection --help.)
- Automatically fork a collection to stage in-progress changes introduced by source control. (See:
postmanctl fork collection --help.)
- Pull API schemas managed in Postman’s API Builder to validate against internal standards and guidelines. (See:
postmanctl get schema --helpalong with output options
- Iterate over environment variables to execute security and compliance checks. (See:
postmanctl get env [environment-id] -o json.)
I’d love to hear what use cases you may have, as well! Feel free to post here or reach out. Issues can be managed on the GitHub repo, though I’m happy to also answer questions here.
See the installation instructions (binary, homebrew, build from source) in the README documentation. Binaries are available for Windows, macOS, and Linux.
Feel free to reach out if you’d like to explore a deeper demo to examine how
postmanctl can help solve your use cases!