All Proxies.fo endpoints use user : password authentication over HTTP, HTTPS, and SOCKS5. Targeting (country, state, city, session, TTL) is controlled by modifiers appended to your username — there’s no separate API, no config file, no SDK.
Username: <base_user>[-<modifier>-<value>][-<modifier>-<value>]...
Password: <your_account_password>
Full example
A residential request targeted at New York City with a 15-minute sticky session:
Username: acme-country-us-state-ny-city-ran-session-asdas1-ttl-15
Password: hunter2
| Segment | Meaning |
|---|
acme | Base username |
country-us | Route through a US IP |
state-ny | Narrow to New York state |
city-ran | Target the “ran” (random city in state) pool — or replace with a specific city code |
session-asdas1 | Sticky session ID — same ID keeps the same IP |
ttl-15 | Hold that IP for 15 minutes |
Supported modifiers
| Modifier | Products | Purpose | Example |
|---|
country-<code> | Residential | ISO 3166-1 alpha-2 country code | country-us, country-de, country-nl |
state-<code> | Residential | US/regional state code | state-ny, state-ca |
city-<code> | Residential | Specific city, or ran for random city in state | city-nyc, city-ran |
session-<id> | Residential, Datacenter | Sticky session ID (any string you choose) | session-abc123 |
ttl-<minutes> | Residential | Session lifetime in minutes | ttl-15, ttl-30 |
Datacenter does not support country/state/city targeting. Pick the regional endpoint (dcp-us or dcp-eu) that’s closest to your target — that determines egress geography.ISP uses static assigned IPs, so targeting modifiers don’t apply either.
Protocols
| Product | HTTP / HTTPS | SOCKS5 | UDP |
|---|
| Residential | ✓ | ✓ | ✓ |
| Datacenter | ✓ | ✓ | ✓ |
| ISP | ✓ (port 61234) | ✓ (port 62234) | — |
Rotating credentials
If you suspect credentials have leaked, rotate them from the dashboard under Account → Security. Existing sessions drop within 60 seconds.
Never commit credentials to version control. Use environment variables or a secrets manager.
