Scrapingbypass API FAQ

Cloudflare and DataDome share one API credit balance, consumption rules and pricing. Choose a plan based on your usage; proxy traffic is billed separately.

V1 and V2(s) consume 1 API credit for each successful request.

When V2(s) successfully completes a verification challenge, it consumes 2 additional credits. This covers supported Cloudflare JS Challenge, Cloudflare Turnstile, DataDome and Incapsula challenges.

An unsuccessful request does not consume the base request credit. However, the 2 challenge credits are deducted as soon as verification succeeds and are not refunded if the subsequent response fails.

Reusing a valid session can reduce repeated challenges, but each successful request still consumes 1 credit. Subsequent requests within the session are not free.

Use credits before the plan expires. Packages retain separate expiry dates, and credits expiring soonest are used first.

Use standard HTTP requests and the same integration logic and request code for Cloudflare and DataDome, without replacing your scraper framework. Keep the proxy IP, cookies and session consistent and validate response status and content. Support for a specific target still depends on the site and challenge type. Test compatibility first; a shared plan does not guarantee access to every target.

Cloudflare and DataDome share the same API integration logic and request code.

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(s) supports JavaScript rendering and polling, making it suitable for more advanced Cloudflare challenges.
V2(s) does not include a default proxy. You must use a Scrapingbypass Proxy with V2(s).
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(s) 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.

Use standard HTTP requests and the same integration logic and request code for Cloudflare and DataDome, without replacing your scraper framework. Keep the proxy IP, cookies and session consistent and validate response status and content. Keep API credentials on the server and use timeouts and bounded retries. Support for a specific target still depends on the site and challenge type. Test compatibility first; a shared plan does not guarantee access to every target. DataDome workflow.