Rate Limits
ReportFlow enforces rate limits to ensure fair usage and platform stability. This guide explains the limits, how to monitor your usage, and best practices for staying within your quota.
Per-Minute Limits
Requests are capped per API key per minute.
Response Headers
Check remaining quota in every response.
Graceful Handling
Implement backoff when limits are reached.
Default limits
| Plan | Requests / Minute | Requests / Day |
|---|---|---|
| Starter | 60 | 10,000 |
| Professional | 300 | 100,000 |
| Enterprise | Custom | Custom |
Rate limit headers
Every API response includes headers to help you monitor usage:
X-RateLimit-Limit— Your per-minute limit.X-RateLimit-Remaining— Requests remaining in the current window.X-RateLimit-Reset— Unix timestamp when the window resets.
Handling 429 errors
When you exceed the limit, the API returns a 429 Too Many Requests status. Implement exponential backoff: wait 1 second, then retry. If you hit 429 again, double the wait time (2s, 4s, 8s, etc.) up to a maximum of 60 seconds.
Best practices
- Batch requests when possible (e.g., fetch multiple clockouts in one call).
- Cache responses locally to reduce redundant API calls.
- Use webhooks for real-time events instead of polling.
- Monitor your usage dashboard to spot trends before hitting limits.
Next steps
- Authenticate requests in API Authentication.
- Explore endpoints in REST API Endpoints.
- Set up event notifications in Webhooks.