Get Started

Last updated: May 2nd, 2018

How does IPlocation work?

IPlocation uses API's from a variaty of diffect IP location database services. The data from these services gets pulled in trough a variaty of formats. The data is cleaned and checked and served in the same data format nomatter what source the data came from. All these sources are then checked, compared and combined to provide the most accurate information.

Usage and data format

Perform a simple HTTP(S) request

To use IPlocation you can simple do a HTTP(S) request. You can use IPlocation to search within all the available API's, but you can also use a specific API service for your request.

HTTP(S) request examples:

https://iplocation.hnjameindersma.net/ip/123.456.789.01

https://iplocation.hnjameindersma.net/service/db-ip.com/123.456.789.01

A XML response is send back

If everything went successfull in the back you should receive a XML response. This response has a set format and give you all the results from the various API's.

Combined API request
  • The root is 'locator'
  • The complex element 'location_request' contains basic information about the request made
    • 'ipaddress', the IP address of which a lookup is requested
    • 'timestamp', the time and date when the request was received by the server
    • 'request_server', the IP address of the server who is responding to your request and handling the API connections
    • 'request_client', the IP address of the client who made the request
  • The complex element 'location_results' contains the various API results
    • The complex element 'location_result' contains one API result, with the IP address as attribute 'ip' and the requested API resource as attribute 'api'
      • 'country', the compared projected country of the IP address, with ISO2 country code as attribute 'code', if available (for both)
      • 'region', the compared projected region of the IP address, with ISO2 region code as attribute 'code', if available (for both)
      • 'city', the compared projected city of the IP address, if available
      • 'zip_code', the compared projected ZIP code of the IP address, if available
      • 'latitude', the compared projected latitude of the IP address, if available
      • 'longitude', the compared projected longitude of the IP address, if available
      • 'time_zone', the compared projected time zone of the IP address, if available
      • 'isp', the compared projected ISP (Internet Service Provider) of the IP address, if available
  • The complex element 'location_compared' is the final result after all the API results are compared to eachother, with the IP address as attribute 'ip'
    • 'country', the compared projected country of the IP address, with ISO2 country code as attribute 'code'
    • 'region', the compared projected region of the IP address, with ISO2 region code as attribute 'code'
    • 'city', the compared projected city of the IP address
    • 'zip_code', the compared projected ZIP code of the IP address
    • 'latitude', the compared projected latitude of the IP address
    • 'longitude', the compared projected longitude of the IP address
    • 'time_zone', the compared projected time zone of the IP address
    • 'isp', the compared projected ISP (Internet Service Provider) of the IP address
Requesting a specific API
  • The root is 'locator'
  • The complex element 'location_request' contains basic information about the request made
    • 'ipaddress', the IP address of which a lookup is requested
    • 'timestamp', the time and date when the request was received by the server
    • 'request_server', the IP address of the server who is responding to your request and handling the API connections
    • 'request_client', the IP address of the client who made the request
  • The complex element 'location_results' contains the various API results
    • The complex element 'location_result' contains one API result, with the IP address as attribute 'ip' and the requested API resource as attribute 'api'
      • 'country', the compared projected country of the IP address, with ISO2 country code as attribute 'code', if available (for both)
      • 'region', the compared projected region of the IP address, with ISO2 region code as attribute 'code', if available (for both)
      • 'city', the compared projected city of the IP address, if available
      • 'zip_code', the compared projected ZIP code of the IP address, if available
      • 'latitude', the compared projected latitude of the IP address, if available
      • 'longitude', the compared projected longitude of the IP address, if available
      • 'time_zone', the compared projected time zone of the IP address, if available
      • 'isp', the compared projected ISP (Internet Service Provider) of the IP address, if available

Process the data however you like

You can now process these results further however you like. However, please keep in mind that all request preformed to API's from this service are from a single source, and thus some API's may reach there daily limit. It is therefor not permitted to use this service in an automated high volume production.