Skip to main content
Requests to /api are rate limited per API key. Each key can make 60 requests per minute. Approved integrations can be given a higher limit of 120 requests per minute. Contact us if you need it. We also limit requests per source IP address to protect the platform. If several keys share one IP address, their combined traffic counts towards that limit.

​
When you exceed a limit

The API responds with 429 Too Many Requests and a Retry-After header giving the number of seconds to wait. The limit is measured over a rolling 60-second window. Requests keep failing for as long as you keep sending above the limit. Stop or slow down, wait for the Retry-After period, then resume.
Limits are enforced approximately. You may see a short delay before throttling starts or stops. Treat them as a ceiling to stay well under, not a quota to use up.

​
Recommendations

  • Retry 429 responses with exponential backoff.
  • Spread batch jobs out over time rather than sending them in bursts.