Skip to main content
All Proxies.fo endpoints use user : password authentication over HTTP, HTTPS, and SOCKS5. Targeting (country, state, city, ASN, session, lifetime) is controlled by modifiers appended to your username — there’s no separate API, no config file, no SDK.

​
Credential format

Username: <base_user>[-<modifier>-<value>][-<modifier>-<value>]...
Password: <your_account_password>
Your base username and password live in the dashboard. Modifiers are optional — without them, the network picks an IP at random from the full pool for whichever regional gateway you connected to.

​
Real-world examples

Residential — targeting Westlake Village: 
pr-eu.proxies.fo:13337:adminpcowe-country-us-city-westlakevillage:maskxsndyb
Residential — targeting AT&T (ASN 7018) in the US: 
pr-eu.proxies.fo:13337:adminpcowe-country-us-asn-7018:maskxsndyb
Datacenter — rotating on every request: 
dcp-eu.proxies.fo:10808:adminywsve:jwqcoz4lfm
Datacenter — sticky session for 300 seconds: 
dcp-eu.proxies.fo:10808:adminywsve-session-5s5d4xud-duration-300:jwqcoz4lfm
Each of those strings follows the host:port:username:password format most proxy testers and browser extensions expect.

​
Modifier reference

ModifierProductsPurposeExample
country-<code>ResidentialISO 3166-1 alpha-2 country codecountry-us, country-de, country-nl
state-<code>ResidentialRegional subdivision code (optional)state-ny, state-ca
city-<n>ResidentialTarget a specific city (works with or without state-)city-westlakevillage, city-pleasanton
asn-<number>ResidentialTarget a specific ISP by Autonomous System Numberasn-7018 (AT&T), asn-7922 (Comcast)
session-<id>Residential, DatacenterSticky session ID — any string you choosesession-5s5d4xud
ttl-<minutes>ResidentialSession lifetime in minutesttl-15
duration-<seconds>DatacenterSession lifetime in secondsduration-300
Residential uses ttl-<minutes>. Datacenter uses duration-<seconds>. Don’t mix them — passing ttl- to a DC endpoint or duration- to residential is ignored or rejected. Datacenter doesn’t support country / state / city / ASN targeting — the regional endpoint (dcp-us or dcp-eu) determines geography. ISP uses static assigned IPs, so no targeting modifiers apply.

​
Targeting granularity (residential)

All of these are valid — pick the level of precision you need. Modifiers stack in any sensible combination:
TargetUsername format
Random IP, any countryadminpcowe
Any US IPadminpcowe-country-us
New York stateadminpcowe-country-us-state-ny
Specific city (state skipped)adminpcowe-country-us-city-westlakevillage
Specific city within stateadminpcowe-country-us-state-ca-city-pleasanton
Specific ISP (AT&T)adminpcowe-country-us-asn-7018
ISP + city combinedadminpcowe-country-us-city-pleasanton-asn-7018
If you know the city, you can skip state- entirely. Include it only when disambiguation is needed (two cities with the same name in different states).

​
ASN targeting

asn-<number> pins your IP to a specific ISP by its Autonomous System Number. Useful when a target correlates IP behaviour with the ISP (e.g. verifying ads served to AT&T customers, testing a CDN’s ISP peering, or simulating traffic from a specific carrier). Common US ASNs:
ASNISP
7018AT&T
7922Comcast
701Verizon
20115Charter / Spectrum
22773Cox
209CenturyLink
2828Verizon Business
Find the ASN for any IP using whois, bgp.he.net, or ipinfo.io. 
# Target AT&T subscribers in the US
curl -x "http://adminpcowe-country-us-asn-7018:maskxsndyb@pr-us.proxies.fo:13337" \
  https://api.ipify.org
ASN stacks with every other modifier — you can narrow to a specific city and a specific ISP within that city: 
# Comcast subscribers in Pleasanton, CA
curl -x "http://adminpcowe-country-us-city-pleasanton-asn-7922:maskxsndyb@pr-eu.proxies.fo:13337" \
  https://api.ipify.org
The narrower the combined targeting, the smaller the IP pool — for high-concurrency workloads, keep at least one level wide.

​
Session IDs

Use any string you want — alphanumeric, 6–16 characters is typical. Same ID = same IP. Good examples: 5s5d4xud, bot-nyc-01, a4f8c2e1 Avoid:
  • Spaces or special characters that break URL parsing ($, @, :, /)
  • Sequential IDs (session-1, session-2) if you want session isolation
  • Reusing IDs across unrelated workflows

​
Protocols

ProductHTTP / HTTPSSOCKS5UDP
Residential✓✓✓
Datacenter✓✓✓
ISP✓ (port 61234)✓ (port 62234)—

​
Rotating credentials

If credentials leak, rotate 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.