Skip to main content
Boltcall enforces rate limits per API key to ensure fair usage across all customers. Limits vary by plan.

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 a 429 status with the following body:
Check the X-RateLimit-Reset header to determine when you can resume sending requests.

Best practices

Implement exponential backoff when retrying after a 429. Start with a 1-second delay and double it on each subsequent retry, up to a maximum of 60 seconds.
  • 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-Remaining proactively and slow down before hitting zero.

Exponential backoff example

Node.js