Rate Limit
Learn about Deeply OpenAPI's rate limiting system, including per-application request quotas, throttling policies, and error handling. Understand how to monitor your API usage, handle rate limit responses, and request quota increases for your production needs. This guide covers best practices for managing API request frequency and avoiding service disruptions.
Overview
Rate limiting is implemented to ensure fair usage of our API resources and maintain service stability for all users. This document outlines our rate limiting policies and what to do when you reach these limits.
Rate Limit per API Endpoint
Each API endpoint is limited to:
- 10 requests per second
- 1,000 requests per minute
These limits are tracked per endpoint and reset automatically each second.
Requesting Higher Limits
If you need higher limits for your application, please contact our support for additional quotas.
Rate Limit Exceeded
If you exceed the rate limit, you will receive a 429 status code with the following response body:
{
"detail": {
"message": "Rate limit exceeded. Please try again in 60 seconds.",
"limit": 1000,
"remaining": 0,
"reset": 1640995200
}
}Best Practices for Handling Rate Limits
To avoid hitting rate limits, we recommend:
- Implement Request Queuing: For bulk operations, queue requests and process them at a controlled rate (maximum 10 requests per second).