How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Discogs User Collection API

Manage a user's record collection.

Discogs User Collection API is one of 8 APIs that Discogs publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User Collection. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 3 paths, and defines 8 schemas. It is described by OpenAPI 3.1.1, at version v2.0.

Requests are made against a single base URL, https://api.discogs.com.

4 operations 3 paths 8 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
v2.0
Base URL
https://api.discogs.com
Authentication
API Key, API Key, OAuth 2.0
Terms of Service
Resource Areas
1

Authentication & Security 3

Discogs User Collection API declares 3 security schemes for authenticating requests. An API key is passed in the header as Authorization (DiscogsToken). An API key is passed in the header as Authorization (DiscogsKeySecret). It supports OAuth 2.0 (OAuth1) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

  • DiscogsToken — Discogs personal access token in header: 'Discogs token={token}'.
  • DiscogsKeySecret — Discogs consumer key + secret in header: 'Discogs key={key}, secret={secret}'.
  • OAuth1 — OAuth 1.0a flow modeled as OAuth2 for tooling. Required for write actions on behalf of other users.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

User Collection 4

Manage a user's record collection.

GET
/users/{username}/collection/folders
Discogs Get Collection Folders
getCollectionFolders 1 param → 200401404
POST
/users/{username}/collection/folders
Discogs Create a Collection Folder
createCollectionFolder 1 param body → 201401
GET
/users/{username}/collection/folders/{folder_id}/releases
Discogs Get Collection Items by Folder
getCollectionItemsByFolder 6 params → 200401404
POST
/users/{username}/collection/folders/{folder_id}/releases/{release_id}
Discogs Add Release to Collection Folder
addReleaseToCollectionFolder 3 params → 201401404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ReleaseSummary (11 properties), ArtistSummary (7 properties), CollectionRelease (6 properties), LabelSummary (5 properties). Each schema is shown below with its type and property counts.

LabelSummary
object
5 properties
Error
object
1 property
ReleaseSummary
object
11 properties
CollectionRelease
object
6 properties
CollectionFolder
object
4 properties
ArtistSummary
object
7 properties
ReleaseFormat
object
4 properties
Pagination
object
Details for paginated results.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

discogs-user-collection-api-openapi.yml Raw ↑

Other APIs Discogs publishes across the network.

Discogs Database API
Discogs Image API
Discogs Inventory Management API
Discogs Marketplace API
Discogs User Identity API
Discogs User Lists API
Discogs User Wantlist API
Where this information came from

This is an independent, third-party profile of Discogs User Collection API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.