Best practices for staying within limits
- Optimize request timing: Distribute requests evenly to avoid sudden spikes that might exceed the rate limit. Consider scheduling or batching requests when possible.
- Implement backoff logic: If you reach the rate limit, add retry logic with a brief delay. This approach helps manage occasional bursts without impacting the application.
- Monitor usage: Regularly track your request volume to identify high-traffic periods or patterns, allowing for adjustments to stay within the limit.
- Set alerts: If available, set up alerts to notify you when request volumes approach the rate limit.
Summary: The absentify API has a rate limit of 150 requests per second per IP. Properly managing request timing, retry logic, and monitoring helps prevent outages and ensures efficient API usage.
Higher rate limits
If you need higher throughput, you can upgrade to 1500 requests per second for $100/€100 per month. To enable this, please contact our support team.List endpoint date range limit
Thestart…end window for GET /requests, GET /requests_per_day, and GET /absences_per_day may span at most 1826 days (5 years). Wider or inverted ranges return 400; retrieve longer periods in consecutive, smaller windows.