Discogs · Rate Limits

Discogs Rate Limits

Discogs throttles requests by source IP address and authentication mode. Authenticated callers (Discogs token, key+secret, or OAuth 1.0a) get a higher per-minute window than unauthenticated callers. Every response includes X-Discogs-Ratelimit headers so clients can self-pace. Discogs also requires every request to carry a unique User-Agent string; generic UAs (curl, Python urllib) are blocked. Limits are not configurable via dashboard — contact api@discogs.com to negotiate a higher cap for high-volume integrations.

Discogs Rate Limits is the machine-readable rate-limit profile for Discogs on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests_per_minute.

The profile also includes 6 backoff/retry policies defined and response codes documented for throttled, unauthorized, and forbidden.

Tagged areas include Rate Limiting, Music, Marketplace, and Catalog.

3 Limits Throttle: 429
Rate LimitingMusicMarketplaceCatalog

Limits

Authenticated requests (Discogs token, key+secret, or OAuth 1.0a) account/IP
requests_per_minute · minute
60
Applies across all endpoints; high-volume callers can request a raise from api@discogs.com.
Unauthenticated requests IP
requests_per_minute · minute
25
Strongly discouraged for production use; use a Discogs token for the higher cap.
Image asset retrieval (OAuth-signed) account
requests_per_minute · day
1000
Soft cap; images are proxied through the API and intended for in-app display, not bulk scraping.

Policies

User-Agent required
Every request must carry a unique, descriptive User-Agent (e.g. 'MyDiscogsApp/1.0 +https://example.com'). Default UAs from common HTTP libraries are blocked.
Rate-limit headers
Each response returns X-Discogs-Ratelimit (cap), X-Discogs-Ratelimit-Used (current count), and X-Discogs-Ratelimit-Remaining (remaining). Use these to self-throttle.
Backoff on 429
On HTTP 429, honor the Retry-After header (when present) and back off exponentially. Do not retry tight loops.
Bulk data via XML dumps
For population-level analysis, use the monthly XML data dumps on S3 rather than crawling the API.
Raise via support
High-volume commercial integrations can request a higher rate cap by emailing api@discogs.com with the application name, expected throughput, and use case.
OAuth + image retrieval
Image URLs returned by other endpoints must be fetched with an OAuth-signed request to /images/{filename}; unauthenticated image fetches will be blocked.

Sources