/integration/ — ScrapingBee proxy mode with Python Requests
Connect Python Requests to the ScrapingBee API through its proxy-compatible endpoint.
Integration. Official documentation · Checked · Review due .
documented capabilities
Proxy- Authentication
- Use the API key as proxy username and API parameters as the password.[1]
- Endpoints
- HTTP proxy port 8886 or HTTPS proxy port 8887 on proxy.scrapingbee.com.[1]
- Rendering
- The guide recommends setting render_js=False; rendering is otherwise enabled by default.[1]
- Billing
- Proxy mode retains the corresponding API request cost and default behavior.[1]
- TLS requirement
- The documented proxy mode requires disabling certificate verification in the client.[1]
Billing: Uses the same API-credit costs as the equivalent standard ScrapingBee API request.
Outputs: http-response
Documented for: Python Requests
[ official reference ][ provider discussion ][ JSON record ]
getting started
documentation reviewed- Choose the HTTP or HTTPS proxy endpoint.
- Build the proxy credentials using the API key and requested API options.
- Follow the provider’s client configuration requirements before using the Requests example.
Requirements & limitations
- The provider requires disabled certificate verification for proxy mode; assess that constraint before choosing this connection.
- This is a proxy front end for a scraping API, not an ordinary bandwidth-priced proxy pool.
- Disabling certificate verification removes TLS certificate authentication for that connection. Use the ordinary HTTPS API if your application requires verified TLS.
We reviewed the linked documentation. No live service connection, checkout or performance test is claimed for this listing.
primary sources
1 references- ScrapingBee proxy mode with Python Requests — official documentationChecked 2026-09-27