Zyte API frequently asked questions#
How many concurrent requests can I send?#
Zyte API rate limiting is based on requests per time.
In practice, your maximum concurrency depends on the requests per minute of your API key (500 by default, can be increased for free) and the average response time of your requests, which depends on the target website and your requests parameters.
Here are some examples (see the math here):
RPM limit |
Response time |
Maximum concurrency |
|---|---|---|
500 |
200 ms |
2 |
500 |
2 s |
17 |
500 |
20 s |
167 |
We do set a 2000 concurrency limit per IP address.
Is there a response size limit?#
The size limit of browserHtml and httpResponseBody (before base64-encoding) is 10 MB. Longer responses are truncated. HTTP compression does not affect this limit.
Can I set a more granular geolocation?#
geolocation only supports country granularity.
However, websites seldom limit content by IP address at a lower granularity. Provided you use the right country, you should be able to get content for any specific country subdivision (ZIP code, state, etc.).
The way to get content targeted at a specific country subdivision is usually through cookies. The way to get the right cookies depends on the target website:
On some websites you can use our setLocation action or some other actions to configure the target subdivision.
Tip
You can use sessions to minimize the amount of browser requests you need.
On some websites you can manually set a cookie that forces content for the target subdivision.
On some websites you may need to start a session and configure that session for the target subdivision.
Can I override the User-Agent header?#
You can on HTTP requests, but Zyte API may override your value for certain websites if needed for ban avoidance.
You cannot on browser requests.