> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/api-reference/software-delivery-agent-apis/release-orchestration.md).

# Release Orchestration

Work with releases, release groups, and freezes using the Harness Release Orchestration API.

The Release Orchestration API lets you work with releases, release groups, and freezes in Harness Release Orchestration.

## Request basics

* **Account ID**: Send your Harness account identifier in the `Harness-Account` header on every request. Go to **Account Settings**, then **Overview**, to find it. It is also in your browser URL: `app.harness.io/ng/account/<YOUR_ACCOUNT_ID>/...`.
* **API key token**: Send it in the `x-api-key` header. Go to [Manage API keys](https://developer.harness.io/harness-platform/use-harness-platform/automation/api/add-and-manage-api-keys) to create a key and token.
* **Organization and project IDs**: Where an endpoint accepts them, send `orgIdentifier` and `projectIdentifier` as query parameters to set the scope. Go to [Organizations and projects](https://developer.harness.io/harness-platform/use-harness-platform/organizations-and-projects) to find these identifiers.
* **Base URL**: Send requests to `https://app.harness.io/gateway/rmg/api`, followed by the endpoint path.

## Example request

List the releases in a time range:

```bash
curl -X POST "https://app.harness.io/gateway/rmg/api/release/list?expectedStartTs=START_MS&expectedEndTs=END_MS" \
  -H "x-api-key: $HARNESS_API_KEY" \
  -H "Harness-Account: ACCOUNT_ID" \
  -H "Content-Type: application/json" \
  -d '{}'
```

Replace `START_MS` and `END_MS` with Unix timestamps in milliseconds, and `ACCOUNT_ID` with your account identifier. Set `HARNESS_API_KEY` to your API key token. To limit the list to an organization or project, add a `scopes` array to the request body.

## Find an endpoint

Endpoint paths are relative to the base URL. This reference has one page for each of these groups:

* **Releases**: Create ad hoc releases, list and fetch releases, and run actions on them. List releases with `POST /release/list`, and fetch one with `GET /release/{releaseId}`.
* **Release Groups**
* **Freeze**
* **YAML Schema**

To learn how releases, release groups, and processes fit together before you call the API, go to [Get started with Release Orchestration](https://developer.harness.io/release-orchestration/new-to-release-orchestration/getting-started).
