Web Unblocker

Web Unblocker is the Scraping API with a proxy interface in front of it.

You point an existing HTTP client at a host and port, the way you would with any proxy. Behind that port we terminate the connection, run the request through the same engine the Scraping API uses (proxy selection, browser rendering, ban handling, retries), and hand the finished page back down your connection.

Why it exists

Some tools cannot be rewritten to call an API. A browser automation suite, a vendor product, a scraper somebody wrote years ago. All of them know how to use a proxy and nothing else.

Web Unblocker meets them where they are. No code changes, no new client library. Change the proxy setting and the unblocking happens underneath.

How it works

Because it wraps an API call in a proxy connection, we terminate TLS between your client and the target. That is what lets us handle the request rather than just forwarding packets. A plain proxy cannot inspect or retry an encrypted request it is only relaying.

The practical consequence: it is not a transparent proxy. You are not getting an exit IP you selected; you are getting a finished page.

What it is not

• Not a residential proxy. You cannot pick the exit IP, and there is no targeting beyond country.
• Not for non-HTTP traffic. There is nothing to unblock in a raw TCP stream.
• Not billed by the gigabyte. It draws from the same per-scrape balance as the Scraping API.

If you want to choose the exit IP yourself, you want Residential Proxies instead.

Checking your usage

Web Unblocker consumption is readable through the Bandwidth API under the web-unblocker product, alongside the proxy products.

Next

Making requests →