Skip to content
Naurt Docs

ID Lookups

Tutorial

As discussed in the Quickstart, there are plenty of ways to access Naurt data. These examples will guide you through each way you can look up specific IDs with Naurt. Before continuing, make sure you have your free API key from the Naurt Dashboard.

ID Lookup

Section titled “ID Lookup”

An ID Lookup is the fastest and most accurate way to use Naurt. Each address in the Naurt database is associated with our own unique ID. While you are not allowed to cache addresses or locations returned by the API, you are permitted to cache Naurt IDs for as long as you like. Therefore, looking up addresses again can be extremely fast the second time.

  1. Configure a POST request to the final-destination endpoint with the following headers.

    Terminal window
    https://api.naurt.net/final-destination/v2
    Authorization: <API-KEY-HERE>
    Content-Type: application/json

  2. Configure your JSON payload with an id

    {
      "queries":[
        {
          "id": "8bd197aa-7328-3e10-9ea7-7ec139e9fa48"
        }
      ]
    }

This type of request does not support any other parameters within the query.

Source ID Lookup

Section titled “Source ID Lookup”

Naurt uses third party data to source complete address strings. Those address sources usually have their own IDs (which, to be clear, are completely separate from Naurt’s own ID system). Some of the underlying datasets have their IDs exposed for search too, which can be a great way to search if you already use those.

At the moment, we only support searching by an Ordnance Survey UPRN or Royal Mail PAF UDPRN. If you are already using an Ordnance Survey address product, or have access to UPRN/UDPRN numbers in any way, this can be a very convenient way to quickly search.

Please note that Ordnance Survey UPRN/Royal Mail PAF UDPRN numbers are only available to search in Great Britain.

  1. Configure a POST request to the final-destination endpoint with the following headers.

    Terminal window
    https://api.naurt.net/final-destination/v2
    Authorization: <API-KEY-HERE>
    Content-Type: application/json

  2. Configure your JSON payload with a source_id object.

    {
      "queries":[
        {
          "source_id": {
            "os_uprn": "200001191298"
          }
        }
      ]
    }
    {
      "queries":[
        {
          "source_id": {
            "os_udprn": "17594066"
          }
        }
      ]
    }