...
Can be accessed with a GET against this end point: https://ws.di.no/ws/json/addressCheck/v-2/fetch/{uuid} where {uuid} is the uuid that you got from the submit.
There is also a V3 of the fetch that can be access on https://ws.di.no/ws/json/addressCheck/v-3/fetch/{uuid} In V3 the sortkey field have slightly different content.
FetchAddressCheckRequest
Field | Description | Example | Data type | Size | Count |
---|---|---|---|---|---|
uuid | Unique identifier for the processing unit, obtained in the response for the SUBMIT (SubmitAddressCheckV2) action. | 388f70cd-3e0c-4be6-a51a-35f32e7e96d9 | UUID (String) | 36 | 1 |
...
Field | Description | Example | Data type | Size | Count |
---|---|---|---|---|---|
referenceId | Customer identifier. Must be unique within the customerSystem. | String | 37 | 1 | |
date | Estimated distribution date by carrier. | 2016-06-01 | Date (YYYY-MM-DD) | 10 | 1 |
supportedByCarrier | Whether the customer address is covered by carrier. | true | Boolean | 4 | 5 | 1 |
geoLocation | Describes the geographical area. Current values are 1, 2 and 3. | 1 | Integer | 1 | 0 - 1 |
authority | Who produced this information | ||||
company | Name of the qualifying distribution company. | SDØ | String | <= 5 | 0 - 1 |
routeNr | Route number of the covering route. | 21618 | String | 10 | 0 - 1 |
routeName | |||||
addrSeq | Address sequence defining sorting on the associated route. | 51 | Integer | 3 | 0 - 1 |
deliveryPointId | Numeric identifier for the delivery point found for the customer address. Typically fed back into the source system to speed up subsequent processes, for instance parcel creation. | 6734687 | Integer | - | 0 - 1 |
transport | Main car number. | 8500 | Integer | - | 0 - 1 |
subTransport | Sub car name, if any. | Some name. | String | - | 0 - 1 |
location | Name / address of the pick-up point. | Rostedsgate 8 | varchar | 60 | 0 - 1 |
locationDirections | Directions associated with the pick-up point. | Free text. | varchar | 60 | 0 - 1 |
sortKey | Key that can be used to sort the addresses in the sequence they should be packaged. Key will contain several geographical parts and sorting terms:
"%05d%05d%05d%05d%05d%05d%07d%05d" In the V3 version the string consists of these fields:
| 003001234500123401230001212345671234512345 | Integer | 42 | 0 - 1 |
linkedAddress | - | - | ? | ||
transportDescription | A string that describes the transport information, on the format: XXXX-yy/ZZZZ-øø-grenbil1 x025117x500 XXXX - Main car number on the pre transport transport ZZZZ - Main car number grenbil1 - Name of subcar x025117 - x + Routenumber | XXXX-yy/ZZZZ-øø-grenbil1 x025117x500 | String | 36 | 0 - 1 |
...