Music release and discography collection
Use Discogs endpoints to turn music release and discography collection into repeatable API requests with documented inputs and JSON responses.
Turn the public Discogs music database into structured JSON — search across releases, masters, artists, and labels; release and master detail with formats, genres, styles, and catalog numbers; and full artist and label discographies for music catalogs, discography research, and enrichment. Credential-free.
Extract Discogs releases, masters, artists, and labels — search, detail, and discographies — as structured JSON from the public Discogs music database.
Endpoint families
5
Documented params
21
Examples
7
Live catalog snapshot
Active endpoints
7
Methods
GET
Required params
14
Schema refs
7
{
"platform": "Discogs",
"endpoint": "discogs-search",
"method": "GET",
"path": "/discogs/search",
"auth": "apiKey"
}Use cases
Extract Discogs releases, masters, artists, and labels — search, detail, and discographies — as structured JSON from the public Discogs music database.
Use Discogs endpoints to turn music release and discography collection into repeatable API requests with documented inputs and JSON responses.
Use Discogs endpoints to turn artist and label catalog enrichment into repeatable API requests with documented inputs and JSON responses.
Use Discogs endpoints to turn format, genre, and pressing research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Discogs endpoint catalog — 7 endpoints, 21 documented request parameters, and 7 published response schemas — the same catalog Docs and Playground run against.
7 documented Discogs endpoints, grouped into 5 request families — Artist, Label and Master, plus 2 more.
21 request parameters are documented across those Discogs endpoints, 14 of them required — the full input contract is public before you write any integration code.
7 of the 7 Discogs endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Discogs endpoints document their error responses (400, 404, 500 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Discogs endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/discogs/artist/{id}
/discogs/label/{id}
/discogs/master/{id}
/discogs/release/{id}
/discogs/search
Endpoint catalog
/discogs/searchSearches the Discogs database for releases, masters, artists and labels, optionally filtered to one `type`, with `page` and `per_page` (max 100). Release and master results carry country, year, formats, labels, genres, styles, catalog number and barcodes; artist and label results carry id, title and thumbnail.
MCP tool discogs_search
/discogs/release/{id}Returns a Discogs release: artists, labels, formats, tracklist, credits, identifiers, videos, images, and community want/have/rating.
MCP tool discogs_release
/discogs/master/{id}Returns a Discogs master release: the version-agnostic grouping of a release across pressings/reissues (artists, tracklist, genres/styles, videos, images, marketplace stats).
MCP tool discogs_master
/discogs/artist/{id}Returns a Discogs artist profile: real name, bio, links, name variations, aliases, and group memberships.
MCP tool discogs_artist
/discogs/artist/{id}/releasesReturns the releases and masters credited to a Discogs artist, identified by the required `id`. Paged with `page` (default 1) and `per_page` (default 50, max 100). Each entry has its `id`, `type` (`release` or `master`), title, artist, role, format, label, year, thumbnail, and want and collection counts, alongside the total item count and page count.
MCP tool discogs_artist_releases
/discogs/label/{id}Returns the profile of a Discogs label by its required label `id`: name, profile text, contact info, website URLs, images, data quality rating, and Discogs page URI. The parent label and the list of sub-labels are included, and the parent label appears only when the label has one.
MCP tool discogs_label
/discogs/label/{id}/releasesLists the releases on a Discogs label, identified by the required label `id`. Paged with `page` (default 1) and `per_page` (default 50, max 100). Each entry has its release `id`, title, artist, format, catalogue number (`catno`), status, year and thumbnail, and the response reports the total item count across all pages.
MCP tool discogs_label_releases
Related APIs
Media & Streaming
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
How to scrape Discogs
Discogs is the reference database for physical and digital music releases. Crawlora's Discogs endpoints return search, release/master detail, and artist/label discographies as normalized JSON — no Discogs API token, rate-limit juggling, or proxy setup.
A search across releases/masters/artists/labels, a release or master by id, or an artist/label with its releases.
Pass a query or a Discogs id to Crawlora's Discogs endpoint (e.g. /discogs/search, /discogs/release, /discogs/artist/{id}/releases).
Receive title, country, formats, labels, genres, styles, catalog numbers, and barcodes as clean JSON, with fields varying by release / master / artist / label.
Batch across search pages and discographies to build catalogs for music research, cataloging, or enrichment.
FAQ
Send a search query or a Discogs id to Crawlora's Discogs endpoints and get releases, masters, artists, and labels as structured JSON — search, detail, and discographies — without holding a Discogs API token. Collect public database data and respect Discogs' terms.
Yes — /discogs/artist/{id}/releases and /discogs/label/{id}/releases return paginated discographies, and /discogs/master and /discogs/release return per-title detail with formats, genres, styles, and catalog numbers.
Collecting publicly accessible music database data (releases, artists, labels) is generally permissible if you respect Discogs' terms of use, robots directives, rate limits, and applicable law. This is for public data you are authorized to collect.