Cloudbypass API FAQ

To solve your usage problems, you can view common answers here or contact customer service

How is the consumption of package points calculated?

A successful API request consumes 1 point, and a failed request does not consume points.
V1 version Each successful request consumes 1 point;
V2 version One successful request consumes 3 points (one API request consumes 1 point, V2 will consume 2 more points through JS polling, and the session duration is 10 minutes, the session state can be maintained without changing the proxy and part parameters, and unnecessary verification is avoided. That is to say, there is no additional charge for continuing requests within 10 minutes after the first request.)

CloudbypassAPI points will be cleared if they are not used up within the validity period;
Recharges are calculated independently and have nothing to do with previous purchases, but the earliest purchased points will be consumed first.

CloudbypassAPI itself is very simple. You only need to send us the http request body sent to the target website, and we will forward 100% to x-cb-host.
You can use code generator to generate code snippets online for cURL and JavaScript , TypeScript, Java, Python and other commands make HTTP requests.
CloudbypassAPI and Cloudbypass proxy IP code example:

The V2 version can pass js polling (can render JS);
Currently the V2 version does not have a default proxy, you need to purchase the Cloudbypass proxy IP, the V1 version comes with a dynamic proxy

Currently, the maximum number of concurrent requests for all our packages is 20 times/s.

In this case, it is most likely that you need to configure a proxy IP. Choose one of API mode and proxy mode to use our services. Domestic users recommend using API mode. Currently, only proxy IPs of the http protocol are supported.

The service mode provided by CloudbypassAPI is that you submit an http request, and the API sends the request for you. This process makes it more difficult to identify your http request as a robot, and will only bypass the Cloudflare verification code as much as possible and let the Cloudflare verification code If it does not appear, you will directly access the target URL instead of automatically clicking on the Cloudflare verification code.

Currently selenium or Puppeteer is not supported because it does not use a browser and only simulates browser requests, but you can use it in conjunction with a fingerprint browser.