Limits by plan
Rate limit headers
Every API response includes the following headers so you can monitor your current usage:429 Too Many Requests
When you exceed the rate limit, the API returns a429 status with the following body:
X-RateLimit-Reset header to determine when you can resume sending requests.
Best practices
- Cache responses — for read-heavy operations like listing agents or leads, cache results locally for 30–60 seconds rather than polling the API.
- Use webhooks — instead of polling for state changes (e.g., call completed, lead updated), subscribe to webhook events to receive push notifications.
- Batch operations — use pagination parameters (
limit,page) to retrieve larger datasets in fewer requests. - Monitor headers — track
X-RateLimit-Remainingproactively and slow down before hitting zero.
Exponential backoff example
Node.js