Browse the docs
Documentation

Rate limits

How many requests an API key can make, and what to do with a 429.

Each API key can make 120 requests per minute and 10,000 requests per day. All of your keys together can make 240 requests per minute and 20,000 requests per day, so spreading calls over more keys doesn't raise your total.

When you go over

The API answers 429 with the code rate_limited and a Retry-After header that gives the number of seconds to wait:

HTTP/1.1 429 Too Many Requests
Retry-After: 17
Content-Type: application/json

{ "success": false, "error": { "type": "error", "code": "rate_limited", "message": "Too many requests. Please try again later." } }

Wait at least that long before the next request. Retrying straight away only gets another 429.

Subscribing a webhook and reading recent events (GET /hooks/sample) have tighter limits of their own. A 429 from either carries Retry-After the same way.

GET /search has its own limit too: 60 searches per minute per person, counted together with the searches they make in VoiceCap. A 429 from it also carries Retry-After.

Staying under the limits

  • Subscribe to a webhook rather than polling for new meetings.
  • If you do poll, pass since (or completedAfter on GET /meetings) so each call returns only what's new.
  • Ask for bigger pages with limit rather than making more calls.