setlist.fm · Rate Limits

Setlistfm Rate Limits

The setlist.fm REST API is rate limited per API key. Standard keys are commonly issued with a limit of 2 requests per second and 1,440 requests per day; setlist.fm can grant higher ceilings (values around 16 requests/second and up to 50,000 requests/day have been reported for upgraded keys) on manual request. The interactive documentation does not print a fixed numeric limit, so the exact ceiling depends on the individual key. Exceeding the limit returns HTTP 429 (Too Many Requests). Clients should throttle to the documented per-second budget and back off on 429 responses.

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

It captures 3 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Music, Concerts, Setlists, Rate Limiting, and Quotas.

3 Limits Throttle: 429
MusicConcertsSetlistsRate LimitingQuotas

Limits

Requests per Second api-key
requests
2 per second (standard key; higher on request)
Standard-key default; upgraded keys have been reported around 16 req/sec.
Requests per Day api-key
requests
1440 per day (standard key; up to ~50000 on upgraded keys)
Daily quota tied to the individual API key.
Rate Limit Upgrade api-key
requests
manual approval
Higher limits requested through the API settings page and reviewed manually.

Policies

Throttle to Budget
Keep sustained request rate within the per-second budget for your key (2 req/sec on standard keys) to avoid 429 responses.
Backoff on 429
On HTTP 429 (rate limit exceeded), pause and retry with exponential backoff rather than hammering the endpoint.
Cache Results
setlist data changes slowly; cache responses client-side to stay within the daily quota.

Sources