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, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions, measuring requests_per_minute.
Limit state is signalled in the rateLimit, rateLimitUsed, rateLimitRemaining, and retryAfter response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
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.
rateLimitrateLimitUsedrateLimitRemainingretryAfter
generated, dated 2026-05-29.
Limits
Policies
Sources
- https://www.discogs.com/developers
- https://www.discogs.com/developers#page:home,header:home-rate-limiting
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.