IP Geolocation API

Check they are where they say they are, resolve an IP and match it to the address they gave you.

Try it free from £0.008 per request, down to £0.0015 at volume

What it checks

IP Geolocation resolves an IP address to a physical location, city, region, country and coordinates, and, when you supply an address, tells you whether the two agree. The standout signal is geoMatch: a direct comparison of the IP's location against the address the user entered, including whether the city and country match and how far apart they are. It answers a simple but powerful question: does where they're connecting from line up with where they claim to be?

What it returns

  • City / region / country / zip , the resolved location of the IP
  • Latitude / longitude , coordinates for the resolved location
  • geoMatch, country match , whether the IP country matches the submitted address country
  • geoMatch, city match , whether the IP city matches the submitted address city
  • Distance , how far the IP location is from the submitted address, in km and miles

When to use it

  • At checkout or sign-up, to flag a mismatch between the billing/shipping address and where the user is actually connecting from.
  • In fraud screening, where a large distance between IP and stated address is a useful risk signal.
  • To tailor experience by location, for example currency, language or regional content.
  • Alongside IP fraud detection, to add a where check on top of the proxy/VPN/abuse signals.

When not to use it

  • As pinpoint tracking, IP geolocation is approximate (typically city-level), not a precise address, so judge by distance bands rather than exact coordinates.
  • As a hard block on mismatch alone, travel, mobile networks and VPNs all create legitimate mismatches; weigh it with other signals.
  • When the user is on a VPN or proxy, the resolved location reflects the exit node, not the person; pair it with IP fraud detection to detect that.
  • For offline records with no originating IP, this check needs the IP the submission came from.

How to read the result

Read the geoMatch and distance together, a mismatch is a signal to weigh, not an automatic failure.

City and country match
The connection lines up with the stated address. A reassuring, low-risk signal.
Country match, city differs (short distance)
Common and usually benign, mobile networks and nearby towns. Low concern on its own.
Large distance / country mismatch
A stronger risk signal. Worth weighing against the value of the action and your other checks.
VPN / proxy suspected
The location reflects the VPN exit, not the user. Combine with IP fraud detection before drawing conclusions.

Pricing

from £0.008 per request, down to £0.0015 at volume

Requests / month Rate
0 – 5,000 £0.008
5,001 – 10,000 £0.005
10,001 – 25,000 £0.0045
25,001 – 50,000 £0.004
50,001 – 100,000 £0.003
100,001 – 200,000 £0.0025
200,001 – 500,000 £0.002
500,001+ £0.0015

Prepaid balance, spent across any check. Each request is charged at the rate for the volume band reached, and earlier requests keep their lower rate. See full pricing.

Need custom pricing? pricing@provero.io

API & bulk usage

Run IP Geolocation in real time at the point of submission, or in bulk to analyse where historical records connected from. Call it on its own, or combine it with other checks in a single request and get every signal back in one response.

Read the API reference →

Request

{
  "geoip": {
    "ip": "8.8.8.8",
    "address": "Sheffield",
    "geoMatch": true
  }
}

Response

{
  "geoip": {
    "ip": "8.8.8.8",
    "country": "United Kingdom",
    "regionName": "England",
    "city": "Sheffield",
    "zip": "S6 3AF",
    "lat": 53.3811,
    "lon": -1.4701,
    "geoMatch": {
      "country": true,
      "city": true
    }
  }
}
Common Questions

IP Geolocation FAQ

What is geoMatch?

geoMatch compares the location of the IP against an address you submit, telling you whether the city and country match and how far apart they are. It's the quickest way to spot a 'where they connect from' versus 'where they say they are' mismatch.

How accurate is IP geolocation?

It's approximate, typically city-level, so it's best read as a distance band rather than a precise pin. That's why the distance value and geoMatch flags are more useful than raw coordinates.

Will a VPN throw it off?

Yes, the resolved location reflects the VPN's exit node, not the user. Combine IP Geolocation with IP Fraud Detection to detect the VPN and interpret the location accordingly.

Should a mismatch block a transaction?

Not on its own. Travel and mobile networks create legitimate mismatches. Use the distance and match flags as one signal alongside your other checks and the value of the action.

How much does IP geolocation cost?

It starts at £0.008 per request and steps down to £0.0015 at volume on a prepaid, graduated balance, with free credits to run a real sample of your own data through every check.

Start with this check

Create a free account, claim your credits and run IP Geolocation as a real-time API or a bulk upload. No card required.

Sign up free