Integrations

Every proxy you buy from RoProxy is a username, a password, a gateway host and two ports, so any HTTP client or browser automation tool can use it. These guides show the exact setup for each tool, plus how to switch between sticky and rotating IPs and trigger a new IP from your code.

What every tool needs

Whatever the language or framework, the setup comes down to the same few values from your proxy.

  • HTTP and HTTPS

    Point the tool at http://USERNAME:PASSWORD@GATEWAY_HOST:HTTP_PORT. HTTPS sites use the same port through a CONNECT tunnel, so encryption stays between your code and the site.

  • SOCKS5

    Pro and Business proxies add socks5://USERNAME:PASSWORD@GATEWAY_HOST:SOCKS5_PORT for tools that only speak SOCKS5. It carries TCP, not UDP.

  • One proxy per job

    Credentials belong to a single proxy. Give parallel jobs their own proxies and they never share, or fight over, an IP.

Rotate from your code

Create an API key in the dashboard and send it as Authorization: Bearer API_KEY. GET https://backend-api.ro-proxy.com/api/session lists your proxies, and POST https://backend-api.ro-proxy.com/api/session/SESSION_ID/rotate gives one a new IP at once, which is the usual answer to a 403 or 429 from a site.

Free proxies cannot be rotated by hand: their IP changes every 10 minutes on its own. On Pro and Business a manual rotation waits 30 seconds after the previous one; calling earlier returns 429, so treat that response as a cue to wait rather than as a failure.