Geo Source Selection

Every geo-targeting parameter you send — country, region, city, ASN, ISP, zipcode — is resolved by looking the IP up in a geolocation database. Which database that is makes a real difference: providers disagree about where a given IP sits and which network owns it, so the same _city-london filter can select a different set of IPs depending on the source used to answer it.

The _geosource- parameter lets you choose. Evomi resolves geo filters against ipapi unless you say otherwise, and additional sources can be added over time without changing how the parameter works.

Available Geo Sources

More sources may be added to this table in future. Until then, _geosource- accepts only the values above.

Implementation

Append _geosource-<value> to your proxy password, alongside the geo filters it should apply to:

http://testuser:[email protected]:1000

The parameter only changes how filters are resolved — it never selects a location on its own. Sent without any geo filter present, it has no effect.

Examples

curl -x http://testuser:[email protected]:1000 https://ip.evomi.com/s

curl -x http://testuser:[email protected]:1000 https://ip.evomi.com/s

import requests

proxies = {
"http": "http://testuser:testpassword_country-US_region-california_geosource-maxmind@rp.evomi.com:1000",
}
response = requests.get("https://ip.evomi.com/s", proxies=proxies)
print(response.text)

const fetch = require('node-fetch');

const proxyUrl = 'http://testuser:[email protected]:1000';
const url = 'https://ip.evomi.com/s';

fetch(url, { proxy: proxyUrl })
.then(res => res.text())
.then(body => console.log(body));

Affected Parameters

Every geo filter is resolved by the selected source:

Any other parameter — sessions, _fraudscore-, _device-, _latency-, protocol options — is unaffected and behaves exactly as documented on its own page.

Product Availability

Unlike the other expert settings, this parameter is available on all three rotating proxy products. Only the endpoint changes:

# Datacenter
curl -x http://testuser:[email protected]:2000 https://ip.evomi.com/s

# Mobile
curl -x http://testuser:[email protected]:3000 https://ip.evomi.com/s

Unrecognised Values

An unrecognised source name is ignored rather than rejected: the request succeeds and is served from the default source, exactly as if you had omitted the parameter.

Values are case-sensitive and must be lowercase, so _geosource-MAXMIND is not recognised and silently resolves against ipapi. Writing _geosource-ipapi explicitly is valid and identical to omitting the parameter.

If a request behaves as though the parameter were absent, check the spelling and casing of the value against the table above first.

Common Use Cases

• Matching the geolocation your own verification or analytics stack reports
• Cross-checking a location that two sources disagree on
• Targeting an ISP or ASN as a specific source attributes it
• Compliance checks that name a particular geolocation dataset as the reference