IP geolocation API

Return the estimated location associated with an IP address.

Compare it with a supplied address to review city, country and distance differences where available.

Part of: Affiliate fraud detection Source audit

Try it free See a sample response From £0.008 per request, down to £0.0015 at volume.

What it checks

You send an IP address, usually the one a form or order was submitted from. Provero returns the estimated location associated with that connection: country, region, city, postcode area and coordinates.

Add the address or postcode the customer gave you and enable geoMatch, and the response also says whether the IP's city and country match that address and how far apart the two locations are. Use it to spot submissions that come from somewhere unexpected, such as a lead form completed from another country, so they can be reviewed.

The location is an estimate for the connection, not the position of a person or device. Mobile networks, corporate networks and VPNs can route traffic through a location some distance from the user. IP geolocation does not check whether a postal address exists. For that, use UK address validation (PAF) or UK address lookup (PAF).

What it returns

  • Estimated location

    Country, region, city and postcode area associated with the IP address.

  • Coordinates

    Latitude and longitude for the estimated location.

  • Country and city match

    With an address and geoMatch enabled, whether the IP's country and city match those of the supplied address.

  • Distance

    With an address and geoMatch enabled, the distance between the IP's estimated location and the supplied address, in kilometres and miles.

Distance and match results are returned only when an address is supplied with geoMatch enabled. When they are missing, the comparison was not made, which is not the same as a mismatch.

When to use it

  • Lead quality review

    Flag leads submitted from a country or region you do not expect, without automatically rejecting them.

  • Checkout and sign-up

    Compare the connection's estimated location with the billing or delivery address and route large differences to review.

  • Fraud screening

    Add location context to a risk review alongside IP fraud detection and your own signals.

  • Historical analysis

    Upload a file of IP addresses to see where past submissions were estimated to come from.

See how IP checks expose fake affiliate leads

How to read the result

Result What it indicates What to consider
City and country match What it indicates: The connection's estimated location agrees with the supplied address. What to consider: Treat it as consistent. It does not confirm who submitted the form or that they are at that address.
Country matches, city differs What it indicates: The estimated location is elsewhere in the same country. What to consider: Check the distance. Mobile networks and nearby towns often produce a short distance, which is usually low concern on its own.
Large distance or different country What it indicates: The connection appears to come from somewhere well away from the supplied address. What to consider: Weigh it with your other signals and the value of the action. Travel, roaming, corporate networks and VPNs all produce legitimate mismatches.
VPN or proxy connection What it indicates: The location reflects where the VPN or proxy connects to the internet, not where the user is. What to consider: Use IP fraud detection to identify anonymised connections, so you know when the location is unlikely to describe the user.
No match or distance returned What it indicates: The comparison was not requested or the address could not be resolved. What to consider: Treat the comparison as unknown, not as a mismatch.

A match is consistency between two pieces of information. Use it as one input to your rules or review, not as confirmation of the customer or of a precise location.

API & bulk usage

Call the API at the point of submission with the IP the request came from, or upload a file of IP addresses through the bulk uploader to review existing records.

  • ip is required.
  • To compare locations, send address (an address or postcode) and set geoMatch to true. An address that cannot be resolved returns a validation error rather than a mismatch.
  • To run IP geolocation with other checks in one call, use Multi-validation with a geoip block.

Example request and response

POST https://api.provero.io/api/fraud-check/geoip

Request

{
  "ip": "198.51.100.7",
  "address": "LS1 4AP",
  "geoMatch": true
}

Response

{
  "country": "United Kingdom",
  "regionName": "England",
  "city": "Manchester",
  "zip": "M1",
  "lat": "53.4808",
  "lon": "-2.2426",
  "ip": "198.51.100.7",
  "distance": {
    "km": 58.2,
    "mi": 36.2
  },
  "geoMatch": {
    "country": true,
    "city": false
  }
}

Illustrative example using a documentation IP address and an example Leeds postcode. The values are not a real result. Here the country matches and the city does not, with the estimated location around 58 km away: a difference to weigh, not a failure.

View the IP geolocation API documentation

Pricing

IP geolocation starts at £0.008 per request and reduces to £0.0015 at volume.

View tiers
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

Paid from a prepaid balance that you can spend across any check. See current rates.

Need volume pricing? Email pricing@provero.io.

Related checks

No single check settles whether a record can be trusted. These are the ones people usually run alongside IP geolocation, each answering a different question about the same record.

See every Provero check →

IP geolocation FAQ

How accurate is IP geolocation?

It is an estimate of where the connection reaches the internet, based on IP location data. It is not the location of a person or device. Read city and distance results as indications rather than precise positions.

How does address comparison work?

Send the address or postcode the customer supplied and set geoMatch to true. The response then includes whether the IP's country and city match that address and the distance between the two locations in kilometres and miles.

What if no match or distance is returned?

The comparison was not made, for example because no address was supplied or geoMatch was not enabled. Treat it as unknown, not as a mismatch. An address that cannot be resolved returns a validation error.

How do VPNs affect the result?

When someone connects through a VPN or proxy, the location reflects the VPN or proxy server, not the user. IP fraud detection flags VPN, proxy and Tor connections, which helps you decide how much weight to give the location.

Is this the same as address validation?

No. IP geolocation estimates where a connection is located. UK address validation (PAF) checks and standardises a postal address against Royal Mail data, and UK address lookup (PAF) helps someone select their address from a postcode.

How much does IP geolocation cost?

It starts at £0.008 per request and reduces to £0.0015 at volume on a prepaid, graduated balance. Free account registration includes credits so you can test it with your own data.

Start with this check

Create a free account, claim your credits and run IP geolocation through the API or bulk upload. No card required.

Sign up free