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

# Delivery package

> How to build the release ZIP (DDEX ERN metadata + audio) you upload as a delivery

A delivery package is a ZIP file containing the DDEX ERN message and the audio files for **one release**. Upload it with [`distribution.files.post`](https://docs.musixmatch.com/enterprises/distribution/api/deliveries/distribution-files-post), then create the delivery with [`distribution.delivery.post`](https://docs.musixmatch.com/enterprises/distribution/api/deliveries/distribution-delivery-post).

> [card] [Download the example package](https://s.mxmcdn.net/pro/api/docs/musixmatch-ddex-ern-example.zip)
>
> A complete ERN 3.8.2 delivery with two tracks. All names and identifiers are fictional and the audio files are generated tones. Use it as a template, not as a real delivery.

## Package structure

```
delivery.zip
└── <UPC>/                    # release folder, named after the UPC/EAN
    ├── <UPC>.xml             # the ERN message
    └── audio/
        ├── track-1.mp3       # audio for the first track
        └── track-2.mp3       # audio for the second track
```

* **Format:** ZIP archive (`application/zip`), up to **1 GB**.
* **One release per ZIP**, with exactly one ERN message.
* The ERN XML goes inside the release folder, as in the tree above.

## ERN version

Use **ERN 3.8.2**. Contact [apisupport@musixmatch.com](mailto:apisupport@musixmatch.com) before delivering any other version.

## Linking tracks to audio files

Each track is a `SoundRecording` in the `ResourceList`, and its audio file is linked through its `FileName`:

```xml theme={null}
<SoundRecording>
  <SoundRecordingId><ISRC>ZZEXA2600001</ISRC></SoundRecordingId>
  ...
  <SoundRecordingDetailsByTerritory>
    <TechnicalSoundRecordingDetails>
      <File>
        <FileName>track-1.mp3</FileName>    <!-- must match a file in the ZIP -->
        <FilePath>audio/</FilePath>
      </File>
    </TechnicalSoundRecordingDetails>
  </SoundRecordingDetailsByTerritory>
</SoundRecording>
```

* `FileName` must exactly match a file in the ZIP, including case and extension. File names must be unique within the ZIP.

## Fields Musixmatch reads

Element paths are relative to the ERN message root (`NewReleaseMessage`).

| Field | Element path | Notes |
| - | - | - |
| ISRC | `ResourceList/SoundRecording/SoundRecordingId/ISRC` | |
| Audio file | `ResourceList/SoundRecording/SoundRecordingDetailsByTerritory/TechnicalSoundRecordingDetails/File/FileName` | |
| Release type | `ReleaseList/Release/ReleaseType` | `Album`, `Single` or `EP`. |
| UPC / EAN | `ReleaseList/Release/ReleaseId/ICPN` | |
| Artist | `ReleaseList/Release/ReleaseDetailsByTerritory/DisplayArtistName` | Main display artist. |
| Cover art | `ResourceList/Image/ImageDetailsByTerritory/TechnicalImageDetails/File/FileName` | Optional. JPEG or PNG, up to 20 MiB. |

Musixmatch does not read any other element, but the message must still validate against the ERN 3.8.2 schema.

## Audio files

Supported formats:

* MP3
* WAV
* FLAC (native FLAC only, FLAC inside Ogg is not supported)
* AIFF (AIFF-C is not supported)

Any other format, such as M4A/MP4, raw AAC, Ogg Vorbis, Opus or WMA, is not supported.

Each audio file can be up to **100 MiB**. There are no requirements on sample rate, bit depth or bitrate.


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