Skip to main content

Rate Limits

Rate limits are applied per API key and enforced at the API gateway level. All limits are measured in requests per minute with an additional burst capacity for short spikes.
Burst capacity allows you to exceed the steady-state rate limit for a short period. For example, an endpoint with 50 req/min and burst 3 means you can fire up to 3 requests in rapid succession before the 50 req/min cap is enforced.
Rate limits are per API key. Each API key has its own independent rate-limit budget — one key hitting its cap does not affect the others. Since an account can have up to 10 API keys, you can spread total throughput across them by issuing requests under different keys.Monthly quotas and resource limits stay per account, however — the analytics call quotas and report emails, plus the resource limits below (configurations, participants, minutes, and so on) are shared across all your keys. Creating more keys raises your rate-limit headroom, not these account-wide caps.

Configurations

Evaluators

Participants

Transcriptions

Analytics


Quotas

Monthly Analytics Quotas

Analytics endpoints are subject to a monthly call quota in addition to the per-minute rate limit. Quotas reset automatically on the 1st of each calendar month.
Your current usage and remaining calls are visible in the Sandbox from the user menu (top right).

Resource Limits

The following limits apply to the number of objects you can create per account.

Supported Audio & Video Formats

Need higher limits?

Default limits work for most use cases, but if your project requires more — more analytics calls, more participants, or a larger team — we can adjust them for you.

Contact us to increase your limits

Reach out to hola@heify.com and tell us what you need. We’ll get back to you quickly.

Handling 429 Errors

A 429 Too Many Requests response means either a per-minute rate limit or a monthly quota has been exceeded. Implement exponential backoff to retry gracefully: