Fetches the results for the specified address check request.
...
In version `v4` of the fetch endpoint, the following data is added to the `v3` version if such information exists:
Field | Description | Example | Data type | Size | Count |
|---|---|---|---|---|---|
| handoverLocationId | Customer-specific id associated with the handover location. | 123456 | String | 0 - 1 | |
| handoverLocationCity | The city of the handover location. | OSLO | String | 0 - 1 | |
| handoverLocationZipCode | The zip code of the handover location. | 383 | Integer | 1 - 5 | 0 - 1 |
| handoverLocationStreetName | The street name of the handover location. | My Street | String | 0 - 1 | |
| handoverLocationStreetNumber | The street number of the handover location. | 61 | Integer | 0 - 1 | |
| handoverLocationDescription | A free-text description of the handover location. | String | 0 - 1 |
linkedAddress
Field | Description | Example | Data type | Size | Count |
|---|---|---|---|---|---|
| countryCode | The country of the address. | NO | String | 2 | 1 |
| postalName | City / place of the address. | Oslo | String | <= 30 | 1 |
| zipCode | Zip code of the address. | 2500, 186 (leading zeros are stripped, this is postal code "0186" in Norway) | Integer | 5 | 1 |
| address | Customer address. This can include street, house number, entrance and appartment number. | Christian Krohgs gate 54 | String | <= 60 | 1 |
The field supportedByCarrier determines whether the fields with count 0 - 1 will be present (true) or not, except for when skipRouteCheck has been set to true. In that case, there will be no route information even though supportedByCarrier may be true but deliveryPointId may be set to aid troubleshooting.
%05d%010d%010d%010d%05d