Optimized Routing and Increased Scrape Success
This release focuses on internal stability and performance improvements.
We upgraded our routing intelligence to use ratio-based decisions when encountering challenges. This prevents healthy connections from being prematurely escalated, resulting in faster and more cost-effective requests.
The API now distinguishes between active challenges and passive security scripts on successful pages. Successful responses are delivered to you immediately instead of triggering unnecessary retries or routing escalations.
Scraping requests are now authorized much faster thanks to optimized caching of client tiers and usage limits. This eliminates redundant validation checks per request, directly lowering overall API response latency.
Improvements
6Optimized routing on protected targets
We upgraded our routing intelligence to use ratio-based decisions when encountering challenges. This prevents healthy connections from being prematurely escalated, resulting in faster and more cost-effective requests.
Accurate success detection on secured sites
The API now distinguishes between active challenges and passive security scripts on successful pages. Successful responses are delivered to you immediately instead of triggering unnecessary retries or routing escalations.
Higher success rates on secured endpoints
We optimized our escalation logic on endpoints with strict security walls. This ensures our advanced bypass methods are reliably deployed when needed, leading to significantly higher success rates on difficult targets.
General bug fixes and improvements
Plus 8 internal improvements for better reliability and performance.
Faster API request processing
Scraping requests are now authorized much faster thanks to optimized caching of client tiers and usage limits. This eliminates redundant validation checks per request, directly lowering overall API response latency.
General improvements
This release includes general improvements and maintenance updates.
Bug Fixes
4Reliable content delivery on late timeouts
The API now preserves and delivers successfully captured page content even if a timeout occurs during the final cleanup phase. This prevents you from losing successfully retrieved data to late-stage timeout errors.
Structured errors during high concurrency
During high-concurrency bursts, the API now returns a structured 503 status instead of a generic 500 error if limits are reached. Connection handling was also optimized to make these limits much harder to hit.
Accurate organization usage charts
We fixed an issue where the billing dashboard did not display usage metrics for specific sub-organizations. Your charts and usage breakdowns now accurately reflect all team scraping activity.
Preserved proxy error details
Upstream status codes and rate limit responses from scraping and batch proxies are now passed back to your client fully intact. This ensures you can inspect exact error bodies and headers for faster troubleshooting.
Plus 27 internal changes for stability and performance.