Search by ID

You may have noticed that every destination comes with an id field. This is a unique ID for every address. You can also search by this. You could, for example, keep a list of favourite addresses.

Use Case

While you may not cache Naurt addresses or locations for any lengths of time, but you are allowed to cache Naurt IDs for as long as you like. You may also associate them with your own IDs or your own addresses or your own locations.

For example, if you have a customer who has input and saved an address, you may cache the Naurt ID and save it with that customer. Then, when that customer orders again later, you can use the Naurt ID to search for a faster and guaranteed result.

Examples

The example section shows the final JSONs which can be placed into the request queries list. It should be noted that a single request can contain multiple different kinds of quries.

{
    "id": "c56dbebb-c7ab-ede2-a7ac-f84e57d1878d"
}

Restrictions

id is incompatible with all other search properties, which to review, is

• location
• address_string
• address_structured
• country
• additional_matches