Cloudflare and DataDome share the same API integration logic and request code. 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 one API credit balance, consumption rules and pricing. Choose a plan based on your usage; proxy traffic is billed separately. View pricing
After successfully testing the code generator, integrate the generated configuration into your local environment by following these steps to execute the HTTP request.
1. Integrate Generated Parameters
Copy the specific parameters generated (such as x-cb-fp, user-agent, or cookie) and embed them into your HTTP request headers or body. Ensure the values match the exact output from the generator to maintain fingerprint consistency.
2. Configure the HTTP Request
Construct your request using the standard Scrapingbypass API format. Use the following structure for your implementation:
- Endpoint: Direct your requests to the specific V1 or V2 gateway URL.
- Method: Typically
POST. - Headers: Include your
Proxy-Authorization(if applicable) and the mandatoryContent-Type: application/json. - Body: Pass the generated code/parameters within the JSON payload.
3. Execution Flow
Once the request is constructed, transmit it via your preferred library (e.g., Axios, Requests, or Go http.Client).
- Request Transmission: Send the formatted HTTP request to the Scrapingbypass server.
- Validation Handling: The API will use the provided parameters to solve challenges (JS, Turnstile, or WAF).
- Response Retrieval: Upon success, the API returns the target website's HTML or JSON data.
4. Session Maintenance (V2 Only)
If you are using Scrapingbypass API V2, capture the session state from the initial response. Reuse these parameters within the valid session to reduce repeated challenges. Each successful request still consumes 1 credit; session reuse does not make subsequent requests free.
Important: Always ensure your local TLS/JA3 fingerprint matches the parameters provided by the code generator to prevent detection by advanced WAFs.