Rate Limit Policies
To provide a more stable and efficient user experience, we have implemented rate limit policies to ensure the best possible performance of our API for all users.
Last updated
To provide a more stable and efficient user experience, we have implemented rate limit policies to ensure the best possible performance of our API for all users.
Last updated
Overall Limit and Application For all public endpoints of the application, the rate limit is set to 500 requests per minute. This limit is applied per IP address or valid authentication token, ensuring that each entity (IP or token) has a fair usage quota.
Rate Limit Operation
Request Limit: Each valid IP or authentication token is allowed up to 500 requests per minute to the public endpoints of the application.
Time Windows: The request count is tracked in 1-minute time windows, resetting every new minute.
Rate Limit Feedback: When the 500 requests per minute limit is reached by a specific IP or token, subsequent requests within the same 1-minute period will receive a response with HTTP status code 429 (Too Many Requests).
To avoid hitting the request limit, we recommend following these best practices:
Support and Contact If you encounter issues related to rate limits or need a custom limit for specific needs, please contact our support team at support@zapsign.com.br or WhatsApp +55 11 4040-1991.
For more details, please visit the original documentation.
Implement Caching: Use caching techniques to reduce the number of repeated requests to the server.
Request Optimization: Aggregate multiple operations into a single request when possible.
Error Management: Implement exponential backoff logic to handle rate limit exceeded responses (HTTP 429).