1. [    Home ](/)
2. [Guides](/guides)
3. [Best Practices](/guides?category=29)
4. API Rate Limits and Quota Management
 
 beginner Best Practices      10 min       3 steps      7 min read  

# API Rate Limits and Quota Management

  A  admin  April 15, 2026  

 

 

       

 

 

 

 

 ##     Prerequisites 

 

 

 

 

 ## On this page

  
  3 steps total 

 [    Back to top ](#main-content) 

 ## Rate Limit Tiers

Each API plan includes request quotas measured per minute, per hour, and per day:

PlanPer MinutePer HourPer DayDeveloper601,00010,000Growth30010,000100,000EnterpriseCustomCustomCustom## 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

1. **Cache aggressively** — Cache GET responses at the application layer. Most reference data (branch lists, product catalogues) changes infrequently
2. **Batch requests** — Use bulk endpoints (e.g. GET /v1/accounts?ids=1,2,3) instead of N individual calls
3. **Implement request queuing** — Smooth out bursts by queuing requests and dispatching at a controlled rate
4. **Monitor proactively** — Set up alerts at 80% quota usage via the portal's Monitoring dashboard
5. **Handle 429 gracefully** — Display a friendly message rather than a raw error when rate limited



 

 

 

 ### Tags

Tags

[Rate Limiting](/taxonomy/term/41)