Skip to main content

Rate limit tiers

Rate limits are applied per API key and vary by plan. Limits are measured in requests per minute (RPM).
Burst allowance lets you briefly exceed your base limit for short spikes. Sustained traffic above your base limit will still be throttled.

Rate limit headers

Every API response includes headers that tell you your current rate limit status:
Example response headers

Handling rate limits

When you exceed your rate limit, the API returns a 429 Too Many Requests response:
429 response

Retry strategy

We recommend implementing exponential backoff with jitter when you receive a 429 response.

Best practices

Meeting data and transcripts rarely change. Cache responses on your side to reduce the number of API calls. Use the ETag header for conditional requests.
Instead of polling for new meetings or transcripts, set up webhooks to receive real-time notifications when data is ready.
When fetching multiple resources, use list endpoints with appropriate limit values instead of making individual requests for each item.
Check the X-RateLimit-Remaining header proactively and throttle your requests before hitting the limit.

Endpoint-specific limits

Some resource-intensive endpoints have additional per-endpoint limits regardless of your plan:
Need higher limits? Contact our sales team about Enterprise plans with custom rate limits and dedicated infrastructure.