What is Rate Limiting?
Rate limiting is a strategy used to control the amount of incoming and outgoing traffic to a network or API. By limiting the number of requests a user can make within a specific timeframe, we ensure that the Talview platform remains stable, secure, and available for all users. Without rate limits, a single high-volume user—whether intentional or due to a coding error (like an infinite loop)—could degrade the performance of the system for everyone else.Handling Rate Limits
When your integration exceeds the allowed number of requests, the Talview Graph API will return a specific error response.HTTP 429 Too Many Requests
If you are rate limited, the API will respond with an HTTP 429 status code. Your system should be prepared to handle this code gracefully.Best Practices
To avoid being rate limited and to ensure a smooth integration, we recommend the following practices:- Implement Exponential Backoff: If you receive a 429 error, do not retry immediately. Instead, wait for a short period and then retry. If it fails again, increase the wait time exponentially (e.g., 1s, 2s, 4s, 8s).
- Optimize Queries: Use GraphQL’s capability to fetch only the data you need. Avoid making multiple small queries if a single, larger query can retrieve the necessary information.
- Cache Data: If you are requesting data that doesn’t change frequently (like catalog details or user roles), cache that information on your server instead of requesting it repeatedly.
- Batch Operations: When possible, use bulk operations or mutations rather than individual requests for each item.