Enhanced Request Diagnostics and API Stability
This release introduces saved request configuration snapshots for scraper jobs to simplify debugging and request auditing. We have also significantly reduced wait times on unreachable target sites and resolved false authentication errors under heavy API load. In addition, error classification for modern web applications and target server failures has been substantially improved.
Scraper jobs now store a snapshot of submitted options like JavaScript rendering, timeouts, and cost caps. This allows you to easily audit and reproduce request behavior from your dashboard.
When target servers are unreachable, requests now fail fast instead of running extended retries. This reduces response times by up to 80 seconds on offline targets and avoids extra charges.
High server load no longer triggers false unauthorized errors or IP security flags on valid API keys. When authentication capacity is briefly saturated, the API now returns 503 with error auth_unavailable and a Retry-After header instead of 401, and WebSocket connections close with code 1013 (Try Again Later) instead of 4001. Retry after the indicated delay; do not rotate the key. Newly created or regenerated API keys also authenticate immediately without lockouts.
New Features
1Job Request Option Snapshots
Scraper jobs now store a snapshot of submitted options like JavaScript rendering, timeouts, and cost caps. This allows you to easily audit and reproduce request behavior from your dashboard.
Improvements
3Fast Failures on Unreachable Target Sites
When target servers are unreachable, requests now fail fast instead of running extended retries. This reduces response times by up to 80 seconds on offline targets and avoids extra charges.
Accurate Target Health Monitoring
Domain health tracking now ignores user-level rate limits and skipped retry steps. This prevents false domain pauses and keeps your extraction pipelines running smoothly.
General bug fixes and improvements
Plus 11 internal improvements for better reliability and performance.
Bug Fixes
4Modern Web App Content Validation
Pages containing large inline hydration state are no longer incorrectly flagged as empty shells. This ensures complete content extraction on modern web applications.
Precise Target Error Classification
Target site server errors and 5xx status codes are now accurately classified as origin errors rather than security blocks. This improves status reporting clarity and retry routing.
Reliable Target Connection Timeouts
Connection timeouts during target site checks are now handled more accurately. Inconclusive proxy connections are distinguished from down targets for predictable request resolution.
Automatic Recharge Status Resolution
Fixed an issue where automatic balance top-ups could stay stuck pending after payment gateway errors. Failed recharges now resolve cleanly so you can retry or update billing details.
Security
1API Key Authentication Stability
High server load no longer triggers false unauthorized errors or IP security flags on valid API keys. When authentication capacity is briefly saturated, the API now returns 503 with error auth_unavailable and a Retry-After header instead of 401, and WebSocket connections close with code 1013 (Try Again Later) instead of 4001. Retry after the indicated delay; do not rotate the key. Newly created or regenerated API keys also authenticate immediately without lockouts.
Breaking Changes
1render_js Requires a Tier 4 Cap
Requests that set advanced.render_js to true with cost_controls.max_tier below "4" are now rejected with 422 at submission, before any charge, on /api/v1/scrape, /api/v1/batch items and /api/v1/crawl. Browser rendering runs on tier 4, so set max_tier to "4", omit it, or use render_js "auto".
Plus 11 internal changes for stability and performance.