Rate limits
The API allows at least 300 requests per minute per client. If you go over, you get:
HTTP/1.1 429 Too Many RequestsRetry-After: 23RateLimit-Limit: 300RateLimit-Remaining: 0RateLimit-Reset: 23{ "error": "rate_limited", "details": "Too many requests in a short time. Wait a moment and try again."}Every response carries the RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, so you can slow down before you hit the limit.
Good practice
Section titled “Good practice”- On
429, wait the number of seconds inRetry-After, then retry. - On
5xxor a network error, retry with exponential backoff (for example 1 s, 2 s, 4 s, up to a minute). - Poll background jobs every few seconds, not in a tight loop.
Other limits
Section titled “Other limits”| Limit | Value |
|---|---|
| File size | 25 MB per file |
| Files per upload request | 25 |
Page size (take) for cases |
1–100, default 50 |
Page size (take) for tasks |
1–250, default 100 |
Page size (take) for case events |
up to 500, default 100 |