> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-commands-guide/distribution-commands.md).

# Distribution Commands

* [getDistributionStatus](#getdistributionstatus)
* [getDistributionURL](#getdistributionurl)
* [getDistributionVersions](#getdistributionversions)
* [createDistribution](#createdistribution)
* [deleteDistribution](#deletedistribution)

#### getDistributionStatus

***

Retrieves the creation status of one or more agent installers (distributions), such as in progress, completed, or failed.

<details>

<summary>Arguments</summary>

| Argument Name     | Description                                 | Required |
| ----------------- | ------------------------------------------- | -------- |
| distribution\_ids | A comma-separated list of distribution IDs. | Required |

</details>

<details>

<summary>Outputs</summary>

**Core.Distribution.id** *string*

The distribution ID.

**Core.Distribution.status** *string*

The status of the distribution.

</details>

#### getDistributionURL

***

Downloads an agent installer (distribution) package and returns it as a file entry in the War Room. Use the getDistributionStatus command to verify that the distribution creation process has been completed and is ready for download.

<details>

<summary>Arguments</summary>

| Argument Name    | Description                                                                              | Required |
| ---------------- | ---------------------------------------------------------------------------------------- | -------- |
| distribution\_id | The ID of the distribution.                                                              | Required |
| package\_type    | The package type to download. Possible values are: upgrade, sh, rpm, deb, pkg, x86, x64. | Required |

</details>

**Outputs**

There are no outputs for this command.

#### getDistributionVersions

***

Retrieves the list of agent versions available per operating system for creating a new agent installer (distribution).

**Arguments**

There are no input arguments for this command.

<details>

<summary>Outputs</summary>

**Core.DistributionVersions.windows** *string*

Available Windows agent versions.

**Core.DistributionVersions.linux** *string*

Available Linux agent versions.

**Core.DistributionVersions.macos** *string*

Available macOS agent versions.

</details>

#### createDistribution

***

Creates an agent installer (also known as a distribution) used to deploy or upgrade the agent on endpoints, and polls until creation completes. The returned distribution ID can be used with getDistributionURL to download the installer.

Note: This is a polling command.

<details>

<summary>Arguments</summary>

| Argument Name         | Description                                                                                 | Required |
| --------------------- | ------------------------------------------------------------------------------------------- | -------- |
| name                  | Name of the installation package.                                                           | Required |
| platform              | Platform for the installation package. Possible values are: windows, linux, macos, android. | Required |
| package\_type         | Type of installation package. Possible values are: standalone, upgrade.                     | Required |
| agent\_version        | Agent version. Required for every platform except android.                                  | Optional |
| description           | Free-text description of the distribution.                                                  | Optional |
| interval\_in\_seconds | Interval in seconds between each poll. Default is 20 seconds.                               | Optional |
| timeout\_in\_seconds  | Polling timeout in seconds. Default is 300 seconds.                                         | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.Distribution.id** *string*

The ID of the created distribution.

**Core.Distribution.name** *string*

The name of the distribution.

**Core.Distribution.platform** *string*

The platform for which the distribution was created.

**Core.Distribution.package\_type** *string*

The package type of the distribution.

**Core.Distribution.agent\_version** *string*

The agent version baked into the distribution.

**Core.Distribution.description** *string*

The description of the distribution.

</details>

#### deleteDistribution

***

Deletes an agent installer (also known as a distribution). This does not affect endpoints where the agent has already been installed.

<details>

<summary>Arguments</summary>

| Argument Name    | Description                           | Required |
| ---------------- | ------------------------------------- | -------- |
| distribution\_id | The ID of the distribution to delete. | Required |

</details>

**Outputs**

There are no outputs for this command.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-commands-guide/distribution-commands.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.