Scrapingbypass API does not currently support Selenium or Puppeteer. The service operates by simulating browser requests at the protocol level rather than launching a headless or headed browser instance.
Fingerprint Browser Integration
While it is technically possible to integrate Scrapingbypass API with fingerprint browsers, we strongly discourage this approach for the following reasons:
- Inefficient Billing: Due to the API's credit model, using a fingerprint browser will lead to rapid credit depletion. Every resource successfully loaded by the browser (images, scripts, CSS) counts as a separate request. A single page load can consume hundreds of credits.
- Performance Overhead: Browser-based automation significantly reduces scraping throughput and increases latency compared to direct API integration.
- Lack of Automation Frameworks: Our API is optimized for non-browser environments. Currently, we do not provide official automation solutions or drivers for browser-based tools.
Recommended Integration
For optimal results, we recommend integrating Scrapingbypass API directly into your backend code using HTTP client libraries. This ensures precise control over TLS/JA3 impersonation and session management while maintaining high efficiency.
- V2 API Implementation: Use the API to handle JS challenges and Turnstile verification directly.
- Cookie Persistence: Maintain the session state within your application logic to avoid redundant validations and credit costs.
