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.
Cloudbypass 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.
Cloudbypass operates as a request-forwarding service. You submit an HTTP request to the Cloudbypass 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 Cloudbypass API is designed to be simple and developer-friendly.
You only need to submit the HTTP request intended for the target website, and Cloudbypass 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.
Cloudbypass API and Proxy integration examples are available here:
View code examples
Cloudbypass 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 Cloudbypass 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 Cloudbypass V1.
If V1 fails, switch to Cloudbypass 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 Cloudbypass API plans currently support up to 30 concurrent requests per second.
This error indicates that your Cloudbypass API account has no remaining credits.
You can purchase credits in the Cloudbypass API console:
Cloudbypass 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–999).
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 Cloudbypass 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. Cloudbypass operates at the HTTP request level and simulates browser requests without launching a real browser.