Rate limits

Each key may make 600 requests per minute. Every response tells you where you stand:

Header
`X-RateLimit-Limit`	Requests allowed per minute for this key
`X-RateLimit-Remaining`	Requests left in the current window
`Retry-After`	Only on `429`: seconds to wait

When the limit is exceeded the API answers 429 rate_limited:

{ "error": { "code": "rate_limited", "message": "Too many requests" } }

Staying within limits

Use per_page=100 and updated_since instead of re-reading everything.
Cache reference data (locations, users, checklists) and refresh it a few times a day.
Run heavy exports at night in your company's time zone.
Use separate keys for separate integrations — limits are per key.
On 429 wait Retry-After seconds, then continue; don't retry immediately in a loop.

Need a higher limit for a large network? Write to [email protected] with the key prefix and the expected volume.