Rate Limiting
The Okasie Partner API implements rate limiting to ensure fair usage and system stability.Default Limits
| Limit Type | Value |
|---|---|
| Requests per minute | 120 |
| Window size | 60 seconds |
| Burst allowance | Up to 5 req/s |
Need higher limits? Contact [email protected] to discuss custom rate limits for your integration.
Rate Limit Headers
Every API response includes rate limit information:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests per window |
X-RateLimit-Remaining | Remaining requests in current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Example Response Headers
Handling Rate Limits
When you exceed the rate limit, you’ll receive a429 Too Many Requests response:
Retry-After header indicating seconds to wait:
Best Practices
Implement exponential backoff
Implement exponential backoff
When receiving 429 errors, wait and retry with increasing delays:
Track rate limit headers
Track rate limit headers
Monitor headers to avoid hitting limits:
Use bulk endpoints
Use bulk endpoints
For large data sets, use
/listings/bulk-upsert to process up to 100 items per request instead of individual calls.Implement caching
Implement caching
Cache responses where appropriate to reduce API calls.
Use incremental sync
Use incremental sync
Use
updatedSince parameter to only fetch changed data instead of full syncs.Sync Scheduling Recommendations
| Sync Type | Recommended Interval | Notes |
|---|---|---|
| Full sync | Daily (off-peak) | Use pagination with pageSize=200 |
| Incremental sync | Every 5-15 minutes | Use updatedSince parameter |
| Real-time updates | As needed | Use individual PUT/DELETE calls |