Targeting

Targeting narrows the set of exits eligible for a request. Start with the broadest constraint that satisfies the use case, then add detail only when the result must be more specific.

Token grammar

Target	Token	Example
Continent	continent-{code}	continent-eu
Country	country-{iso2}	country-us
Region	region-{slug}	region-texas
City	city-{slug}	city-houston
ASN	asn-{number}	asn-7018

Use lowercase values and hyphens for spaces. Country values use a two-letter ISO code. Retrieve continent codes from GET /locations/continents for the selected package instead of hard-coding them. Available continents, regions, cities, and ASNs depend on the package and current provider catalog.

package-elite-country-us-region-texas-city-houston-asn-7018

Target a continent

Continent targeting is a broad alternative to country, region, city, ASN, and ISP targeting. Send only the continent token and the gateway selects an eligible country and provider inside that continent.

−+×

RequestGET https://api.ipify.org?format=json

curl 'https://api.ipify.org?format=json' \
  --proxy 'http://package-elite-continent-eu:{proxy_password}@{proxy_host}:{proxy_port}'

−+×

Response200 OK

{
  "ip": "203.0.113.42"
}

Replace placeholders in braces with your values. Responses use synthetic example data.

−+×

RequestGET https://api.ipify.org?format=json

curl 'https://api.ipify.org?format=json' \
  --proxy 'socks5h://package-elite-continent-eu:{proxy_password}@{proxy_host}:{proxy_port}'

−+×

Response200 OK

{
  "ip": "203.0.113.42"
}

Replace placeholders in braces with your values. Responses use synthetic example data.

Use one location form per credential:

{package}-continent-{continent}
{package}-country-{cc}-region-{region}-city-{city}-asn-{asn}

Do not append country, region, city, ASN, or ISP tokens to continent-{code}. If no eligible route exists inside the requested continent, the request fails rather than widening to another continent.

Precision reduces the eligible pool

Country + region + city + ASN is an intersection, not a fallback sequence. If the intersection is empty, remove the least important constraint rather than retrying the same impossible request indefinitely.

Selection strategy

1. Retrieve the package or order used for the connection.
2. Read available location and network options for that package through the API.
3. Choose the minimum set of constraints required by the product promise.
4. Normalize human labels to the exact slug or identifier returned by the catalog.
5. Cache catalog results and refresh on a package change or cache miss.

Availability matrix

Requirement	Suggested targeting	Availability impact
Any exit	No location token or country-any when supported	Lowest
Continental coverage	Continent	Low
Country compliance	Country	Low
Localized content	Country + region or city	Medium
Network-specific validation	Country + ASN	Medium to high
Exact local network	Country + region + city + ASN	Highest

Combine targeting with a session

Place sid and ttl after targeting tokens:

package-elite-continent-eu-sid-cart-42-ttl-1800

Session tokens work with continent and more precise location targeting. Changing the targeting while reusing the same session ID creates a different routing request. Keep both stable when continuity matters.

SAFE SANDBOX

Compose a proxy request

PLACEHOLDERS ONLY

Package usernameCountryRegionCityASNSession IDTTL, seconds

cURLCopy command

curl --proxy 'http://package-elite-country-us:{proxy_password}@proxy.your-domain.example:8000' 'https://api.ipify.org?format=json'

Keep credentials server-side.Never embed a proxy password in frontend code or a public repository.

For API-driven catalog discovery, see catalog and proxy generation. For the provider-selection order and the explicit no-fallback rule, see routing and failure behavior.