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...
Connect OpenClaw to Cloudflare handling, sticky proxies and scheduled extraction. For supported DataDome targets, use the confirmed solver workflow and return validated content.
V1 HTTP API example for opensea.io/category/memberships. Read the API key from CLOUDBYPASS_APIKEY.
: "${CLOUDBYPASS_APIKEY:?Set CLOUDBYPASS_APIKEY first}"
curl --include --request GET --max-time 40 \
"https://api.cloudbypass.com/category/memberships" \
--header "x-cb-apikey: $CLOUDBYPASS_APIKEY" \
--header "x-cb-host: opensea.io" \
--header "x-cb-timeout: 30"
V2 requires x-cb-version: 2 and x-cb-proxy. For Turnstile, also configure x-cb-sitekey and [cf_token] as shown in the guide. Use 2s for streaming; check x-cb-status before parsing.
V1 HTTP API example for opensea.io/category/memberships. Read the API key from CLOUDBYPASS_APIKEY.
import os
import requests
response = requests.get(
"https://api.cloudbypass.com/category/memberships",
headers={
"x-cb-apikey": os.environ["CLOUDBYPASS_APIKEY"],
"x-cb-host": "opensea.io",
"x-cb-timeout": "30",
},
timeout=40,
)
if response.headers.get("x-cb-status") != "ok":
raise RuntimeError(response.text)
print(response.status_code)
print(response.text)
V2 requires x-cb-version: 2 and x-cb-proxy. For Turnstile, also configure x-cb-sitekey and [cf_token] as shown in the guide. Use 2s for streaming; check x-cb-status before parsing.
V1 HTTP API example for opensea.io/category/memberships. Read the API key from CLOUDBYPASS_APIKEY.
package main
import (
"fmt"
"io"
"log"
"net/http"
"os"
"time"
)
func main() {
key := os.Getenv("CLOUDBYPASS_APIKEY")
if key == "" { log.Fatal("Set CLOUDBYPASS_APIKEY first") }
req, err := http.NewRequest("GET",
"https://api.cloudbypass.com/category/memberships", nil)
if err != nil { log.Fatal(err) }
req.Header.Set("x-cb-apikey", key)
req.Header.Set("x-cb-host", "opensea.io")
req.Header.Set("x-cb-timeout", "30")
client := &http.Client{Timeout: 40 * 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" {
log.Fatal(string(body))
}
fmt.Println(res.StatusCode)
fmt.Println(string(body))
}
V2 requires x-cb-version: 2 and x-cb-proxy. For Turnstile, also configure x-cb-sitekey and [cf_token] as shown in the guide. Use 2s for streaming; check x-cb-status before parsing.
V1 HTTP API example for opensea.io/category/memberships. Read the API key from CLOUDBYPASS_APIKEY.
// Node.js 18+; no extra packages required.
async function main() {
const key = process.env.CLOUDBYPASS_APIKEY;
if (!key) throw new Error("Set CLOUDBYPASS_APIKEY first");
const response = await fetch(
"https://api.cloudbypass.com/category/memberships",
{
headers: {
"x-cb-apikey": key,
"x-cb-host": "opensea.io",
"x-cb-timeout": "30",
},
signal: AbortSignal.timeout(40000),
}
);
const body = await response.text();
if (response.headers.get("x-cb-status") !== "ok") {
throw new Error(body);
}
console.log(response.status);
console.log(body);
}
main().catch(error => {
console.error(error.message);
process.exitCode = 1;
});
V2 requires x-cb-version: 2 and x-cb-proxy. For Turnstile, also configure x-cb-sitekey and [cf_token] as shown in the guide. Use 2s for streaming; check x-cb-status before parsing.
V1 HTTP API example for opensea.io/category/memberships. Read the API key from CLOUDBYPASS_APIKEY.
// Java 11+; save as Main.java.
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");
if (key == null || key.isBlank()) {
throw new IllegalStateException("Set CLOUDBYPASS_APIKEY first");
}
HttpClient client = HttpClient.newBuilder()
.connectTimeout(Duration.ofSeconds(10)).build();
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://api.cloudbypass.com/category/memberships"))
.timeout(Duration.ofSeconds(40))
.header("x-cb-apikey", key)
.header("x-cb-host", "opensea.io")
.header("x-cb-timeout", "30")
.GET().build();
HttpResponse<String> response = client.send(
request, HttpResponse.BodyHandlers.ofString());
if (!response.headers().firstValue("x-cb-status").orElse("").equals("ok")) {
throw new IllegalStateException(response.body());
}
System.out.println(response.statusCode());
System.out.println(response.body());
}
}
V2 requires x-cb-version: 2 and x-cb-proxy. For Turnstile, also configure x-cb-sitekey and [cf_token] as shown in the guide. Use 2s for streaming; check x-cb-status before parsing.
Register a Scrapingbypass API account - Sign Up Now
Register a Scrapingbypass Proxy account - Sign Up Now
One registration gives you access to both API and Proxy products. Log in within 30 days and click Trial Activity to claim test credits and proxy traffic.
Enter your target URL in the Code Generator to test whether the target page needs WAF bypass, proxy routing, sticky sessions, or extra headers.
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.
Add the API to your crawler, job queue, or AI automation agent, then validate response status, headers, proxy strategy, and parsing logic before production.
Choose API credits or proxy traffic based on request volume, target protection level, and session duration - View Pricing
To handle Cloudflare's JS Challenge, purchase a credit plan.
For proxy traffic, select a Rotating Datacenter or Rotating Residential proxy plan.
Cloudflare bypass consumes points and may require proxy support. A proxy alone cannot bypass Cloudflare.
Keep access handling outside your parser. Scrapingbypass handles Cloudflare JS Challenge and Turnstile. For supported DataDome targets, follow the CAPTCHA solver integration workflow, preserve session context and validate the returned content.
Auto-solves complex challenges and matches real browser behavior.
Decrypts and formats responses so you get structured data faster.
Customize Referer and headers to fit the target verification flow.
Send business data via JSON payloads or form parameters.
Handle URL query parameters for search, paging, and filtering.
Use external proxy IP and rotating IP pools for geo-matching access.
Scrapingbypass exposes WAF bypass and proxy routing as standard HTTP requests. Add a few headers, keep your existing scraper framework, and avoid maintaining custom challenge solvers, browser farms, and fingerprint patches.
Test with native cURL in one command to verify Cloudflare challenge handling, with minimal setup.
Use requests or aiohttp for HTTP requests and asynchronous collection.
Leverages Go concurrency with fast, type-safe APIs for large-scale scraping workloads.
Fits full-stack apps and automation tools, enabling fast request routing in services or scripts.
Built for enterprise standards, supports multithreaded calls for steady access in complex flows.
Includes full type definitions to improve reliability across modern web scraping pipelines.
Modern WAFs compare far more than IP reputation. Scrapingbypass aligns TLS fingerprints, HTTP/2 behavior, browser headers, and device-like signals so automated requests look consistent across the full session, reducing 403, 429, and challenge-loop failures.
Syncs updates fast and supports protocol-level handling for new bot checks.
Handle Cloudflare JS Challenge and Turnstile in supported workflows.
Mimics traffic source paths for sites with strict origin validation.
Large real-device UA pool for desktop and mobile, with easy switching.
Works with Web Application Firewall (WAF) and CDN protection layers, including Imperva and Akamai.
Protocol-level headless browser simulation with JavaScript rendering efficiency for faster data extraction.
Compared with heavy Selenium/Puppeteer setups, Scrapingbypass API uses a protocol-based request mode with no real browser instance. This keeps server usage low while supporting high concurrency across OS and cloud environments.
Fits Windows workflows for local debugging and fast delivery of small-to-mid data extraction jobs.
Works smoothly on Apple Silicon, making scripting, testing, and iteration faster for developers.
Optimized for mainstream Linux, with Docker deployments and horizontal cluster scaling.
Meets enterprise stability needs and runs long-term in traditional IDC environments.
Supports mobile protocol forwarding for iOS testing and mobile data extraction access.
Fits Android API calls and helps automated access pass cloud firewall checks reliably.
|
|
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. |
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.
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.
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
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.
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.
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.
All Scrapingbypass API plans currently support up to 30 concurrent requests per second.
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 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).
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.
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.
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.
Yes, for supported targets and challenge types. Start with the DataDome integration workflow and send an authorized target URL to support to confirm the mode. Keep the approved session consistent and validate returned content before parsing. Cloudflare and DataDome use different verification flows; support is confirmed per target. See the DataDome workflow.
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.
Scrapingbypass Proxy supports multiple payment methods, including Alipay, USDT, and other supported options depending on your region.
For Scrapingbypass Rotating Proxies, traffic usage is calculated based on the total volume of uploaded and downloaded data through the proxy connection.
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 .
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.
Scrapingbypass Proxy currently supports both HTTP and SOCKS5 proxy protocols, ensuring compatibility with most scraping tools, browsers, and automation frameworks.
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.
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.
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 API Points Usage Concise Rules: 1 point per successful request, V2 version consumes 3 points. Points expire monthly and reset; recharge is separate. V2 supports JS polling, requires time-limited Proxy purchase. Max concurrent requests: 20/s. 403 or Access Denied may require Proxy configuration. Not compatible with selenium or Puppeteer; can be used with Anti-Detection Browsers and collectors.
View MoreScrapingbypass global Proxy is billed by data package, never expires. Supports payment methods such as Alipay, USDT. Data package usage includes upload + download data. Provides dynamic residential and Data Center Proxys, supports http and Socks5 proxy protocols. Free trial available after registration. Chinese users need to use it in Global environments as direct connection to mainland China IP is not supported.
View MoreBypass Cloudflare effortlessly with Scrapingbypass API for unhindered web data collection. It offers HTTP API and global Rotating Proxy services, supporting customizable browser fingerprints like Referer and UA for enhanced control. Scrapingbypass IP service settings cover FAQs, IP extraction tutorials, Anti-Detection Browsers, computer browsers, and mobile platforms. Detailed guides include configurations for various browsers and platforms.
View MoreWhen change alerts for FamilyTreeNow evidence retention suddenly increase, do not assume the site changed. Check retriev...
When change alerts for FamilyTreeNow opt-out monitoring suddenly increase, do not assume the site changed. Check retriev...
The choice between browser automation and an API access layer for FamilyTreeNow field-change alerts should follow the in...
Evidence fields for FamilyTreeNow public-record quality should first prove that the response is still the intended page,...
A useful monitoring workflow for FamilyTreeNow availability monitoring starts with page scope, acceptance criteria, and ...
Bottom line: Direct fetch is enough for stable low-risk pages. Scrapingbypass API becomes more useful when monitoring jo...