Rate Limits

Understanding API Rate Limiting

To ensure the reliability and stability of our API for all users, we enforce rate limiting. Rate limiting controls the number of requests that can be made to our API within a specific time period. If too many requests are made within a short timeframe, you may receive a 429 Too Many Requests response.

How Rate Limiting Works

Our API uses a sliding window rate limiting approach. This means that your requests are monitored over small intervals within a larger time window, ensuring that request spikes are spread more evenly. If the total number of requests you make exceeds the allowed limit during this window, your requests will be temporarily throttled.

• Limit: You can make a certain number of requests within a defined time window.
• Throttle Response: If you exceed the limit, the API will respond with a 429 Too Many Requests status code until the window resets.
• Retrying: The rate limit window resets over time, so you’ll be able to make requests again shortly after hitting the limit. You should implement retry logic with exponential backoff to handle rate limiting gracefully.

Best Practices

To avoid reaching the rate limit:

• Monitor your usage: Keep track of the number of requests you are making and anticipate when you might reach the limit.
• Implement exponential backoff: If you receive a 429 response, introduce a delay before retrying your requests.
• Optimize your requests: Minimize unnecessary API calls. For example, avoid polling the API too frequently for updates, as this can quickly exhaust your rate limit. Instead, consider reducing the frequency of non-urgent queries.

By following these guidelines, you can prevent disruptions to your service and ensure a smoother integration with our API.