***

title: Collection commands
approved: 2026-03-16T00:00:00.000Z
topictype: reference
slug: docs/postman-cli/postman-cli-collections
max-toc-depth: 2
----------------

This topic covers collection-related commands for the [Postman CLI](/docs/postman-cli/postman-cli-overview/).

You can run your collections with HTTP requests using the `postman collection run` command. With a paid plan, you can also run collections with gRPC and GraphQL requests.

You can also use the `postman collection migrate` command to migrate collections from the v2.1 JSON format to the v3 YAML format.

## `postman collection run`

This command runs a collection and displays run results in the terminal. If you're signed in to Postman, the command sends the run results to the Postman cloud. Learn how to sign in to Postman with [the `postman login` command](/docs/postman-cli/postman-cli-auth/#postman-login).

Specify the collection with its file path if you're running it locally. If you're signed in to Postman, specify the collection with its ID to send the results to the Postman cloud.

<Tip>
  You can find the collection ID in Postman. Click the <img alt="Items icon" src="https://assets.postman.com/postman-docs/aether-icons/v12/descriptive-items-stroke.svg#icon" width="20px" /> Items tab, click **Collections** in the sidebar, and select a collection. Then click the <img alt="Info icon" src="https://assets.postman.com/postman-docs/aether-icons/state-info-stroke.svg#icon" width="16px" /> **Info** tab in the right sidebar to view or copy the collection ID.
</Tip>

### Usage

```bash
postman collection run <collection> [options]
```

<ParamField path="<collection>">
  One of the following:

  * A collection file path if running locally.
  * A collection ID (UUID format) if signed in to Postman.
</ParamField>

### Options

<ParamField path="--bail [optional modifiers]">
  Specifies whether to stop a collection run on encountering the first error. `--bail` can optionally accept two modifiers: `--folder` and `--failure`. `--folder` skips the entire collection run if there are any errors. If a test fails, `--failure` stops the collection run after completing the current script.
</ParamField>

<ParamField path="--color [value]" default="auto">
  Controls colors in the CLI output. Accepts `on`, `off`, and `auto`. With `auto`, the Postman CLI attempts to automatically turn color on or off based on the color support in the terminal.
</ParamField>

<ParamField path="--cookie-jar [path]">
  Specifies the file path for a `JSON` cookie jar. This uses the `tough-cookie` library to deserialize the file.
</ParamField>

<ParamField path="--delay-request [number]" default="0">
  Specifies a delay (in milliseconds) between requests.
</ParamField>

<ParamField path="--disable-unicode">
  Replaces all symbols in the output with their plain text equivalents.
</ParamField>

<ParamField path="--environment [UID] or [file-path], -e">
  Specifies an environment file path or UID.
</ParamField>

<ParamField path="--env-var [environment-variable-name]=[environment-variable-value]">
  Specifies environment variables in a `key=value` format. Multiple CLI environment variables can be added by using `--env-var` multiple times, for example: `--env-var "this=that" --env-var "alpha=beta"`.
</ParamField>

<ParamField path="--export-cookie-jar [path]">
  Specifies the path where the Postman CLI will output the final cookie jar file after completing a run. This uses the `tough-cookie` library to serialize the file.
</ParamField>

<ParamField path="--global-var [global-variable-name]=[global-variable-value]">
  Specifies global variables in a `key=value` format. Multiple CLI global variables can be added by using `--global-var` multiple times, for example: `--global-var "this=that" --global-var "alpha=beta"`.
</ParamField>

<ParamField path="--globals [file-path], -g">
  Specifies a path to a file containing global variables. Global variables are similar to environment variables but have lower precedence and can be overridden by environment variables having the same name.
</ParamField>

<ParamField path="--integration-id [ID]">
  (This option is only supported in [Postman v11 and earlier](/v11/docs/postman-cli/postman-cli-options).) Specifies an integration ID when using an integration with CI/CD. This sends the Postman CLI results to the correct integration in Postman.
</ParamField>

<ParamField path="--iteration-count [number], -n">
  Specifies the number of times the collection will run when used in conjunction with the iteration data file.
</ParamField>

<ParamField path="--iteration-data [file-path], -d">
  Specifies the local file path to a data file (JSON or CSV) to use for each iteration.
</ParamField>

<ParamField path="-i [requestUID] or [folderUID]">
  Runs only the specified folder UID or request UID from the collection. Multiple items can be run in order by specifying `-i` multiple times, for example: `postman collection run collectionUID -i folder1UID -i folder2UID`.
</ParamField>

<ParamField path="-i [requestName] or [folderName]">
  Runs only the specified folder name or request name from the collection. If there are duplicate names, the Postman CLI runs the folder or request that appears first.
</ParamField>

<ParamField path="--ignore-redirects">
  Prevents the Postman CLI from automatically following 3XX redirect responses.
</ParamField>

<ParamField path="--insecure, -k">
  Turns off SSL verification checks and enables self-signed SSL certificates.
</ParamField>

<ParamField path="--mock [file-path]">
  Specifies the path to a mock server configuration file in JSON format. This starts a mock server using the specified configuration, runs the collection against the mock server, and then stops the mock server. Learn how to [create a mock server in your Git repository](/docs/design-apis/mock-apis/local-mock-servers).
</ParamField>

<ParamField path="--no-insecure-file-read">
  Prevents reading of files situated outside of the working directory.
</ParamField>

<ParamField path="--silent">
  Turns off terminal output.
</ParamField>

<ParamField path="--ssl-client-cert-list <path>">
  Specifies the path to a client certificates configuration (JSON).
</ParamField>

<ParamField path="--ssl-client-cert <path>">
  Specifies the path to a client certificate (PEM).
</ParamField>

<ParamField path="--ssl-client-key <path>">
  Specifies the path to a client certificate private key.
</ParamField>

<ParamField path="--ssl-client-passphrase <passphrase>">
  Specifies the client certificate passphrase (for a protected key).
</ParamField>

<ParamField path="--ssl-extra-ca-certs <path>">
  Specifies more trusted CA certificates (PEM).
</ParamField>

<ParamField path="--suppress-exit-code, -x">
  Specifies whether to override the default exit code for the current run.
</ParamField>

<ParamField path="--timeout [number]">
  Specifies the time (in milliseconds) to wait for the entire collection run to complete.
</ParamField>

<ParamField path="--timeout-request [number]" default="0">
  Specifies a time (in milliseconds) to wait for requests to return a response.
</ParamField>

<ParamField path="--timeout-script [number]" default="0">
  Specifies the time (in milliseconds) to wait for scripts to complete.
</ParamField>

<ParamField path="--verbose">
  Shows detailed information for the collection run and each request sent.
</ParamField>

<ParamField path="--working-dir [path]">
  Sets the path of the working directory to use while reading files with relative paths. This defaults to the current directory.
</ParamField>

<ParamField path="--reporters [reporter], -r [reporter]">
  Generates a local report for the collection run in the specified format: `cli`, `json`, `junit`, and `html`. If the `--reporters` option isn't specified, the `cli` report is output by default. Only the `cli` report output is supported for collections with HTTP, gRPC, and GraphQL requests. To learn more, go to [Generate collection run reports using the Postman CLI](/docs/postman-cli/postman-cli-reporters/).
</ParamField>

### Examples

```bash
postman collection run postman/collections/myCollectionName

postman collection run 12345678-12345ab-1234-1ab2-1ab2-ab1234112a12
```

Learn more at [Run a collection using the Postman CLI](/docs/postman-cli/postman-cli-run-collection/) and [Use the Postman CLI with GitHub Actions](/docs/postman-cli/postman-cli-github-actions/).

## `postman collection migrate`

Use the `postman collection migrate` command to migrate your existing v2.1 collection to the new v3 collection format.

### Usage

```bash
postman collection migrate <collection-file> [options]
```

<ParamField path="<collection-file>">
  Path to the existing v2.1 collection file to migrate.
</ParamField>

#### Options

<ParamField path="-o, --output <directory>">
  Specifies the directory to migrate your new collection to. If you don't specify a directory, the Postman CLI saves the new collection in the current directory.
</ParamField>

### Examples

```bash
postman collection migrate your-existing-collection.json
```

```bash
postman collection migrate your-existing-collection.json --output path/to/your-new-collection
```