Hybrid unlock for Cloudflare, DataDome, Akamai, and peers on allowlisted domains
Website WebUnlocker
When Crawler and Rendering still hit a wall, BrowserSolver WebUnlocker runs a hybrid session on approved domains. Clear challenges, return parseable HTML, and keep billing predictable with failed-retry rules documented in the API.
- Allowlisted domains only: confirm coverage before production
- Playbooks for Cloudflare, DataDome, Akamai, PerimeterX, Kasada, Imperva, Fastly
- Same redirect and raw-source controls as Website Crawler
- Failed unlock attempts after exhaustion are not billed
3×
unlock lane
Hybrid
render + fetch
Allowlist
required
0
bill on exhaust
Unlock only when cheaper modes fail
- Step 1
Detect
Run Website AntiBot to name the vendor and challenge family.
- Step 2
Confirm allowlist
Check domain support or contact support before scaling.
- Step 3
Unlock
Call WebUnlocker once per URL and parse the returned HTML.
When cheap HTTP and render are not enough
Retailer and marketplace scrapes often hit vendor stacks after a clean Crawler or Rendering call fails. WebUnlocker is a separate mode on the same balance, one URL per call, allowlisted domains only, hybrid engine when WAF layers block extraction.
- Confirm the domain is supported before production traffic, or contact support if it is not enabled yet
- Maintained playbooks for Cloudflare, DataDome, Akamai, PerimeterX, Kasada, and peers
- Failed retries after exhaustion are not billed
- Same API key and credit balance across BrowserSolver scrape modes
Unlocked HTML back into your parser
After challenges clear, page bodies land in the same shape as Website Crawler, no second integration path for protected extracts.
- Pass-rate visibility per allowlisted domain in the dashboard
- Run Website AntiBot first when you are unsure which layer is blocking
- Escalate from 1× Crawler or 2× Rendering only on URLs that still fail after probe
- Same API key and credit balance across BrowserSolver scrape modes
When Crawler and Rendering hit a wall
One URL per call on approved domains, after AntiBot tells you unlock is the right mode.
Allowlist
Production unlocks on approved domains.
Hybrid engine
JS rendering plus fetch-mode fallback.
Redirect control
Inspect or follow chains after unlock.
Clean HTML out
Unlocked page bodies ready for your parsers.
Session rotate
Fresh identity when blocks repeat.
Hybrid unlock
Built for vendor-hardened allowlisted domains.
Hybrid
Render plus fetch-mode fallback in one call
Allowlist
Production unlocks on approved hosts
Vendors
Cloudflare to Kasada playbooks maintained
Fair billing
Exhausted unlock retries are not billed
WAF unlock guides
Runbooks for clearing common WAF and bot vendors with BrowserSolver.
Frequently asked questions
Credits, scrape types, and billing before your first production job.
Which domains support WebUnlocker?
Unlock runs on supported domains only. Confirm coverage in docs or with support before pointing production scrapers at a new host.
How is WebUnlocker different from Rendering?
Rendering executes JavaScript on pages you can already reach. WebUnlocker adds vendor bypass for hardened allowlisted domains.
Should I unlock every URL?
No. Start with Crawler or Rendering. Use AntiBot when unsure, then unlock only the URLs that still fail.
Where are vendor guides?
See /bypass/cloudflare and the other vendor pages under /bypass for Cloudflare, DataDome, Akamai, and peers.
Pick your next move
Wire up an integration, review plans, or read the API reference before your first job.
Integrations
Trigger BrowserSolver from n8n, Zapier, Make, or any stack that speaks HTTP.
Scrape your first blocked URL
Fetch, render, screenshot, or unlock from one dashboard. Proxies, browsers, and anti-bot lanes stay on our side.
- 500 signup credits
- No card to start
- All scraping modes