Getting Started
Rate Limiting
The Invoice Falcon API uses a token-bucket algorithm to manage traffic. Each store is allocated a fixed budget of request points that refills over time.
The Invoice Falcon API uses a token-bucket algorithm to manage traffic. Each store is allocated a fixed budget of request points that refills over time.
Default limits
| Parameter | Value |
|---|---|
| Bucket size | 40 points |
| Refill window | 60 seconds |
| Cost per request | 1 point |
A fresh bucket lets you burst up to 40 requests, after which you must wait for points to refill.
Response headers
Every response includes headers so you can track your remaining budget:
| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum points in the bucket |
X-RateLimit-Remaining | Points still available |
X-RateLimit-Reset | Seconds until the bucket fully refills |
Exceeding the limit
When you run out of points the API returns 429 Too Many Requests. Wait for the number of seconds indicated in X-RateLimit-Reset before retrying.
Best practices
- Cache responses where possible to reduce unnecessary calls.
- Respect the
Retry-After/X-RateLimit-Resetheader instead of polling in a tight loop. - If you need higher limits, contact us at support@invoicefalcon.com.
