Lastfm Rate Limits
Last.fm enforces rate limits at the originating IP / API key level. The documented guidance is approximately 5 requests per second per originating IP. Sustained excess yields account suspension. The API does not publish standard RFC 9239 RateLimit headers and instead returns numeric Last.fm error codes (notably code 29 — Rate limit exceeded — and code 26 — Suspended API key). Scrobble batches are hard-capped at 50 scrobbles per request.
Lastfm Rate Limits is the machine-readable rate-limit profile for Last.fm on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, across the free and commercial tiers, measuring requests_per_second, scrobbles_per_request, and bytes_total.
Limit state is signalled in the limit, remaining, reset, 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 response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Music, Scrobbling, Rate Limiting, and Throttling.
limitremainingresetretryAfter
generated, dated 2026-05-29.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.