The limit
60
requests
60 s
rolling window
1 key
one limit, shared by REST and MCP
When you go over
You get a429 rate_limit_exceeded with a Retry-After header of 60 seconds. Nothing is charged for a request that was refused.
429 Too Many Requests
Working through a big list
- Send one request at a time, or a few in parallel, and wait for
Retry-Afterwhen you hit a 429. - Use an
Idempotency-Keyper contact so a retry never charges twice. - For thousands of contacts, upload a CSV in the app instead. It runs in the background and has no rate limit.