The response time for each request varies significantly based on the API version and the complexity of the security challenge being handled. Under optimal network and server conditions, you should expect the following benchmarks:
Performance by Version
| API Version | Typical Latency | Handling Logic |
|---|---|---|
| Scrapingbypass V1 | 100 – 300 ms | Standard request forwarding and TLS/JA3 impersonation. |
| Scrapingbypass V2 | 2 – 10 seconds | Full JavaScript execution, Turnstile/Challenge solving, and polling. |
Why V2 Takes Longer
Unlike V1, which performs a direct handshake, the Scrapingbypass API V2 engine must interact with the target site's security layer. This includes:
- JS Challenge Execution: Running the target's JavaScript to prove the request is from a real browser.
- Turnstile/WAF Solving: Computing the necessary validation tokens.
- Polling Mechanism: Continuous monitoring of the challenge status before the final data payload is delivered.
Factors Affecting Latency
While the above figures represent ideal scenarios, real-world latency is influenced by:
- Target Site Performance: Slow response times from the destination server will increase the total API round-trip time.
- Proxy Node Location: Geographic distance between the proxy exit node and the target server.
- WAF Complexity: High-intensity Cloudflare or Akamai challenges may require additional computation cycles within the V2 engine.
Optimization Tip
For high-frequency data collection where Cloudflare JS challenges are not present, use V1 to achieve sub-second latency. Switch to V2 only when dealing with sites protected by Turnstile or interactive WAF challenges.
