Riot Games · Rate Limits

Riot Games Rate Limits

Riot enforces app-level rate limits per region and per API key, plus method-level limits on individual endpoints. Limits are applied across both the user's personal/production app and the underlying service; either layer can return 429. Limits scale with key tier (development/personal vs production), with production-key limits expandable for developers in good standing.

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

It captures 5 rate-limit definitions, measuring requests_per_second, requests_per_2_minutes, requests_per_10_seconds, requests_per_10_minutes, and varies.

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

Tagged areas include Riot Games, League of Legends, VALORANT, and Rate Limiting.

5 Limits Throttle: 429
Riot GamesLeague of LegendsVALORANTRate Limiting

Limits

Development / Personal key burst key/region
requests_per_second · second
20
Personal and development keys share this 20 req / 1 s burst limit, enforced per region.
Development / Personal key sustained key/region
requests_per_2_minutes
100
100 requests per 2 minutes, per region, on personal/development keys.
Production key burst key/region
requests_per_10_seconds
500
500 requests per 10 seconds, per region. Expandable for approved production apps in good standing.
Production key sustained key/region
requests_per_10_minutes
30000
30,000 requests per 10 minutes, per region. Expandable on request.
Method-level limits key/method/region
varies
see endpoint reference
Individual endpoints carry their own per-method limits in addition to the app-level caps; method limits surface as 429 with X-Rate-Limit-Type when triggered at the edge.

Policies

Per-Region Enforcement
All rate limits are enforced per regional shard (e.g. NA1, EUW1, KR). A single key can run against multiple regions but each region carries its own counter.
Retry-After Compliance
Clients must honor the Retry-After header on 429 responses and pause until the indicated time before retrying.
Rate Limit Type Header
When the 429 originates at the API edge, X-Rate-Limit-Type identifies whether the breach was at the application or method layer. The header is not guaranteed for 429s surfaced by the underlying service.
Production Approval
Production-key issuance and any subsequent rate-limit raise requires Developer Relations review of a working prototype and adherence to Riot's developer policies.

Sources