To keep the API reliable for everyone, Ondorse limits how many requests a client can send. The limits are generous for normal integrations and exist to stop abuse and runaway scripts.
| Limit | Applies to | Value |
|---|---|---|
Write requests (POST, PUT, PATCH, DELETE) | Each API key | 300 per minute |
| All requests | Each source IP address | 20,000 per 5 minutes |
Read requests (GET) are not limited per API key, but they count toward the per-IP limit.
When a limit is exceeded
The API answers 429 Too Many Requests with a Retry-After header (in seconds) and a JSON body:
HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json
{"detail": "Too many requests"}Requests are counted over a sliding window, so you can send again once enough of the window has passed.
Recommendations
- On a
429, wait for theRetry-Afterdelay, then retry with exponential backoff. - Spread bulk operations (imports, mass updates) over time instead of sending them in one burst.
- Reuse data you have already fetched rather than polling the same resource in a tight loop.
- If your use case needs higher limits, contact support at [email protected] with your account and the volume you expect.
These limits may evolve. We announce changes in the changelog.