Custom Proxy
If you already have your own proxy infrastructure or a subscription to a third-party proxy service, you can route ScrAPI requests through your own proxy server. This gives you full control over the proxy IP, protocol, and authentication.
Set the customProxyUrl parameter to your proxy URL in the format protocol://username:password@host:port. There is no need to set proxyType to Custom - it is implied automatically when customProxyUrl is provided.
Custom proxies do not consume additional credits. See Credit Usage for details.
When To Use This
- Existing proxy subscriptions - Leverage proxy services you already pay for (e.g., Bright Data, Oxylabs, SmartProxy) while using ScrAPI’s scraping engine.
- Enterprise network access - Route requests through corporate SOCKS or HTTP proxies to reach internal or restricted websites.
- Specific IP requirements - When you need requests to originate from a particular IP address that you control.
- Cost optimization - Use your own proxy infrastructure to avoid per-request proxy credit charges.
Supported Protocols
http://- Standard HTTP proxyhttps://- Encrypted HTTP proxysocks4://- SOCKS4 proxysocks5://- SOCKS5 proxy (supports authentication)
Example Request
POST https://api.scrapi.tech/v1/scrape
With Authentication
{
"url": "https://deventerprise.com",
"customProxyUrl": "socks5://username:password@scrapi.tech:8080"
}Without Authentication
{
"url": "https://deventerprise.com",
"customProxyUrl": "https://scrapi.tech:9090"
}Related Features
- Data Center Proxy - ScrAPI-managed alternative if you don’t have your own proxy.
- Residential Proxy - Premium ScrAPI-managed proxy with global geolocation.
- Sessions - Maintain consistent state across requests when using your custom proxy.
- Credit Usage - Custom proxies add no extra credit cost.
Testing
Test this request in the Playground or view the OpenAPI specification.