Retrieve available geo-locations
Return targeting options for a proxy service plan. Management REST on monitor.geonode.com (Basic Auth).
Auth
HTTP Basic Auth with your Geonode account username and password (dashboard login user, not the full -type-residential proxy string unless that is your account username).
curl -u "<username>:<password>" \
"https://monitor.geonode.com/services/<SERVICE>/targeting-options"Service path values
| Service path | Description |
|---|---|
RESIDENTIAL-PREMIUM | Premium residential |
ROTATING-DATACENTER | Rotating datacenter |
UNLIMITED-RESIDENTIAL | Unlimited residential |
Example
curl -u "<username>:<password>" \
"https://monitor.geonode.com/services/RESIDENTIAL-PREMIUM/targeting-options"Response
HTTP 200. Top-level object:
| Field | Type | Description |
|---|---|---|
countries | array | List of country objects |
Each country object:
| Field | Type | Description |
|---|---|---|
code | string | Country code (lowercase in response, e.g. us) |
name | string | Country name |
asns | array | { "code": "7922", "name": "AS7922 ..." } |
states | array | States; each may include nested cities |
Cities are nested under states (not a top-level cities.prefix object). Example: the catalog can include 200+ countries; a large country like the US may expose many ASNs and states, with cities nested under each state.
{
"countries": [
{
"code": "us",
"name": "United States",
"asns": [
{ "code": "3", "name": "AS3 Massachusetts Institute of Technology" }
],
"states": [
{
"code": "alabama",
"name": "Alabama",
"cities": [
{ "code": "birmingham", "name": "Birmingham" }
]
}
]
}
]
}Use these code values with connection username flags (-country-US, -state-alabama, -city-birmingham, -asn-7922). See Geo targeting.
Was this page helpful?