Scrapingbypass API V1 Integration Guide

Follow these steps to configure and integrate the Scrapingbypass API V1 into your automated workflows.

1. Account Registration

Create your developer account at the Scrapingbypass API Dashboard:
https://console.scrapingbypass.com/#/proxy/account

2. Purchase Credit Packages

Access the Billing or Package section in the dashboard to acquire credits.

  • Trial Access: New users can typically apply for a trial credit package via the "Promotion" or "Trial" tab in the dashboard to test technical compatibility before a full purchase.
  • Billing Logic: V1 consumes 1 credit per successful request.

3. Using the Code Generator

The Code Generator is the primary tool for debugging and generating integration snippets.

  • Distinguishing V1 vs. V2: * V1: Used for standard bypass requirements. It is selected by default or identified when the part parameter is absent.
    • V2: Specifically designed for complex JavaScript challenges and Turnstile. You can switch between versions via the toggle in the dashboard's configuration panel.
  • Validation: Use the "Test Request" button to ensure the target URL is successfully bypassed and the expected HTML/JSON payload is returned.

4. Integration into Custom Scripts

Once your test passes in the Code Generator, migrate the logic to your production environment:

  1. Copy the Generated Code: Select your preferred language (Python, Node.js, Go, etc.) from the generator and copy the snippet.
  2. Replace Placeholders: Ensure your Proxy-Authorization (User-Pass) and API Key are correctly mapped to your environment variables.
  3. Endpoint Configuration: Point your requests to the V1 API endpoint as specified in the generated code:
    http://api.scrapingbypass.com/v1/get (or the equivalent POST endpoint).
  4. Error Handling: Implement retry logic for 403 or 503 errors to handle transient network issues, keeping in mind that failed requests do not consume credits.

Integration Tip

Always maintain consistent User-Agent and TLS Fingerprint settings between your test environment and your production script to ensure the highest bypass success rate.