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 a429 Too Many Requests response:
429 response
Retry strategy
We recommend implementing exponential backoff with jitter when you receive a429 response.
Best practices
Cache responses when possible
Cache responses when possible
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.Use webhooks instead of polling
Use webhooks instead of polling
Instead of polling for new meetings or transcripts, set up webhooks to receive real-time notifications when data is ready.
Batch your requests
Batch your requests
When fetching multiple resources, use list endpoints with appropriate
limit values instead of making individual requests for each item.Monitor your usage
Monitor your usage
Check the
X-RateLimit-Remaining header proactively and throttle your requests before hitting the limit.