Cloudflare Bypass API —
Scrape Protected Sites
Anti-bot protection blocking your scraper? SnapRender's built-in FlareSolverr integration handles Cloudflare, DataDome, and PerimeterX challenges automatically. Just flip a flag.
One flag. Zero config.
You send a request
Add use_flaresolverr: true to any SnapRender API call. Same endpoints, same parameters, same response format.
FlareSolverr solves the challenge
The request is routed through FlareSolverr, which uses a real browser to solve JavaScript challenges, CAPTCHAs, and anti-bot checks.
You get clean data
SnapRender processes the unprotected page and returns your screenshot, PDF, HTML, or markdown — exactly as if Cloudflare wasn't there.
Add one flag.
No proxy lists. No CAPTCHA solvers. No separate FlareSolverr instance to run.
curl -X POST https:#666">//api.snaprender.dev/v1/render \
-H #A8D4A0">"x-api-key: sr_live_YOUR_KEY" \
-H #A8D4A0">"Content-Type: application/json" \
-d #A8D4A0">'{
#A8D4A0">"url": "https://cloudflare-protected-site.com",
#A8D4A0">"format": "html",
#A8D4A0">"use_flaresolverr": true
}'Anti-bot? Handled.
Cloudflare
JavaScript challenges, Turnstile, Under Attack mode, and managed challenge pages. The most common anti-bot protection on the web — solved automatically.
DataDome
DataDome bot detection and CAPTCHA challenges. Common on e-commerce, travel, and ticketing sites.
PerimeterX / HUMAN
PerimeterX (now HUMAN) behavioral challenges. Used by major retailers, financial services, and media sites.
No extra charge for bypass.
Most scraping APIs charge 5-75x more for "premium" or "protected" sites. SnapRender charges the same $0.006/request whether you use Cloudflare bypass or not. 100 free requests/month.
Questions & answers
SnapRender integrates FlareSolverr, which uses a real browser to solve Cloudflare JavaScript challenges. When you set use_flaresolverr: true, the request is routed through FlareSolverr first, then SnapRender processes the page normally.
Cloudflare (all challenge types including JS challenges and Turnstile), DataDome, and PerimeterX/HUMAN. The FlareSolverr engine handles the challenge-solving automatically.
The first request to a Cloudflare-protected domain takes 5-15 seconds to solve the challenge. Subsequent requests to the same domain reuse the session and are much faster — typically under 3 seconds.
Yes. Add use_flaresolverr: true to any endpoint — /screenshot, /pdf, /render, or /extract. The bypass runs first, then your requested operation executes on the unprotected page.
No. Flat pricing. A request with use_flaresolverr: true costs exactly the same as a request without it. No premium tiers, no per-bypass surcharges.