/musicbrainz/labels/releases

POST /api/musicbrainz/labels/releases

Price: 5 credits

List the release catalog of a label by MBID or URL

How to use it

List the release catalog of a MusicBrainz label by label MBID or URL. Optionally filter by release status. Returns each release's title, status, packaging, date, country, barcode, artist credits, label info (catalog numbers), release events, parent release group, formats and track count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• label string required — MusicBrainz label MBID (UUID) or full label URL (examples: "68803e28-86fe-4a95-985f-8e493795ab31"; minLength: 1)
• count integer required — Max number of releases to return (min: 1)
• status string nullable — Restrict to releases with this status (one of: "official", "promotion", "bootleg", "pseudo-release", "withdrawn", "cancelled")

Response

• @type string (default: "MusicBrainzReleaseBrowseRow")
• id string required
• url string required
• status string nullable
• packaging string nullable
• date string nullable
• country string nullable
• barcode string nullable
• disambiguation string nullable
• artist_credit array (default: [])
  • @type string (default: "MusicBrainzArtistCredit")
  • name string nullable
  • join_phrase string nullable
  • artist object nullable
    • @type string (default: "MusicBrainzArtistRef")
    • id string nullable
    • name string nullable
    • sort_name string nullable
    • disambiguation string nullable
    • type string nullable
• label_info array (default: [])
  • @type string (default: "MusicBrainzLabelInfo")
  • catalog_number string nullable
  • label object nullable
    • @type string (default: "MusicBrainzLabelRef")
    • id string nullable
    • name string nullable
    • sort_name string nullable
    • type string nullable
    • label_code integer nullable
    • disambiguation string nullable
• release_events array (default: [])
  • @type string (default: "MusicBrainzReleaseEvent")
  • date string nullable
  • area object nullable
    • @type string (default: "MusicBrainzAreaRef")
    • id string nullable
    • name string nullable
    • sort_name string nullable
    • type string nullable
    • disambiguation string nullable
    • iso_3166_1_codes array (default: [])
    • iso_3166_2_codes array (default: [])
• release_group object nullable
  • @type string (default: "MusicBrainzReleaseGroupStub")
  • id string nullable
  • url string nullable
  • primary_type string nullable
  • secondary_types array (default: [])
  • first_release_date string nullable
  • disambiguation string nullable
• formats array (default: [])
• track_count integer (default: 0)

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Label not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.