Zyte API rate limits#
Zyte API limits the number of requests per minute (RPM). Each API key has a rate limit that can be increased. Additional rate limits may apply.
Rate-limited requests receive a rate-limiting response at no cost and can be retried.
API key rate limit#
To increase your rate limit, see Increasing rate limits.
Other rate limits#
Additional rate limits may apply:
Website limits: Each website has its own rate limit to prevent issues on target sites.
Account-website limits: Each account has per-website limits to ensure fair access.
Temporary limits: Applied during high demand to ensure platform stability.
See also
Increasing rate limits#
Temporary increases
For short-term needs (single job, specific dates), open a support ticket at least 24 hours in advance with:
Target API key
Desired RPM
Target websites
Start and end dates
Permanent increases
Concurrency#
Rate limits are based on requests per minute, not concurrent requests.
Your maximum concurrency depends on:
Your RPM limit
Average response time of target sites
Estimation formula:
max concurrency ≈ RPM limit ÷ 60 × avg response time (seconds)
Examples:
RPM limit |
Avg. response time |
Max. concurrency |
---|---|---|
500 |
0.2 s |
2 |
500 |
2 s |
17 |
500 |
20 s |
167 |