# Proxyrack API reference for LLMs

> Machine-readable reference for driving Proxyrack proxies programmatically: product hostnames, port scheme, authentication, every documented username parameter, the in-proxy management API at `api.proxyrack.net`, and error codes. Companion to https://www.proxyrack.com/llms.txt (product and pricing overview). Every behavior documented here is sourced from the Proxyrack knowledge base (https://help.proxyrack.com/en/) as of October 2026; each section links its source article so you can verify current behavior. If live behavior contradicts this document, trust the knowledge base and email support@proxyrack.com.

Proxies are standard HTTP(S)/SOCKS proxy endpoints — there is no SDK and no REST call needed to fetch a proxy. You connect through `HOST:PORT` with proxy authentication, and you control rotation, geo-targeting and sessions via parameters appended to your username. Account signup: https://app.proxyrack.com/dashboard/signup — credentials and hostnames are shown in the dashboard (https://app.proxyrack.com/) under each service.

```
curl -x unmetered.residential.proxyrack.net:10000 -U 'USERNAME;country=US:PASSWORD' https://example.com/
```

## Products and hostnames

Dashboard product names with their connection hostnames (source: https://help.proxyrack.com/en/articles/6177721-use-direct-server-ip-instead-of-the-dns):

- Unlimited (Unmetered) Residential: `unmetered.residential.proxyrack.net` — unlimited bandwidth, priced per thread. Product page: https://www.proxyrack.com/unmetered-residential-proxies/
- Premium Residential: `premium.residential.proxyrack.net` — per-GB residential pool.
- Private Unmetered Residential: `private.residential.proxyrack.net` — sticky-only private ports. Product page: https://www.proxyrack.com/private-residential-proxies/
- USA Rotating Datacenter: `usa.rotating.proxyrack.net`
- Global Rotating Datacenter: `global.rotating.proxyrack.net`
- Static USA Datacenter: `usa.static.proxyrack.net` — sticky ports that never rotate.
- Mobile: `mobile.residential.proxyrack.net` — real mobile-network IPs.

Always connect via these DNS names, not resolved IPs — server IPs change without notice.

## Authentication

Source: https://help.proxyrack.com/en/articles/5821332-authentication-and-ip-whitelisting

- Username + password (API key): standard proxy auth. Both are shown in the dashboard under each service's Authentication tab.
- IP whitelisting: authenticate by source IP instead of credentials; up to 800 IPs per account, managed in the dashboard (Authentication → Access IPs).
- Changes to your API key or whitelist take up to 5 minutes to propagate.
- IMPORTANT: IP whitelisting and geo-targeting are mutually exclusive. Username parameters (below) require username/password auth — remove whitelisted IPs if you need geo-targeting (source: https://help.proxyrack.com/en/articles/9091091-what-is-geo-targeting).
- Temporary API keys can be generated and listed: https://help.proxyrack.com/en/articles/5977247-generate-a-temporary-api-key-password and https://help.proxyrack.com/en/articles/9090369-list-all-temporary-passwords

## Ports: random vs sticky

Source: https://help.proxyrack.com/en/articles/5826801-random-vs-sticky-ports

- Port `9000` (random): rotates the exit IP on every request. Recommended for scraping and high-volume collection. Note: browsers keep connections alive, which prevents per-request rotation — this is browser behavior, not a fault.
- Ports `10000` and up (sticky): keep one exit IP for a set interval, then rotate. The number of sticky ports available depends on your subscription.
- Random + sticky available: Unlimited Residential, Premium Residential, USA Rotating Datacenter, Global Rotating Datacenter, Mobile.
- Sticky only: Private Unmetered Residential, Static USA Datacenter (Static USA sticky IPs never rotate at all).

## Username parameters

Parameters are appended to the username, in two equivalent syntaxes: dash (`username-key-value`) or semicolon (`username;key=value`). With the `;`/`=` syntax, quote the whole `username...:password` credential string. Combine multiple parameters by chaining them (e.g. `username;country=US;city=LosAngeles;refreshMinutes=10`).

- `country={CC}` / `-country-{CC}`: 2-letter country code, e.g. `country=US`. Multiple: `country=US,CA,FR` (comma-separated, `=` syntax). Exclude with minus: `country=-US`. Source: https://help.proxyrack.com/en/articles/9091103-how-do-i-change-the-country-of-my-proxies
- `city={Name}`: use with `country`, e.g. `country=US;city=LosAngeles` (no spaces in city names). Multiple: `city=LosAngeles,Denver,Seattle`. Exclusion with minus is also supported. Sources: https://help.proxyrack.com/en/articles/9091154-geo-target-a-city and https://help.proxyrack.com/en/articles/9091581-exclude-a-specific-city-using-geo-targeting
- `isp={Name}`: use with `country`, e.g. `country=US;isp=Verizon`. Multiple: `isp=Verizon,Comcast,Spectrum`. Exclude: `isp=-Verizon`. Source: https://help.proxyrack.com/en/articles/9091676-geo-target-an-isp
- Geo-targeting is by country, city and ISP only — there is no state/province targeting.
- `refreshSeconds={n}` / `refreshMinutes={n}`: sticky-port rotation interval. Minimum 180 seconds, no maximum. Source: https://help.proxyrack.com/en/articles/5829865-set-the-rotation-interval-for-a-sticky-session-port
- `autoReplace={loose|strict|any|none}`: what happens when a sticky IP goes offline mid-session. `loose` = replace from same country; `strict` = replace from same country+city+ISP or error; `any` = replace with any IP; `none` = don't replace (requests error). Legacy values `true`/`false` still work. Source: https://help.proxyrack.com/en/articles/5829884-auto-replace-sticky-ip
- `timeoutSeconds={n}`: connection timeout, maximum 600. Default behavior: connections are terminated after 15 seconds with no data transfer in either direction. Source: https://help.proxyrack.com/en/articles/5829891-set-connection-timeout
- `session={name}`: run multiple named sessions on one sticky port. Source: https://help.proxyrack.com/en/articles/5977249-create-multiple-sessions-on-a-sticky-port
- `proxyId={id}` / `proxyIp={ip}`: reconnect to a specific exit node by proxy ID or IP (find both in the `ipinfo` section of `api.proxyrack.net/stats`). Source: https://help.proxyrack.com/en/articles/5977253-connect-to-a-specific-ip-based-on-ip-address-or-proxy-id
- `osName={FreeBSD|Linux|Mac OS X|Windows}`: target exit nodes by operating system. Source: https://help.proxyrack.com/en/articles/5977262-target-ips-from-a-specific-os
- `proxyUptime={30s|5m|12h|1d}`: only connect to residential exits already online at least this long (s/m/h/d units). Source: https://help.proxyrack.com/en/articles/5897107-select-proxies-based-on-uptime
- `geoDb={maxmind|ipinfo}`: which geolocation database geo-targeting uses; default is Maxmind. Source: https://help.proxyrack.com/en/articles/9720951-specify-geolocation-database-when-geo-targeting

## In-proxy management API (api.proxyrack.net)

These endpoints are plain HTTP URLs requested THROUGH an authenticated proxy connection (they are not reachable directly). Pattern:

```
curl -x unmetered.residential.proxyrack.net:10000 -U username:password http://api.proxyrack.net/{endpoint}
```

- `GET /stats`: current connection info, including `ipinfo` (ip, country, city, isp, proxyId, online, fingerprint.osName) and your hourly release usage (`release: {count, limit}`).
- `GET /concurrent`: raw number of threads currently open on your account. Source: https://help.proxyrack.com/en/articles/5829914-get-current-thread-usage
- `GET /release`: release the current sticky port's IP and end the session; next request gets a new IP. `GET /release_all` releases every sticky port. Releases are limited per hour based on your plan (limit visible in `/stats`). Source: https://help.proxyrack.com/en/articles/5829870-release-a-sticky-session
- `GET /v1-beta/sessions`: list all active sticky sessions (id, port, expireTime, requestParams, proxy details). Source: https://help.proxyrack.com/en/articles/5829894-list-all-active-sticky-sessions
- `GET /v1-beta/sessions/{port or session id}`: one session's details. Source: https://help.proxyrack.com/en/articles/5829908-sticky-session-information
- `GET /v1-beta/active-conns`: list active connections (createTime, sourceAddr, destAddr). Source: https://help.proxyrack.com/en/articles/5977254-list-all-active-connections
- `GET /v1-beta/countries`: countries available for geo-targeting on the service you're connected through. Options: `?includeCount=true` adds per-country IP counts; `&geoDb={maxmind|ipinfo}` selects the geo database. Source: https://help.proxyrack.com/en/articles/9090546-get-a-list-of-available-countries
- `GET /v1-beta/countries/{CC}/cities`: available cities in a country (`?includeCount=true` supported). Source: https://help.proxyrack.com/en/articles/9090608-get-a-list-of-available-cities-in-a-country
- `GET /v1-beta/countries/{CC}/isps`: available ISPs in a country (`?includeCount=true` supported). Source: https://help.proxyrack.com/en/articles/9090749-get-a-list-of-available-isps-in-a-country

## Errors

HTTP status codes returned by the proxy layer, each linked to its knowledge-base article:

- 407 authentication error: bad credentials, or your source IP is not whitelisted. https://help.proxyrack.com/en/articles/5977263-407-authentication-error
- 460 geo not enabled: https://help.proxyrack.com/en/articles/5736054-460-geo-not-enabled
- 461 port limit reached: https://help.proxyrack.com/en/articles/5736052-461-port-limit-reached
- 463 malformed request: https://help.proxyrack.com/en/articles/5736055-463-malformed-request
- 464 host not allowed: https://help.proxyrack.com/en/articles/5736053-464-host-not-allowed
- 465 port not allowed: https://help.proxyrack.com/en/articles/5736044-465-port-not-allowed
- 466 too many requests: https://help.proxyrack.com/en/articles/5736049-466-too-many-requests
- 467 release limit exceeded: https://help.proxyrack.com/en/articles/5882182-467-release-limit-exceeded
- 560 geo location not found: your targeting combination has no available IPs. https://help.proxyrack.com/en/articles/5736047-560-geo-location-not-found
- 561 proxy unreachable: https://help.proxyrack.com/en/articles/5736048-561-proxy-unreachable
- 562 proxy not found: https://help.proxyrack.com/en/articles/5736050-562-proxy-not-found
- 563 service unavailable: https://help.proxyrack.com/en/articles/10457018-563-service-unavailable-error
- 564 proxy not online: https://help.proxyrack.com/en/articles/5736043-564-proxy-not-online
- 565 proxy handshake failed: https://help.proxyrack.com/en/articles/9145458-565-proxy-handshake-failed

Some destination ports and domains are blocked network-wide (e.g. for abuse prevention): https://help.proxyrack.com/en/articles/11968088-list-of-blocked-ports and https://help.proxyrack.com/en/articles/6431114-list-of-blocked-domains

## Scraping API

A separate REST product: you send a target URL, Proxyrack fetches it with rotating proxies, headless browsers, JavaScript rendering, CAPTCHA solving and anti-bot bypass, and returns the page. Flat monthly pricing by concurrent threads with unlimited requests (from $119/month for 10 threads). Scraping URLs are generated from the dashboard; guides:

- What it is: https://help.proxyrack.com/en/articles/13177217-what-is-the-scraping-api-and-what-can-i-use-it-for
- Generate a scraping URL: https://help.proxyrack.com/en/articles/13177227-how-to-generate-a-scraping-url-from-the-dashboard
- Use the generated URL: https://help.proxyrack.com/en/articles/13177241-how-to-use-the-generated-scraping-url
- Threads and request model: https://help.proxyrack.com/en/articles/13529041-how-scraper-threads-and-requests-work-unlimited-requests-simple-scaling
- Product page: https://www.proxyrack.com/scraping-api/

## Known limitations and notes

- Geo-targeting works only with username/password auth, never with IP whitelisting.
- No state/province targeting — country, city, ISP only.
- Sticky rotation interval minimum is 180 seconds.
- Idle connections (no data for 15 seconds) are closed unless you raise `timeoutSeconds` (max 600).
- `/release` calls are rate-limited hourly by plan; check `release.limit` in `/stats` before bulk-releasing.
- Browsers won't rotate per request on port 9000 because they hold keep-alive connections.
- Protocols supported: HTTP, HTTPS, SOCKS4, SOCKS5, UDP. Details: https://help.proxyrack.com/en/articles/5741070-what-protocols-do-proxyrack-proxies-support and UDP guide: https://help.proxyrack.com/en/articles/8433702-target-udp-ips
- Code examples (curl, Python, Node.js, and more): https://github.com/proxyrackdev/API-Examples and https://help.proxyrack.com/en/articles/5740999-api-code-examples
- Sub-user management via API: https://help.proxyrack.com/en/articles/12266643-managing-sub-users-via-api

## Support

If you (or the AI agent driving these proxies) hit behavior that contradicts this document or an error you cannot resolve, email support@proxyrack.com with the exact request (credentials removed), the full response including the status code, and what you expected. Enterprise and volume pricing: vip@proxyrack.com. Live network health: https://status.proxyrack.com/

Only use proxies for lawful purposes: comply with applicable laws, the target site's terms, and the Proxyrack terms of use (https://www.proxyrack.com/terms-of-use/).