Qobuz · Rate Limits

Qobuz Rate Limits

Rate-limit model for the Qobuz Music API v0.2. Qobuz does not publicly document explicit per-endpoint rate limits or quota headers. The API is a partner-only interface accessed via app_id and app_secret credentials issued by Qobuz; usage boundaries are governed by the API Terms of Use and partner agreement rather than published numeric thresholds. Community-developed client libraries (qobuz-dl, QobuzApiSharp, gobuz) implement exponential backoff on HTTP 429 responses, indicating that rate limiting does occur in practice. Streaming URL generation endpoints (track/getFileUrl) require request signing and are the most latency-sensitive operations.

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

It captures 4 rate-limit definitions.

The profile also includes response codes documented for throttled, quotaExceeded, and unauthorized.

Tagged areas include Music Streaming, Rate Limiting, and Hi-Res Audio.

4 Limits Throttle: 429 Quota: 429
Music StreamingRate LimitingHi-Res Audio

Limits

application
Exact per-second or per-minute request caps are not publicly documented. Community libraries use exponential backoff on HTTP 429. Partners should implement respectful request pacing and cache metadata results to avoid redundant catalog queries.
request
Streaming URLs returned by track/getFileUrl are time-limited signed URLs. The TTL is not publicly documented but URLs must be used promptly after generation. URL generation requires a fresh MD5 signature with the current Unix timestamp.
user
The user_auth_token returned by user/login is cached by client libraries for the duration of the session. The exact expiry is not publicly documented; clients should handle 401 responses by re-authenticating.
request
Search and list endpoints accept limit and offset parameters for pagination. Maximum page size is not publicly documented; community libraries default to 50 results per page for catalog search operations.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/qobuz-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.