Web Unlocker: One Endpoint, Any Public Page

The Web Unlocker is a "send a URL, get the page" API. No proxy pool to manage, no retry, CAPTCHA or fingerprint logic to maintain: send the target URL to the unlock endpoint and the server picks the right exit, handles anti-bot challenges, retries failures and returns the page HTML. Exits span 200+ countries and regions.

The problem it solves

When scraping protected sites through raw proxies, the engineering lives after the request fails: rotate the IP, solve the CAPTCHA, fix conflicting fingerprints, requeue the timeouts. That logic is scattered across your codebase and hard to measure. The unlocker collapses the whole chain server-side:

How it works

The unlock endpoint is a plain HTTPS API. Pass the target URL as the request target and authenticate exactly like the proxy products (username/password):

# Example: fetch a page through the unlock endpoint
import requests

proxy = "http://username:password@unlock-host:port"
r = requests.get(
    "https://target-site/any-page",
    proxies={"http": proxy, "https": proxy},
    timeout=30,
)
print(r.status_code)          # 200 = unlocked
print(r.text[:200])           # target page HTML

Your code only cares about two things: send the URL, parse the HTML. IP selection, sessions and retries all happen server-side.

Typical use cases

How it fits the IPLight lineup

If your team already runs stable scraping code and just needs clean exits, dynamic residential proxies (from $1/GB) plus your own retries may fit better. If you want the anti-bot chain off your plate — or the target is strict enough that DIY cost blows up — the unlocker is the lower total-cost route. Both share one account and console, so you can switch anytime.

FAQ