Official SDK and HTTP API
Official SDKs are available for Python, Node.js, and Go. Applications in other languages can call the HTTP API directly and handle response status and error details in their own request layer.
Cloudflare access verification solution
Cloudbypass API
Turn complex web page access verification into clear and controllable API requests
For developers, data teams, and automation projects, it handles access verification such as Cloudflare JS challenges and Turnstile through the HTTPS interface. You can call the HTTP API directly, or use the official SDK or local proxy tools to access it.
Please only use it for authorized web access, automated testing and data processing tasks.Check out the official Quickstart
Supports Cloudbypass API V1, V2 and V2s
Access verification processingJS query and Turnstile
HTTPS APISupports all HTTP methods
V1 / V2 / V2sSelect by verification scenario
Official SDKPython、Node.js、Go
Product positioning
What problems can Cloudbypass API solve?
When a standard HTTP request encounters a Cloudflare JS challenge or Turnstile check, Cloudbypass API sends the target request through one HTTPS endpoint. The official SDKs and local proxy tool simplify integration while using the same underlying HTTP API.
- Suitable for authorized data collection, page monitoring and automated testing
- The required request headers are x-cb-apikey and x-cb-host
- x-cb-status and error JSON should be checked when handling responses
cURL request example
curl --include --request GET \
--url "https://api.cloudbypass.com/user/login.html" \
--header "x-cb-apikey: <APIKEY>" \
--header "x-cb-host: example.io"
# Original target URL: https://example.io/user/login.html
# x-cb-protocol defaults to https
core competencies
Designed around real development processes
Cloudbypass API provides a consistent workflow for testing target pages, configuring request parameters, and moving into production.
All access is ultimately forwarded to the HTTP API
Direct requests must include x-cb-apikey and x-cb-host. The SDKs and local proxy tool simplify request construction while routing calls through the same Cloudbypass HTTP API.
Cloudbypass API V1
It is suitable for scenarios where the browser can access and the program request returns 403. V1 does not need to set x-cb-version, it has a dynamic proxy by default, and each request is stateless.
Cloudbypass API V2
Request header setting x-cb-version: 2. V2 must provide fixed or time-sensitive x-cb-proxy; sessions can be managed in cookie mode or x-cb-part, and Turnstile can configure x-cb-sitekey.
Cloudbypass API V2s
V2s provides the same core capabilities as V2 with streaming responses for large downloads or incremental processing. Set the x-cb-version request header to 2s.
Integration Flow
Start using Cloudbypass API in three steps
Get APIKEY from the console, test accessibility first, then select V1, V2, or V2s by verification type.
Step 01
Register and get access credentials
Register an account and log in to the console to obtain the access credentials required for the project.
Register for Cloudbypass API
Step 02
Test using code generator
Test authorized target URLs and confirm x-cb-host, version, and proxy configuration.
Open the code generator
Step 03
Integrate and monitor results
Connect to the existing task and confirm that x-cb-status is ok; if it fails, read the id, code and message in the error JSON.
View Cloudbypass API documentation
Use Cases
Serving projects that require stable web page access
Use Cloudbypass API only for authorized workflows that comply with the target website's terms, with clear request handling and auditable results.
Web data collection
Obtain public page content for structured organization, research and business analysis.
Price and page monitoring
Regularly check for public changes to merchandise, inventory, announcements, or key pages.
Automated quality inspection
Verify page availability and return results in different network environments.
AI data workflow
Provide web content to authorized search, summarization, and AI agent workflows.
Points package
Cloudbypass API package price
Choose a points package based on monthly request size and concurrency needs. The prices below are consistent with Cloudbypass's current plans.
No points will be deducted for failed requests; 1 point will be consumed for a successful request, and 3 points will be consumed for a successful request for Cloudbypass API V2. Currently showing1 month package.
Basic package
$49/month
80,000 API credits
- Validity period:30 days
- Concurrent threads: 20 times/second
Standard package
$79/month
300,000 API credits
- Validity period:30 days
- Concurrent threads: 20 times/second
Premium package
$129/month
1,000,000 API credits
- Validity period:30 days
- Concurrent threads: 25 times/second
Professional package
$259/month
2,200,000 API credits
- Validity period:30 days
- Concurrent threads: 25 times/second
Premium package
$489/month
4,600,000 API credits
- Validity period:30 days
- Concurrent threads: 30 times/second
Supreme package
$1056/month
12,000,000 API credits
- Validity period:30 days
- Concurrent threads: 30 times/second
FAQ
Learn about Cloudbypass API
View frequently asked questions such as product positioning, version selection, access methods, and response status.
It is recommended to read Quickstart before accessing for the first time and start testing with small-scale requests.
Cloudbypass API is a web access interface based on HTTPS. Python, Node.js, Go SDK and local proxy tools will eventually forward the request to Cloudbypass HTTP API.
It is suitable for authorized data collection, price monitoring, content aggregation, quality inspection, automated testing and other projects that require stable access to public web page content. Use is subject to the target site's terms and applicable laws.
What is the difference between the HTTP API, SDKs, and the local proxy tool?
HTTP API is the actual request entrance; the official SDK encapsulates common calls and error handling; the local proxy tool forwards the original proxy request to the HTTP API, which is suitable for Java, collectors and complex session requests.
Official documentation provides Python, Node.js, and Go SDKs. Other languages capable of sending HTTPS requests can call the HTTP API directly and handle response status and errors themselves.
You can test V1 first when the browser is accessible but the program request returns 403; use V2 when encountering JS challenges or Turnstile, and provide a fixed or time-sensitive proxy; use V2s when streaming downloads or processing while receiving are required.
The response header x-cb-status is ok, indicating that the processing is successful. When it fails, the HTTP API returns JSON error information, which includes the request id, error code and message; when using the SDK, the response error is automatically handled and an exception is thrown.
Start using Cloudbypass API
First test the target page in the console, and then choose the access method suitable for the project.
