API Rate Limits and Quota Management
Prerequisites
Rate Limit Tiers
Each API plan includes request quotas measured per minute, per hour, and per day:
| Plan | Per Minute | Per Hour | Per Day |
|---|---|---|---|
| Developer | 60 | 1,000 | 10,000 |
| Growth | 300 | 10,000 | 100,000 |
| Enterprise | Custom | Custom | Custom |
Reading Rate Limit Headers
Every API response includes headers showing your current quota status:
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 247
X-RateLimit-Reset: 1713200460
X-RateLimit-Window: 60
- Limit — Total requests allowed in the window
- Remaining — Requests remaining in the current window
- Reset — Unix timestamp when the window resets
- Window — Duration of the window in seconds
Best Practices for Staying Within Limits
- Cache aggressively — Cache GET responses at the application layer. Most reference data (branch lists, product catalogues) changes infrequently
- Batch requests — Use bulk endpoints (e.g. GET /v1/accounts?ids=1,2,3) instead of N individual calls
- Implement request queuing — Smooth out bursts by queuing requests and dispatching at a controlled rate
- Monitor proactively — Set up alerts at 80% quota usage via the portal's Monitoring dashboard
- Handle 429 gracefully — Display a friendly message rather than a raw error when rate limited