Skip to main content
Proxies
Web Unblocker
Web Scraper API
Datasets
General updates
AI Studio
Headless Browser

June 19, 2026

Web Scraper API

Video Data API: video quality selection

You can now control the resolution of downloaded videos, from 144p all the way up to 8K, or simply request the best or worst available quality. Set it once with the context: video_quality parameter and get videos at the size that fits your storage and processing needs.

Learn more

June 18, 2026

Web Scraper API

Error codes for Video Data API

Oxylabs Video Data API now returns a specific error code when a video can't be downloaded, identifying the exact cause. Each reason maps to its own code in the job status response, so you can handle failures programmatically instead of parsing a generic error.

Learn more

June 02, 2026

General updates

Top-up flow improvements

You can now top up your traffic balance for Residential Proxies, Mobile Proxies, Datacenter Proxies (per GB), Web Unblocker, and Web Scraper API by any amount within your plan's range, instead of picking from a handful of preset options.
Need exactly 5 GB? Add it in a single step – no more splitting one purchase into several top-ups.

Learn more

May 28, 2026

General updates

Oxylabs Dashboard API

Introducing Oxylabs Dashboard API to programmatically access your product usage statistics for Oxylabs Datacenter Proxies (DC) and Headless Browser (HB). This allows automated reporting and real-time usage monitoring without the need to directly access the Oxylabs dashboard.

Learn more

May 14, 2026

Proxies

HTTP/3 protocol support

You can now connect to Residential Proxies and Mobile Proxies with HTTP/3 protocol, offering faster connections and more reliable automated request management. Access is available through a dedicated SOCKS5 endpoint with UDP support.

Learn more

May 14, 2026

Proxies

Session IP change control

Residential Proxies and Mobile Proxies now support a new sticky session behavior via sessid_oneip. Users can keep the same IP for as long as the original exit node remains available up to the set session duration. If that exit node expires or goes offline before the duration ends, the request returns a 502 error rather than being routed through a new IP.

Learn more