FamilyTreeNow privacy-aware retrieval: Public Records, Privacy, and Opt-Out Boundaries
When change alerts for FamilyTreeNow privacy-aware retrieval suddenly increase, do not assume the site changed. Check re...
Web access APIs for Cloudflare and DataDome
Challenge handling: Process Cloudflare JS Challenge, Turnstile, supported DataDome slider and puzzle CAPTCHA, and Imperva / Incapsula verification workflows.
Proxy routing: Use rotating residential or datacenter proxies, HTTP/SOCKS5, or your own provider. Match regions and keep IPs and sessions consistent.
Request configuration: Configure TLS fingerprints, User-Agent and request headers to match your session and target requirements.
Developer integration: Use cURL, Python, Go, Node.js or Java request examples with your existing scraper.
Response handling: Retrieve HTML or JSON through protocol-level requests, then check response status and content before passing results to your parser.
Rotating Residential & Datacenter Proxies
Route requests through rotating residential, datacenter or custom proxies. Match the region and keep IPs consistent for Cloudflare and DataDome sessions. Proxy routing and CAPTCHA solving are separate functions.
OpenClaw x Scrapingbypass API Automation
Connect OpenClaw to verification APIs, proxy routing and scheduled extraction. Use the supported Cloudflare or DataDome integration workflow, then pass validated responses to your automation tasks.
HTTP API examples
V2 Part mode for Cloudflare JS Challenge and DataDome challenges.
#!/usr/bin/env bash
set -euo pipefail
: "${CLOUDBYPASS_APIKEY:?Set CLOUDBYPASS_APIKEY first}"
: "${CLOUDBYPASS_PROXY:?Set CLOUDBYPASS_PROXY first}"
headers=$(mktemp)
body=$(mktemp)
trap 'rm -f "$headers" "$body"' EXIT
curl --fail-with-body --silent --show-error --max-time 130 \
--dump-header "$headers" --output "$body" \
"https://api.cloudbypass.com/your/path" \
--header "x-cb-apikey: $CLOUDBYPASS_APIKEY" \
--header "x-cb-host: example.com" \
--header "x-cb-version: 2" \
--header "x-cb-proxy: $CLOUDBYPASS_PROXY" \
--header "x-cb-part: 0" \
--header "x-cb-timeout: 120"
if ! grep -iq '^x-cb-status: *ok[[:space:]]*$' "$headers"; then
cat "$body" >&2
exit 1
fi
cat "$body"import os
import requests
key = os.environ["CLOUDBYPASS_APIKEY"]
proxy = os.environ["CLOUDBYPASS_PROXY"]
if not key or not proxy:
raise ValueError("Set API key and proxy first")
headers = {
"x-cb-apikey": key,
"x-cb-host": "example.com",
"x-cb-version": "2",
"x-cb-proxy": proxy,
"x-cb-part": "0",
"x-cb-timeout": "120",
}
response = requests.get(
"https://api.cloudbypass.com/your/path",
headers=headers,
timeout=(10, 130),
)
if response.headers.get("x-cb-status") != "ok":
raise RuntimeError(response.text)
response.raise_for_status()
print(response.text)package main
import (
"fmt"
"io"
"log"
"net/http"
"os"
"time"
)
func main() {
key, proxy := os.Getenv("CLOUDBYPASS_APIKEY"), os.Getenv("CLOUDBYPASS_PROXY")
if key == "" || proxy == "" { log.Fatal("Set API key and proxy first") }
req, err := http.NewRequest("GET",
"https://api.cloudbypass.com/your/path", nil)
if err != nil { log.Fatal(err) }
req.Header.Set("x-cb-apikey", key)
req.Header.Set("x-cb-host", "example.com")
req.Header.Set("x-cb-version", "2")
req.Header.Set("x-cb-proxy", proxy)
req.Header.Set("x-cb-part", "0")
req.Header.Set("x-cb-timeout", "120")
client := &http.Client{Timeout: 130 * time.Second}
res, err := client.Do(req)
if err != nil { log.Fatal(err) }
defer res.Body.Close()
body, err := io.ReadAll(res.Body)
if err != nil { log.Fatal(err) }
if res.Header.Get("x-cb-status") != "ok" || res.StatusCode >= 400 {
log.Fatal(string(body))
}
fmt.Println(string(body))
}async function main() {
const key = process.env.CLOUDBYPASS_APIKEY;
const proxy = process.env.CLOUDBYPASS_PROXY;
if (!key || !proxy) throw new Error("Set API key and proxy first");
const response = await fetch(
"https://api.cloudbypass.com/your/path",
{
headers: {
"x-cb-apikey": key,
"x-cb-host": "example.com",
"x-cb-version": "2",
"x-cb-proxy": proxy,
"x-cb-part": "0",
"x-cb-timeout": "120",
},
signal: AbortSignal.timeout(130000),
}
);
const body = await response.text();
if (response.headers.get("x-cb-status") !== "ok" || !response.ok) {
throw new Error(body);
}
console.log(body);
}
main().catch(error => {
console.error(error.message);
process.exitCode = 1;
});import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
import java.time.Duration;
public class Main {
public static void main(String[] args) throws Exception {
String key = System.getenv("CLOUDBYPASS_APIKEY");
String proxy = System.getenv("CLOUDBYPASS_PROXY");
if (key == null || key.isBlank() || proxy == null || proxy.isBlank()) {
throw new IllegalStateException("Set API key and proxy first");
}
HttpClient client = HttpClient.newBuilder()
.connectTimeout(Duration.ofSeconds(10)).build();
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://api.cloudbypass.com/your/path"))
.timeout(Duration.ofSeconds(130))
.header("x-cb-apikey", key)
.header("x-cb-host", "example.com")
.header("x-cb-version", "2")
.header("x-cb-proxy", proxy)
.header("x-cb-part", "0")
.header("x-cb-timeout", "120")
.GET().build();
HttpResponse<String> response = client.send(
request, HttpResponse.BodyHandlers.ofString());
if (!response.headers().firstValue("x-cb-status").orElse("").equals("ok")
|| response.statusCode() >= 400) {
throw new IllegalStateException(response.body());
}
System.out.println(response.body());
}
}V1 includes rotating proxies. V2 requires a fixed or sticky proxy. V2s uses x-cb-version: 2s for streaming responses.
For Turnstile, set x-cb-sitekey and place [cf_token] where the target request expects the token.
Keep the same proxy within a session partition. Use a different x-cb-part (0–999) for each concurrent worker.
Start Scrapingbypass in Four Practical Steps
1.Create Your Account
Register a Scrapingbypass API account - Sign Up Now
Register a Scrapingbypass Proxy account - Sign Up Now
One account gives you API and proxy access. Log in within 30 days and open Trial Activity from the gift icon to claim trial credits and traffic.
2.Test with the Code Generator
Use the Code Generator to test Cloudflare requests. For DataDome slider or puzzle CAPTCHA, follow the DataDome CAPTCHA solver API integration workflow and keep the target request, proxy IP and session parameters consistent.
V1 includes a rotating proxy. V2 requires a stable proxy IP; configure a sticky session of at least 10 minutes when using Scrapingbypass rotating proxies.
For assistance, see the API documentation or contact Scrapingbypass Support.
3.Integrate the Scrapingbypass API
Integrate the configured Cloudflare or DataDome workflow into your existing application. Check response status, content and session context before continuing with pagination, parsing or automation.
4.Select a Pricing Plan
Choose a plan based on your usage - View Pricing
Use the relevant API credit plan for Cloudflare requests. For DataDome CAPTCHA handling, follow the support and billing information for the DataDome CAPTCHA solver API.
For proxy traffic, select a Rotating Datacenter or Rotating Residential proxy plan.
Cloudflare and DataDome verification may require proxy routing. API credits and proxy traffic are billed separately; changing an IP alone does not solve a CAPTCHA.
A web scraping API for Cloudflare and DataDome workflows
Keep verification handling separate from your parser. Scrapingbypass handles Cloudflare JS Challenge, Turnstile and supported DataDome slider or puzzle CAPTCHA. Integrate the relevant workflow, then extract business data from the returned content.
-
Cloudflare and DataDome challenge handling
Distinguish JS Challenge, Turnstile and DataDome slider or puzzle CAPTCHA. Use the corresponding workflow and preserve its session context.
-
HTML / JSON response validation
Check the status and content for block or CAPTCHA pages before passing the response to your parser. Retrieving HTML is not the same as extracting structured business data.
-
Configurable headers
Customize Referer and headers to fit the target verification flow.
-
Custom request body
Send business data via JSON payloads or form parameters.
-
Query parameters support
Handle URL query parameters for search, paging, and filtering.
-
HTTP/SOCKS5 proxy support
Use external proxy IP and rotating IP pools for geo-matching access.
Integrate with Python, Go, Node.js, Java or cURL
Use standard HTTP requests for the relevant Cloudflare or DataDome API workflow without replacing your scraper framework. Configure parameters and response checks for each integration rather than repeating verification logic in your business code.
-
cURL CLI Call
Test with native cURL in one command to verify Cloudflare challenge handling, with minimal setup.
-
Python SDK (Official)
Use requests or aiohttp for HTTP requests and asynchronous collection.
-
Go SDK (High-Throughput)
Leverages Go concurrency with fast, type-safe APIs for large-scale scraping workloads.
-
Node.js SDK
Fits full-stack apps and automation tools, enabling fast request routing in services or scripts.
-
Java API Integration
Built for enterprise standards, supports multithreaded calls for steady access in complex flows.
-
TypeScript Support
Includes full type definitions to improve reliability across modern web scraping pipelines.
Consistent fingerprints, IPs and sessions for Cloudflare and DataDome
Keep TLS fingerprints, User-Agent, request headers, cookies and proxy IPs consistent throughout verification. When investigating a DataDome CAPTCHA loop, 403 or 429 response, check the target response, routing and session parameters together.
-
Match anti-automation protection
Syncs updates fast and supports protocol-level handling for new bot checks.
-
Full Cloudflare verification flow
Handle Cloudflare JS Challenge and Turnstile in supported workflows.
-
Configurable Referer params
Mimics traffic source paths for sites with strict origin validation.
-
Configurable User-Agent
Large real-device UA pool for desktop and mobile, with easy switching.
-
WAF / edge security ready
Works with Web Application Firewall (WAF) and CDN protection layers, including Imperva and Akamai.
-
Supports headless browser mode
Protocol-level headless browser simulation with JavaScript rendering efficiency for faster data extraction.
HTTP API access across platforms
Use HTTP requests from Windows, macOS, Linux or cloud services to integrate supported Cloudflare and DataDome verification workflows. The access layer retrieves HTML or JSON; your application remains responsible for parsing, retries and task scheduling.
-
Windows Deployment Support
Fits Windows workflows for local debugging and fast delivery of small-to-mid data extraction jobs.
-
macOS Dev & Production Ready
Works smoothly on Apple Silicon, making scripting, testing, and iteration faster for developers.
-
Linux Servers (Recommended)
Optimized for mainstream Linux, with Docker deployments and horizontal cluster scaling.
-
Enterprise CentOS Support
Meets enterprise stability needs and runs long-term in traditional IDC environments.
-
iOS Mobile Request Routing
Supports mobile protocol forwarding for iOS testing and mobile data extraction access.
-
Android Proxy-Based Access
Fits Android API calls and helps automated access pass cloud firewall checks reliably.
Web access for Cloudflare and DataDome workflows
Use Cases
Data collection with Cloudflare and DataDome verification
For permitted retail, inventory and ticketing data collection, combine supported DataDome CAPTCHA handling with the appropriate proxy route. Keep the region, session and request parameters consistent before pagination and parsing.
|
|
Monitor product listings, prices, stock, promotions and reviews across permitted retail sources. |
|
|
Track permitted ad creatives, landing-page changes and campaign signals for market research. |
|
|
Monitor permitted public posts, engagement and sentiment for social listening and trend analysis. |
|
|
Organize permitted media metadata and licensed assets into searchable reference libraries. |
|
|
Collect permitted publication updates, topic pages and release information for research and monitoring. |
|
|
Collect permitted market prices, historical records and timestamps for research, alerts and analytics. |
|
|
Monitor job listings, hiring demand, skills and salary ranges across permitted sources. |
|
|
Track permitted property listings, local businesses and pricing changes for regional market research. |
|
|
Monitor permitted fares, availability and policy updates with dates, currency and region preserved. |
|
|
Track permitted offers, discount changes and expiry dates for campaign comparisons. |
|
|
Monitor permitted schedules, container events and freight rates with shipment IDs and timestamps. |
|
|
Collect permitted public risk indicators and source evidence for review, scoring and alerts. |
Scrapingbypass Product FAQ
Find answers to common usage questions or contact our technical support team for assistance.
How are Scrapingbypass API credits consumed?
Each successful API request consumes credits, while failed requests do not deduct any credits.
V1: Each successful request consumes 1 credit.
V2: Each successful request consumes 3 credits. One credit is used for the API request itself, and two additional credits are consumed during JavaScript polling.
The session remains valid for 10 minutes. During this period, the same proxy and session parameters can be reused to avoid repeated Cloudflare verification.
This means no additional credits are charged for subsequent requests within the same session window.
Scrapingbypass API credits expire if not used within their validity period.
Each recharge is calculated independently, and credits are consumed on a first-in, first-out basis.
How does the Scrapingbypass API work?
Scrapingbypass operates as a request-forwarding service. You submit an HTTP request to the Scrapingbypass API, and the API executes the request on your behalf. This approach significantly reduces the likelihood of your traffic being identified as automated. The system focuses on preventing Cloudflare challenges from being triggered, allowing direct access to the target URL instead of programmatically interacting with challenge pages.
How do I use the Scrapingbypass API? Are code examples available?
The Scrapingbypass API is designed to be simple and developer-friendly.
You only need to submit the HTTP request intended for the target website, and Scrapingbypass will forward it exactly as provided.
You can use the online code generator to generate request examples in cURL, JavaScript, TypeScript, Java, Python, and more.
Scrapingbypass API and Proxy integration examples are available here:
View code examples
What is the difference between Scrapingbypass API V1 and V2?
Scrapingbypass V2 supports JavaScript rendering and polling, making it suitable for more advanced Cloudflare challenges.
V2 does not include a default proxy. You must use a Scrapingbypass Proxy with V2.
V1 includes a built-in rotating proxy by default.
What does session partitioning mean in Scrapingbypass API V2?
Session partitions are used to manage Cloudflare cookies and verified sessions.
Once a session is successfully verified, the proxy IP, browser fingerprint, and related parameters must remain unchanged for 10 minutes.
This prevents additional Cloudflare challenges from being triggered during the session.
Session partition values range from 0 to 999, allowing up to 1,000 concurrent session partitions per account.
After a successful request, the proxy IP is locked to the session partition.
Changing the partition value allows you to switch proxies.
Each successful request refreshes the 10-minute session duration.
How do I choose between Scrapingbypass V1 and V2?
Start by testing your target URL using the
code generator with Scrapingbypass V1.
If V1 fails, switch to Scrapingbypass V2 and configure your own proxy IP.
A test proxy is available in the backend for validation.
It is recommended to set the proxy extraction duration to more than 10 minutes.
What is the maximum concurrency supported by the Scrapingbypass API?
All Scrapingbypass API plans currently support up to 30 concurrent requests per second.
Error code: "INSUFFICIENT_BALANCE"
This error indicates that your Scrapingbypass API account has no remaining credits.
You can purchase credits in the Scrapingbypass API console:
Scrapingbypass API Console,
or contact customer support to request test credits.
Error code: "CHALLENGE_LOCK_OCCUPIED"
Error description:
This error occurs when the current session partition is already processing a Cloudflare challenge.
Common causes:
The same session partition is used concurrently by multiple threads.
Multiple users are operating on the same account and partition.
A previous request is still holding the verification lock.
Recommended solutions:
Wait for the lock to be released and retry the request.
Switch to a different session partition (range: 0-99).
Error code: "FORBIDDEN" - V3 Challenge Failed
Recommended actions:
1. Set the proxy IP extraction duration to at least 10 minutes.
2. Switch to proxy IPs from different countries or regions.
Using IPs from the same region repeatedly may increase the risk of restriction.
Why do I encounter 403, 503, or Access Denied errors?
These errors usually indicate that a proxy is required. You can use either API mode or Proxy mode to access Scrapingbypass services. API mode is recommended for domestic users. Currently, only HTTP proxies are supported.
Does Scrapingbypass API support Selenium or Puppeteer?
Browser automation tools such as Selenium and Puppeteer are not supported. Scrapingbypass operates at the HTTP request level and simulates browser requests without launching a real browser.
Can I use a DataDome CAPTCHA solver API with Scrapingbypass?
Yes, for supported targets and challenge types. DataDome and Cloudflare use different verification flows. Follow the DataDome CAPTCHA solver API integration, keep the proxy IP, cookies and session consistent, and validate the returned content. A proxy provides routing; it does not solve CAPTCHA by itself.
Do you offer monthly subscription plans?
Scrapingbypass does not use monthly subscriptions. All Scrapingbypass Proxy services follow a traffic-based pricing model with no expiration. You can purchase traffic packages on demand, and unused bandwidth will never expire.
What payment methods are supported by Scrapingbypass Proxy?
Scrapingbypass Proxy supports multiple payment methods, including Alipay, USDT, and other supported options depending on your region.
How is proxy traffic usage calculated?
For Scrapingbypass Rotating Proxies, traffic usage is calculated based on the total volume of uploaded and downloaded data through the proxy connection.
Why does the detected IP location differ from the selected country?
IP geolocation results may vary depending on the detection database used. Please verify the proxy IP location using the official Scrapingbypass IP check tool: http://ipinfo.cloudbypass.com .
What proxy networks does Scrapingbypass provide?
Scrapingbypass offers two core proxy networks: Rotating Residential Proxies and Rotating Datacenter Proxies. Both proxy types are designed for Cloudflare bypass scenarios and can be managed from a single unified platform.
Which proxy protocols are supported?
Scrapingbypass Proxy currently supports both HTTP and SOCKS5 proxy protocols, ensuring compatibility with most scraping tools, browsers, and automation frameworks.
Do you offer unlimited or unmetered proxy plans?
Scrapingbypass Proxy uses a traffic-based billing model for both rotating residential and datacenter proxies. All traffic packages do not expire. You may request a free trial to evaluate Cloudflare bypass performance before purchasing.
Can users from mainland China use Scrapingbypass Proxy?
Direct connections from mainland China IP addresses are not supported.
To use Scrapingbypass Proxy services, you must deploy a global network environment, such as a server or VPS located in Hong Kong or other overseas regions.
Desktop users may connect via a global network accelerator, while mobile users can access through a router configured with a global network environment.
If you are unable to set up a compatible global network environment, please do not proceed with a purchase.
Refunds are not available for unsupported direct connections.
Trusted by developers and data professionals worldwide
Scrapingbypass API significantly improved our data extraction efficiency, especially for websites protected by Cloudflare. The API is straightforward, easy to integrate, and saved us countless hours dealing with anti-bot restrictions.
Since adopting Scrapingbypass API, bypassing Cloudflare challenges has become effortless. It handles captchas reliably and allows uninterrupted access to the data pipelines we depend on.
Scrapingbypass simplified our web data collection workflow by automatically handling complex Cloudflare verifications. It's fast, stable, and extremely reliable in production environments.
As a market analyst working with large-scale web sources, avoiding 403 errors is critical. Scrapingbypass API ensures consistent access to protected pages and delivers clean, usable data.
Scrapingbypass makes bypassing Cloudflare protection simple. The documentation is clear, the API behavior is predictable, and integration was completed in minutes. Highly recommended for developers.
I was initially skeptical, but Scrapingbypass exceeded expectations. It consistently bypasses Cloudflare human verification and has become a core component of our data infrastructure.
Scrapingbypass Help Center
Cloudflare and DataDome integration guides
Common Issues with Cloudflare Bypass API
Review Cloudflare and DataDome API integration, credit rules and session configuration. Diagnose errors through response status and content rather than mixing parameters or billing assumptions between verification types.
View More
Common Issues with Scrapingbypass Global Proxy
Choose residential or datacenter traffic plans for HTTP, SOCKS5 and session routing. Proxy traffic and API verification serve different purposes and can be combined for the relevant workflow.
View More
Tutorial for Using Scrapingbypass API/Proxy
Explore Cloudflare and DataDome verification guides, code examples and proxy setup, including request headers, TLS, User-Agent and response validation.
View MoreLatest Articles
Cloudflare and DataDome integration guides
FamilyTreeNow evidence retention: Public Records, Privacy, and Opt-Out Boundaries
When change alerts for FamilyTreeNow evidence retention suddenly increase, do not assume the site changed. Check retriev...
FamilyTreeNow opt-out monitoring: Change Alerts Without Noisy Results
When change alerts for FamilyTreeNow opt-out monitoring suddenly increase, do not assume the site changed. Check retriev...
FamilyTreeNow opt-out page testing: Change Alerts Without Noisy Results
When change alerts for FamilyTreeNow opt-out page testing suddenly increase, do not assume the site changed. Check retri...
FamilyTreeNow field-change alerts: Browser Automation or an API Layer
The choice between browser automation and an API access layer for FamilyTreeNow field-change alerts should follow the in...
FamilyTreeNow public-record response schema: Browser Automation or an API Layer
The choice between browser automation and an API access layer for FamilyTreeNow public-record response schema should fol...