Skip to main content
The Platform enforces rate limits to restrict the number of API requests a user, account, or application can make within a timeframe. It helps prevent a single user or service from consuming disproportionate resources that could degrade the service for others. When a rate limit is exceeded, subsequent requests will fail with one of the following error messages:
  • Minute-based Limit: “You’ve exceeded the per-minute rate limit. Please wait for sometime before retrying.”
  • Hour-based Limit: “You’ve exceeded the hourly rate limit. Please wait for sometime before retrying.”

Automation AI

The Platform enforces rolling rate limits within a dynamic timeframe. Requests are monitored against both sixty-second and one-hour limits. As long as neither limit is exceeded, the application can continue making requests. However, if the one-hour limit is breached, all further requests are blocked, even if the sixty-second limit is still within bounds.

API Rate Limit Matrix

Contact Center AI

Contact Center AI enforces rate limits to restrict the number of API requests an account/application can make within a timeframe. Requests are monitored against a sixty-second limit. As long as the limit isn’t exceeded, the account/application can continue making requests.

API Rate Limit Matrix

Quality AI

Quality AI enforces rate limits to restrict the number of API requests an account/application can make within a timeframe. Requests are monitored against a sixty-second limit. As long as the limit isn’t exceeded, the account/application can continue making requests.

API Rate Limit Matrix

Monitor API Usage

All APIs have rate limits, and calls that exceed the limit fail with the error: Rate limit for this API has been reached. Please try again after some time. To help you monitor your usage, every response from an Automation AI API, whether it succeeds or fails, includes the following rate limit headers.
The header values are specific to the API group you called. They are not a combined count across all API groups. Different API groups can have different rate limit thresholds.

Best Practices

  • Spread out calls evenly to avoid traffic spikes.
  • Use filters to limit the data response size and avoid calls that request overlapping data.
  • When the limit has been reached, stop making API calls. Wait for the specific time period to pass. Alternatively, implement a backoff strategy where your application automatically reduces its request frequency and retries failed requests after a calculated delay.
Need a higher or custom rolling Rate Limit? Contact support.