Rate Limits and Access Patterns

1. The game API has rate limits of approximately 200 requests per minute
2. Rate limit violations trigger a 429 HTTP error
3. Recommended configuration: Implement a throttler at 100 requests per 30 seconds for safety

Recommended Access Patterns

Safe to access:

1. Ongoing games
2. Match histories
3. Leaderboards

Optimization Strategy

Use a dual-API approach:

1. Game API

1. Primary use: Fetching ongoing observable games
2. Expected usage: 10-15 requests per minute

2. Community API

1. Use for match histories and leaderboards
2. Benefits from higher rate limits
3. Reduces load on main game API

Actions to Avoid

1. Accessing chat channels
2. Accessing presence-related features
3. Making POST requests
4. Creating lobbies via API
5. Any other write operations

Error Handling

Implement logging for rate limit errors (HTTP 429) to monitor API usage patterns