Skip to main content
releaseId is your own ID for the release: 1 to 128 letters, digits, ., _, : or -. Use the ID your system already has (a catalog number works well). Sending the same ID again updates that release; see Updating a release.

Example

Release fields

string
required
The release title, without the version.
string
For example Deluxe or Remixes.
string
Single, EP, Album or Compilation. If left out, it’s set from the track count: 1–3 tracks Single, 4–6 EP, 7 or more Album.
date
required
The date the release goes live in stores, as YYYY-MM-DD.
string
12 or 13 digits with a valid check digit. Leave it out and one is assigned when the release is approved. Required for catalog transfers.
string
Your catalog number.
string
default:"en"
The language of the metadata, as a code such as en, es or pt-BR.
object
required
{ "primary": …, "secondary": … }. Each is a genre name or ID from GET /delivery/reference/genres. Secondary is optional.
string
The copyright holder for the release, without the year. Defaults to your account’s default, then to the first artist.
string
The sound recording copyright holder, without the year. Same defaults as cLine.
Defaults to the year of releaseDate (or of originalReleaseDate for a transfer).
array
required
The release’s artists. At least one must be a primary artist. See Artists.
object
The cover. See Files.
array
required
1 to 100 tracks. See Tracks.
object
Marks the release as a catalog transfer. See Catalog transfers.
date
For transfers only: the date the release first came out.
string
Needed only when the key covers more than one account. See Accounts.

Payload errors

All problems in a body come back together, each with the path into your request:
A body that passes these checks can still be incomplete for submission, for example a track without a production credit. Validate lists those.