Throttling

Overview

To ensure the stability and reliability of our API services, we have implemented a throttling policy. This policy helps to prevent abuse and ensures fair usage of resources across all users.

Throttling Limits

• Requests per Minute: Each account is allowed up to 60 requests per minute.

Throttling Behavior

If an account exceeds the allowed number of requests per minute, additional requests will be throttled. Throttled requests will receive a 429 Too Many Requests response status code.

Handling Throttling

When you receive a 429 Too Many Requests response, it is important to handle this gracefully in your application. Here are some strategies:

• Retry After Delay: Check the Retry-After header to determine how long to wait before making a new request.
• Exponential Backoff: Implement an exponential backoff strategy to progressively increase the wait time between retries.
• Rate Limit Information: Use the X-RateLimit-Remaining and X-RateLimit-Limit headers to track and manage your request rate more efficiently.

Example Response

When throttling is triggered, the API will respond with a 429 Too Many Requests status code. Below is an example of such a response:

{
  "message": "Too many requests",
  "code": "too_many_requests",
  "trace_id": "a7772ecc-5ad2-4045-aa33-e09211ce2b5b"
}

Best Practices

To avoid hitting the rate limits, consider the following best practices:

• Batch Requests: Whenever possible, batch your requests to minimize the number of API calls.
• Cache Responses: Cache the responses from the API to reduce the number of requests made for the same data.
• Optimize Request Frequency: Ensure your application only makes necessary requests and avoids redundant calls.
  By adhering to these guidelines and managing your request rate effectively, you can ensure smooth and uninterrupted use of the API.

For further assistance or questions regarding the throttling policy, please contact our support team.