Tokens
| Token | Value | Description |
|---|---|---|
-country-<cc> | ISO 3166-1 alpha-2 (us, gb, de, jp…) | Exit country. Omit for any country. |
-state-<st> | State / region name | Narrow within a country. |
-city-<city> | City name (lowercase, no spaces) | Narrow to a city. Takes precedence over state. |
-asn-<n> | ASN number | Target a specific network/carrier. |
-session-<id> | Your chosen id | Keep the same IP across requests. See Sessions. |
-sesstime-<min> | Minutes, 3–1440 | How long a sticky session holds its IP. |
Use lowercase ISO country codes. Combine
-city- with -country- for accuracy (for example -country-us-city-newyork).Examples
Common locations
A few popular locations to get you started. Any ISO 3166-1 alpha-2 country code works, so this list is illustrative, not exhaustive.| Country | Code | Example city token |
|---|---|---|
| United States | us | -city-newyork |
| United Kingdom | gb | -city-london |
| Germany | de | -city-berlin |
| Canada | ca | -city-toronto |
| France | fr | -city-paris |
| Japan | jp | -city-tokyo |
Country targeting spans 195+ countries. State and city targeting work where the pool has coverage. If a specific city returns no exits, broaden to the country.
Notes
- Country codes follow the ISO 3166-1 alpha-2 standard.
-city-and-state-are mutually exclusive. If you set both, city wins.- The more specific your targeting, the smaller the available pool, which can affect availability and speed in some locations.
- Targeting tokens are case-insensitive, but lowercase is recommended.
Next: Sessions
Keep the same IP with sticky sessions, or rotate on every request.