Postman CLI troubleshooting and FAQ
This page answers common questions and problems reported for the Postman CLI (postman). For a specific command’s own options, see its command reference page.
I have two copies of the Postman CLI installed
If you installed the Postman CLI with both npm and the curl-based script, your system may have two copies of the postman binary, and which one runs depends on your PATH environment variable’s directory order. See Troubleshooting on the Install page for the exact steps to check which binary is active and remove the one you don’t want.
Does the Postman CLI support Alpine Linux?
No. Linux support excludes Alpine Linux distributions, due to libc compatibility requirements. See Install the Postman CLI for supported platforms.
Why can’t I use an API key with collection run or performance run in the EU region?
--postman-api-key on postman collection run and postman performance run is only supported in the US region. If your organization uses Postman EU Data Residency, sign in with postman login --region eu instead of passing an API key directly to these two commands. See Authenticate and configure for the full picture of how region and credentials interact.
How is the Postman CLI different from Newman?
The Postman CLI is Postman’s current, actively developed command-line tool, and supports features Newman doesn’t, including monitors, mock servers, flows, and the collection v3 format required for Native Git workflows. Newman only runs collections, and can’t run collections created or updated in Postman v12 and later. If you have existing Newman scripts, see Migrate from Newman to the Postman CLI for a command mapping and migration steps.
Where do I report a bug or request a feature?
Run postman feedback "<your feedback>" from the command line to submit feedback about CLI usability, gaps, or improvement suggestions directly to Postman.