Iteration Layer API requests are rate-limited per organization using a sliding window of 100 requests per minute. All API keys belonging to the same organization share the same rate limit bucket.
How Rate Limits Work
Every response includes rate limit headers:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1709312400-
X-RateLimit-Limit— Maximum requests allowed per minute -
X-RateLimit-Remaining— Requests remaining in the current window -
X-RateLimit-Reset— Unix timestamp when the window resets
How to Handle a 429 Response
When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header indicating how many seconds to wait:
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
Retry-After: 42
Implement exponential backoff to retry requests gracefully. A simple strategy: wait for the number of seconds in the Retry-After header before retrying.
Need A Higher Limit?
If your workflow regularly approaches the default rate limit, contact support@iterationlayer.com.
Include the API endpoint, expected request volume, burst pattern, organization name, and whether requests are synchronous or webhook-based. This helps us review whether a higher limit, batching, or an async workflow is the right fit.