1. Account Registration

Access the Scrapingbypass API Dashboard to create your account and manage your developer credentials.

• Dashboard URL: https://console.scrapingbypass.com/#/proxy/account

2. Credit Acquisition

Scrapingbypass API operates on a credit-based consumption model.

• Trial Credits: New users can contact support or check the dashboard promotions to claim initial test credits.
• Purchase: Select a package based on your expected traffic volume. Credits are deducted only upon successful requests.

3. Using the Code Generator (Sandbox)

The Code Generator is the primary tool for debugging your requests before moving to production.

Selecting API Versions

• V1: Used for standard web scraping where simple bypass is sufficient.
• V2: Mandatory for sites protected by Cloudflare Turnstile, JS Challenges, or advanced WAF rules.
• Detection: You can toggle between versions in the generator settings. Note that V2 requires additional headers and parameters (e.g., part="0").

Proxy Configuration (V2 Requirement)

Unlike V1, V2 requires a proxy. You must configure either a Static Residential Proxy or a Rotating Proxy within the request.

• Reason: V2 binds the browser fingerprint and challenge solution to a specific IP address to prevent WAF detection.

4. Integration into Your Workflow

Once your request successfully passes in the Code Generator, follow these steps to integrate it into your script:

Step 1: Copy Request Metadata

Extract the following from the Code Generator:

• Endpoint URL: Ensure you are hitting the correct gateway.
• Headers: Verify Proxy-Authorization, X-Cb-Sitekey (if applicable), and User-Agent.
• Payload: For V2, ensure the [cf_token] placeholder is placed in the correct JSON fields or headers.

Step 2: Implement Session Persistence

To optimize credit consumption and maintain a "passed" state:

• Maintain the Session: Reuse the same proxy credentials and headers for 10 minutes.
• Handle Responses: Ensure your script handles standard HTTP status codes (200 for success, 403 for blocked/expired sessions).

Step 3: Production Deployment

• Replace hardcoded parameters with environment variables.
• Set up a retry logic for failed requests (which do not consume credits) to ensure high reliability.

Important Note

For V2 requests, always include the part="0" parameter in your request body or query string. This triggers the advanced bypass engine required for Cloudflare's latest protection layers.