> ## Documentation Index
> Fetch the complete documentation index at: https://developer.ammdistro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Updating a release

> Send the release again with the same ID to change it.

To change a release, send the whole release again with the same `releaseId`. There's no separate update endpoint and no partial update: the body you send becomes the release.

## When you can update

| Status | Can update? |
| - | - |
| `draft` | Yes |
| `changes_requested` | Yes |
| Anything else | No: `409 release_locked` |

## What an update changes

* **Metadata, artists and credits** are replaced with what you send.
* **Tracks** are matched to the existing ones, then updated. A track you leave out is removed. A new one is added.
* **Files** you leave out are kept. A different URL, or `upload: true` again, replaces a file.
* **An identical body** changes nothing; the response has `changed: false`.

## How tracks are matched

Each track you send is matched to an existing track:

1. by its `externalId`;
2. otherwise by ISRC;
3. otherwise by disc and track number.

Use `externalId` on every track. Then you can reorder tracks, retitle them or add an ISRC, and each keeps its uploaded audio. Without it, moving a track to a new position can make it count as a new track, and its audio has to be sent again.

## Updating after changes are requested

If review sends a release back, its status is `changes_requested`. Send the corrected release with `PUT`, check it with `validate`, then `submit` again.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.