Skip to main content

Rate Limiting

The Okasie Partner API implements rate limiting to ensure fair usage and system stability.

Default Limits

Need higher limits? Contact info@okasie.be to discuss custom rate limits for your integration.

Rate Limit Headers

Every API response includes rate limit information:

Example Response Headers

Handling Rate Limits

When you exceed the rate limit, you’ll receive a 429 Too Many Requests response:
The response includes a Retry-After header indicating seconds to wait:

Best Practices

When receiving 429 errors, wait and retry with increasing delays:
Monitor headers to avoid hitting limits:
For large data sets, use /listings/bulk-upsert to process up to 100 items per request instead of individual calls.
Cache responses where appropriate to reduce API calls.
Use updatedSince parameter to only fetch changed data instead of full syncs.

Sync Scheduling Recommendations

Example: Rate-Limited Sync Script

Next Steps

Error Handling

Handle API errors gracefully

Incremental Sync

Efficient sync patterns