Scrapingbypass API supports the integration of third-party IP proxies. You can route your requests through your preferred provider by configuring the x-cb-proxy header.

Configuration Requirements

To ensure successful integration, your third-party proxy must meet the following criteria:

• Format: Standard http://user:pass@host:port or http://host:port format.
• Protocol: Currently, only HTTP and HTTPS proxies are supported for the x-cb-proxy parameter.
• Header Implementation: Pass the proxy string as a value within the x-cb-proxy custom header in your API request.

Integration Workflow

1. Select Provider: Use any third-party residential, DC, or ISP proxy.
2. Define Header: Add the proxy credentials to your request headers.
3. Execute Request: The Scrapingbypass API node will receive your request, adopt the specified IP, and perform the target site bypass (JS Challenge/Turnstile) using that IP.

Important Technical Considerations

• IP Consistency: For V2 API session persistence, ensure you use the same third-party IP throughout the 10-minute session window to maintain the "cleared" status of the browser challenge.
• Whitelisting: If your third-party proxy provider requires IP whitelisting, you must whitelist the Scrapingbypass API server IPs to allow the connection.
• Latency: Using third-party proxies introduces an additional network hop, which may slightly increase overall request latency compared to using built-in Scrapingbypass Proxy services.