/discogs/masters

POST /api/discogs/masters

Price: 1 credit

Get Discogs master release details by ID or URL

How to use it

Get full details of a Discogs master release (the parent record grouping all editions/pressings) by master ID or master URL. Returns title, artists, genres, styles, tracklist, images, videos, the main and most recent release references, and marketplace availability.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• master string required — Discogs master ID (e.g. '96559') or full master URL (examples: "96559", "https://www.discogs.com/master/96559-Rick-Astley-Never-Gonna-Give-You-Up"; minLength: 1)

Response

• @type string (default: "DiscogsMaster")
• id integer required
• url string required
• year integer nullable
• artists array (default: [])
  • @type string (default: "DiscogsReleaseArtist")
  • id integer nullable
  • name string nullable
  • anv string nullable
  • role string nullable
  • join string nullable
  • tracks string nullable
• genres array (default: [])
• styles array (default: [])
• tracklist array (default: [])
  • @type string (default: "DiscogsTrack")
  • position string nullable
  • type string nullable
  • duration string nullable
  • artists array (default: [])
    • @type string (default: "DiscogsReleaseArtist")
    • id integer nullable
    • name string nullable
    • anv string nullable
    • role string nullable
    • join string nullable
    • tracks string nullable
  • extraartists array (default: [])
    • @type string (default: "DiscogsReleaseArtist")
    • id integer nullable
    • name string nullable
    • anv string nullable
    • role string nullable
    • join string nullable
    • tracks string nullable
• images array (default: [])
  • @type string (default: "DiscogsImage")
  • type string nullable
  • image string nullable
  • thumbnail string nullable
  • width integer nullable
  • height integer nullable
• videos array (default: [])
  • @type string (default: "DiscogsVideo")
  • uri string nullable
  • description string nullable
  • duration integer nullable
  • is_embed boolean (default: false)
• data_quality string nullable
• main_release_id integer nullable
• main_release_url string nullable
• most_recent_release_id integer nullable
• most_recent_release_url string nullable
• versions_url string nullable
• for_sale_count integer (default: 0)
• lowest_price number nullable

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 — Master 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.