Skip to content
IsabiProxy

Documentation

IsabiProxy Docs

Quick Start

Five steps, five minutes.

  1. 1

    Create an IsabiProxy account.

    Sign up with your email — no card needed to explore the dashboard.

  2. 2

    Choose your proxy type.

    Residential, static residential, datacenter, or mobile — see the proxy types section if unsure.

  3. 3

    Select your location.

    Country first; city or ISP where the product and stock allow.

  4. 4

    Generate your proxy credentials.

    The dashboard issues a host, port, username, and password.

  5. 5

    Connect your browser or application.

    Use the Chrome extension, or plug the credentials into any HTTP client.

curl (HTTP proxy)

curl -x http://USERNAME:PASSWORD@proxy.isabi.cloud:8080 https://example.com

curl (SOCKS5)

curl --proxy socks5h://proxy.isabi.cloud:1080 https://example.com

Python (requests)

import requests

proxies = {"https": "http://USERNAME:PASSWORD@proxy.isabi.cloud:8080"}
print(requests.get("https://example.com", proxies=proxies).status_code)

Authentication

HTTP / HTTPS

Your username and password are sent via the standard Proxy-Authorization header — every mainstream client handles this automatically when credentials are in the URL or settings.

SOCKS5

SOCKS5 supports username/password auth, but client support varies. Some environments — notably Chromium's SOCKS implementation — do not send credentials at all. For browser work with authentication, prefer HTTP or HTTPS.

Rotation & Sticky Sessions

Rotating proxies change the exit address automatically — per request or on a timer, depending on the product. Sticky sessions hold one address for a fixed duration (commonly 10–30 minutes), which multi-step flows like logins and carts need. Static proxies keep one address for the life of the resource.

You pick the mode when generating the proxy. The generator only offers modes the chosen product supports.

Troubleshooting

  • Connection refused: check the port and protocol; confirm the proxy is not paused in the dashboard.
  • Auth failures on HTTP: re-copy the credentials; they are per-proxy.
  • SOCKS5 login prompts in Chrome: expected — Chromium cannot send SOCKS credentials; switch to HTTP/HTTPS.
  • Wrong location: verify the exit IP with the IP checker; targeting applies at generation time.

Still stuck? Contact support.