Limitations

Rate limits

To maintain system stability and performance, the Player Profiling API enforces rate limits on incoming requests. Rate limits specify the maximum number of requests that can be made in a given time frame, typically measured in requests per second (RPS). If the rate limit is exceeded, the API will return a HTTP 429 Too Many Requests response, and further requests will be throttled until the rate limit window resets. Implement exponential backoff strategies in your applications to handle rate limiting gracefully.

Requests per second
300

---

Burst

The rate limit controls sustained traffic over time, while the burst limit defines the number of requests the API can handle concurrently, meaning requests run in parallel. If the burst limit is exceeded, the system responds with HTTP 429 Too Many Requests . These limits together provide more robust and flexible traffic control, especially in scenarios with variable or unpredictable load.

Burst requests
200