Proxies for cURL

Before you start

You need an active plan, your gateway credentials from the dashboard, and either your server IP whitelisted or a user and password pair. Replace USER:PASS in the examples with your real credentials.

The rotating port gives a new IP on every request. Sticky ports hold one address for the life of the session, and both live on the same host, so you choose by port rather than by product.

The gotcha worth knowing

Use socks5h rather than socks5 so DNS resolution happens at the proxy rather than on your machine, which prevents your real resolver leaking the hostname you are requesting.

Configuration

cURL is the fastest way to confirm your credentials work before wiring the proxy into anything larger.

# rotating: new IP each call
curl -x http://USER:PASS@gateway.proxyrotator.com:11000 https://api.ipify.org

# SOCKS5 on the same host
curl -x socks5h://USER:PASS@gateway.proxyrotator.com:11000 https://api.ipify.org

# verbose, to see the proxy handshake
curl -v -x http://USER:PASS@gateway.proxyrotator.com:11000 https://api.ipify.org

Where to go next

Running more than one tool against the same gateway is normal. These cover the others.

• All integration guides, setup notes for every tool we cover
• Guides and tutorials, the concepts behind the config, including when to rotate and when not to
• Postman setup, another library or framework wired to the same gateway
• Apify setup, another library or framework wired to the same gateway
• Rotating proxies, a new IP per request, which is the default for crawling