Skip to main content
Each API key makes 600 calls an hour. A call without a valid key counts against its IP address instead. A workspace runs at most five calls at once, across all its keys. Send the next call of a sync when one answers, rather than all of them together. These limits count requests, and they are separate from the plan’s monthly event allowance. The allowance counts the events the workspace’s sites collect, and calls to the API never spend it. Get the event usage reports the events used this period, the plan’s limit and when the count resets. That route answers while the workspace is locked, when every other route answers 403.

​
Budget headers

Every response states the key’s hourly budget in the RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset headers, and in the structured RateLimit-Policy and RateLimit fields. Each endpoint page describes them.

​
Refused calls

A refused call answers 429 with a Retry-After header, in seconds. Its code says which limit it ran into:
  • RATE_LIMITED: the key has used its 600 calls for the hour.
  • TOO_MANY_CONCURRENT_REQUESTS: the workspace already has five calls running.
A report that runs into the time cap answers 422 with the code QUERY_TIMEOUT. Ask again for a shorter range.