cURL proxy integration
cURL is the fastest way to sanity-check a proxy before you wire it into code. The -x flag sets the gateway and -U passes your username and password, so a single command tells you whether traffic is leaving through Murphy. The same flags drop straight into any shell script.
# HTTP proxy with username and password
curl -x http://gateway.murphyproxies.com:8000 \
-U USERNAME:PASSWORD \
https://httpbin.org/ip
# SOCKS5 in one flag (credentials inline)
curl --proxy socks5://USERNAME:PASSWORD@gateway.murphyproxies.com:8000 \
https://httpbin.org/ip
# Reuse a proxy across a session via an environment variable
export https_proxy="http://USERNAME:PASSWORD@gateway.murphyproxies.com:8000"
curl https://httpbin.org/ipSetup in 5 steps
- 1Set the gateway with -x http://gateway.murphyproxies.com:8000.
- 2Pass your credentials with -U USERNAME:PASSWORD (or inline them in the proxy URL).
- 3Request an IP echo endpoint like https://httpbin.org/ip to read back the exit IP.
- 4For SOCKS5, swap the scheme to socks5:// on the --proxy flag.
- 5Export https_proxy in your shell to route every following cURL call without repeating the flags.
cURL proxy questions
Everything you need to route cURL through Murphy, from authentication to rotation.
The -x (or --proxy) flag sets the proxy host and port, while -U (or --proxy-user) supplies the username and password. You can also fold the credentials into the -x URL as user:pass@host:port and skip -U entirely.
Use the socks5:// scheme on the proxy URL, for example --proxy socks5://USERNAME:PASSWORD@gateway.murphyproxies.com:8000. Use socks5h:// instead if you want DNS resolution to happen on the proxy side.
Yes. Export the https_proxy and http_proxy environment variables with your credentials, and every cURL call in that shell session will use the Murphy gateway without needing the -x flag each time.
Get credentials for cURL
Pick the network that fits your target. ISP proxies for fast, stable sessions, residential proxies for broad IP diversity against strict anti-bot systems.