Rate limits
Requests are limited per business, per minute.
The limit
By default each business may make 120 requests per minute across all v1 endpoints. The window is fixed and resets at the top of each minute.
Headers
Every response includes your current standing:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the window. |
X-RateLimit-Remaining | Requests left in the current window. |
X-RateLimit-Reset | Unix timestamp when the window resets. |
Retry-After | Seconds to wait — sent only on a 429. |
Being rate limited
When you exceed the limit you receive a 429 with a Retry-After header.
429 Response
{
"error": {
"type": "rate_limited",
"message": "Rate limit exceeded. Try again after the window resets."
},
"meta": { "request_id": "req_1a2b3c4d5e6f7a8b" }
}
Handling it well
- Read
X-RateLimit-Remainingand slow down before you hit zero. - On a 429, wait for
Retry-Afterseconds, then retry. - Use exponential backoff with jitter for repeated retries.
- Batch work and cache responses that don't change often (like cars and drivers).
Need a higher limit for a high-volume dispatch integration?
Get in touch through the Help Center.