Rate Limits
Overview
Zuva API implements rate limiting as a measure to prevent denial-of-service (DoS) attacks and to ensure fair use of resources among all users. Rate limiting helps maintain the stability and reliability of the API, ensuring that no individual or organization can overwhelm the system with excessive requests.
Rate Limit Details
The default rate limit for each organization is set to 18,000 requests per minute, which is equivalent to 300 requests per second.
Key Points:
- Requests per minute: 18,000 requests
- Requests per second: 300 requests
- Rate Limit Scope: This limit applies to each organization individually. Each organization has its own rate limit quota, separate from others.
Rate Limiting in Action
If your organization exceeds the rate limit, the Zuva API will respond with HTTP 429 Too Many Requests status code, indicating that the rate limit has been exceeded.
Increasing Your Rate Limit
If your organization requires a higher rate limit than the default, you can request an increase by reaching out to our support team.
To request a rate limit increase, please contact us via email at: support@zuva.ai
In your email, kindly include the following details:
- Organization name
- Specific rate limit requirements (e.g., number of requests per minute or second)
- Reason for the increase (if applicable)
Our support team will review your request and respond with the next steps.
Best Practices
Monitor Request Rates: Regularly monitor your API usage to ensure you stay within the rate limit.
Efficient Requests: Make sure to use the API efficiently by batching requests where possible and avoiding unnecessary frequent calls.
Handle Rate Limiting Gracefully: Implement proper error handling in your code to manage HTTP 429 responses, including retry mechanisms with backoff.
On This Page