One gateway. No SDK required.
InsideProxy doesn't use a REST API for traffic — you authenticate and target with a single username string over a standard HTTP/SOCKS5 proxy connection. This page documents exactly how that string works.
Overview
Every proxy type — residential, ISP, datacenter, mobile, IPv6 — is reached through the same gateway. There's nothing to install: point any HTTP, HTTPS or SOCKS5-capable client at the gateway, authenticate with your username and password, and encode what you want (country, city, session behavior) directly into the username string.
Authentication
Authentication is standard HTTP proxy basic auth — no API keys, tokens or headers. Your credentials are the username shown on Generate proxies and your account password, passed the same way you'd authenticate any proxy:
http://username:password@gate.insideproxy.net:7001Gateway & ports
One hostname handles every proxy type and protocol — the port and your username string determine what you get, not a separate endpoint per product.
| Host | Port | Protocol |
|---|---|---|
| gate.insideproxy.net | 7001 | HTTP / HTTPS |
| gate.insideproxy.net | 7002 | SOCKS5 |
Targeting syntax
Targeting is encoded directly into the username using hyphen-separated segments — no separate parameters or request headers.
user-CC-us-city-newyork-time-30-session-a1b2c3d4| Segment | Meaning |
|---|---|
| user | Your account username, shown on Generate proxies. |
| CC-us | Country targeting via ISO 2-letter code. Omit entirely for any country. |
| city-newyork | Optional city targeting, lowercase with no spaces. Requires a country segment. |
| time-30 | Requested sticky duration in seconds — see Sessions & rotation below. |
| session-a1b2c3d4 | Sticky session ID, 8 characters — same segment, reused, pins the IP. |
Sessions & rotation
By default, every request gets a fresh IP. To hold the same IP across multiple requests — for a login flow or a multi-step checkout, for example — add a session suffix.
- -time-30-session-a1b2c3d4 requests a sticky IP, pinned to that exact session ID string. time-N is the requested duration in seconds, but treat it as advisory — our own testing found a session can stay pinned well past its requested N. Don't rely on it as a timer.
- To reliably get a new IP, change the session- value yourself — any different 8-character string opens a fresh sticky session with its own new IP, confirmed on every test we ran.
- Drop -time- and -session- entirely to rotate on every single request.
Code examples
The same credentials work with any HTTP client — here's the gateway in the languages people ask about most.
curl -x http://user-CC-us-time-30-session-a1b2c3d4:PASSWORD@gate.insideproxy.net:7001 https://api.ipify.orgStatus codes
The gateway itself returns standard HTTP status codes. Anything from the target site passes straight through unchanged.
OK
Request routed successfully and the target responded normally.
Proxy Authentication Required
Your username or password is missing or incorrect. Check the credentials in your Generate proxies page.
Too Many Requests
You have exceeded the concurrency or rate limit for your plan. Back off and retry with backoff.
Bad Gateway
No healthy exit IP was available for the requested targeting. Rare — retry, ideally with a different session ID.
Gateway Timeout
The target site itself timed out. Not a proxy-side failure — increase your client timeout or retry.
Rate limits
There is no cap on concurrent threads or sub-users on any plan — you're only metered on bandwidth or IPs consumed, depending on the product. In practice this means you can open as many parallel connections as your own infrastructure can sustain; the gateway scales with you rather than throttling a thread count.
Common errors
Connection refused
Double-check the gateway host and port — gate.insideproxy.net:7001 — and that your firewall allows outbound connections on that port.
407 on every request
Your username or password string is malformed. Copy it fresh from Generate proxies rather than typing it by hand — the session suffix is easy to mistype.
Same IP every request when you expected rotation
You're reusing a sticky session ID (the -session-xxxxxxxx segment). Drop -time-/-session- entirely, or change the session ID, to rotate on every call.
Different IP every request when you expected a sticky session
Add -time-30-session-xxxxxxxx and reuse the exact same username string across requests. Treat -time-N as advisory, not a guaranteed auto-expiry — our own testing found a session can outlive its requested N seconds. If you need a new IP on a schedule, change the session ID yourself rather than waiting on -time-N.
Still stuck? Contact support or browse the Knowledge Base.