Flexible Billing and Enhanced Session Privacy
This release delivers enhanced self-service options to the billing portal, allowing seamless updates to corporate tax and address details. We have also introduced rigorous improvements to session privacy and request screening, guaranteeing safer data transmission and stricter isolation of third-party cookies.
You can now maintain a consistent residential IP and share cookies across sequential requests using a session handle. This simplifies multi-step tasks like logging in and then scraping data.
You can now update your company billing address and tax ID directly from the self-serve billing portal. This ensures that automatically generated invoices reflect the correct corporate details without needing manual support.
Cross-origin cookies from third-party iframes are now strictly filtered and isolated from your session's cookie jar. This prevents unauthorized third-party cookies from being replayed to your primary target domains on subsequent requests.
New Features
2Stateful scraping sessions
You can now maintain a consistent residential IP and share cookies across sequential requests using a session handle. This simplifies multi-step tasks like logging in and then scraping data.
Self-Serve Billing Details
You can now update your company billing address and tax ID directly from the self-serve billing portal. This ensures that automatically generated invoices reflect the correct corporate details without needing manual support.
Improvements
5Universal session IP pinning
Stateful session IP pinning is now supported across all scraping tiers, including direct HTTP requests. Sequential calls to simple and complex pages alike will now share the exact same residential IP.
Accurate credit pre-billing
Credit pre-estimations for browser-tier tasks are now calculated accurately at submission. This prevents temporary over-billing and ensures your playground balance matches the final processed tier pricing.
SDK-side session validation
The Node SDK now includes client-side validation for stateful session handles and lifetimes to match the Python SDK. This provides immediate feedback on invalid inputs before sending requests to the API.
General bug fixes and improvements
Plus 22 internal improvements for better reliability and performance.
Compact Billing Layout
The billing dashboard layout has been optimized to reduce empty vertical space and group active details more compactly. Active payment methods, recharges, and receipt tables are now positioned for easier scannability.
Bug Fixes
9Stateful session race fix
Resolved a concurrency race condition in stateful sessions that could cause captured cookies to be dropped when scraping in parallel. Your shared cookie jar remains accurate during concurrent actions.
Browser cookie capture
Captured browser cookies are now correctly recorded and available in your stateful sessions. This enables seamless, stateful transitions between standard HTTP scraping and browser-driven actions.
Validation for JS features
Requesting browser-only features without enabling JavaScript rendering now returns a clear validation error. This prevents silent execution failures on incompatible non-JS tiers.
Stateful routing leak fix
Fixed a routing leak in fast-fetch discovery calls during stateful sessions to guarantee that all traffic stays pinned. All sub-requests now strictly maintain your designated residential exit IP.
Lost session detection
Stateful sessions now return a clear indicator when a session has expired or dropped rather than failing silently. This allows you to easily detect lost states and re-initialize sessions.
Complex HTML parsing
Fixed a parsing crash when converting complex, deeply nested HTML structures into clean markdown or JSON. This prevents unexpected validation errors when scraping highly structured pages.
Dashboard playground stability
Fixed a dashboard issue where balance refresh errors could cause unhandled promise rejections. This stabilizes the developer playground interface during balance updates.
Session Cookie Protection
We resolved a session-saving bug where fully invalid or malicious cookie harvests could accidentally overwrite and erase your existing valid cookie jars. Your active, functional session credentials will now be safely preserved.
Mislabeled Session Metadata
We corrected a response metadata issue where request logs mislabeled session status as active for standard sticky sessions. Your API response logs now accurately reflect the exact proxy configuration utilized.
Security
7Domain-scoped session cookies
Stateful session cookies are now securely scoped to their specific domains. Reusing a single session handle across different host domains will no longer leak or replay cookies between them.
Session payload sanitization
Captured session cookies are now sanitized to strip control characters and limit payload sizes. This protects stateful operations and prevents unexpected errors during session replay.
Strict Session Isolation
Cross-origin cookies from third-party iframes are now strictly filtered and isolated from your session's cookie jar. This prevents unauthorized third-party cookies from being replayed to your primary target domains on subsequent requests.
Fail-Safe Cookie Scoping
If a target URL fails to parse during request scoping, the connection now fails closed by default rather than exposing unfiltered cookies. This ensures zero risk of cross-origin leakage during complex navigation paths.
Control Character Protection
Our request screening now rejects non-standard C1 control characters and Unicode line separators in session inputs. This defense-in-depth update blocks sophisticated injection techniques that exploit lenient parser behaviors.
Secure Cookie Sanitization
Response cookies and active session updates are now subjected to rigorous sanitization before ingestion. This closes sanitization gaps and prevents malformed cookies from destabilizing your session jars.
Enhanced Token Redaction
To protect sensitive active data, session-specific proxy tokens are now completely redacted from all system logs. This guarantees your active credentials remain private during execution.
Plus 44 internal changes for stability and performance.