Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

FetchAddressCheckRequest

FieldDescriptionExampleData typeSizeCount
uuidUnique identifier for the processing unit, obtained in the response for the SUBMIT (SubmitAddressCheckV2) action.388f70cd-3e0c-4be6-a51a-35f32e7e96d9UUID (String)361

 

FetchAddressCheckResponse

Field
Description
Example
Data typeSize
Count
uuid

Unique identifier for the processing unit, obtained in the response for the SUBMIT (SubmitAddressCheckV2) action.

388f70cd-3e0c-4be6-a51a-35f32e7e96d9

UUID (String)361
nextAction

Describes what the client should do next:

  • STOP : stop sending more requests for this UUID to the service
  • REPEAT : send a new request with this UUID to get updated information

STOP

String4 | 61
status

Describes the current status of the unit.

Processing statesResult statesError states

QUEUED

COMPLETED

 

REJECTED_BUSY

INPROGRESS

 

 

FAILED
 

COMPLETED_RESENT

 

INVALID_UUID
  EXCEEDED_MAX_PROCESSING_TIME

Terminal statuses are all result states and error states.
They have the nextAction field set to STOP, which means that the client should stop sending requests to the service with that UUID.

See more detailed descriptions of the states below.

INPROGRESS

String6 - 281
secondsDelay

A hint from the server that may be provided if the server known when the status of the unit is likely to change. Defaults to two minutes.

The client should also ensure reasonable min, max and default values for the delay on their end.

120Integer 1
productProduct name for the unit.

AFM

String101
customerSystemName of the customer system for the unit.

AFT

String51
batchIdClient-side identifier for the unit (may be empty). String-1
addressCoverage

Describes a customer, whether his/her address is supported, and gives transport information if supported.
See detailed description of the addressCoverage entity below.

Whether there are zero or more address coverage items depends on the nextAction field.
If it is STOP there will be as many items as received when the batch was submitted through SubmitAddressCheckV2.
If it is REPEAT there will be zero  address coverage items.

 --0 - 10'000

 

State descriptions

Note that all statues except QUEUED and INPROGRESS are terminal. If the client receives a terminal response, new further requests should be sent to the service for the given UUID.

QUEUED

This processing states means that the batch has been received by service, and it is waiting to be processed.

INPROGRESS

This processing states means that the batch has been received by the service and is currently being processed.

COMPLETED

This terminal result state means that the batch has been processed and that the results are included in the response.

COMPLETED_RESENT

This terminal result state means that the batch has been processed, that the results have been sent already at least once. The results are included in the response. The previous result state was COMPLETED.

This can take place as long as the batch hasn't expired. If the batch has expired, the service will return INVALID_UUID.

REJECTED_BUSY

This terminal error state means that the system is overloaded, and that the processing queue is full. Try again later.

FAILED

This terminal error state means that an error casued the batch processing to fail. Try the request again, check your input data, and if the error persists, contact DI.

INVALID_UUID

This terminal error state means that the system has no knowledge about the UUID in the request.

EXCEEDED_MAX_PROCESSING_TIME

This terminal error state means that the system spent too much time to process the batch. This may be caused by high load on the system. Try again later, or split the batch into smaller batches.

AddressCoverage

Field
Description
Example
Data typeSize
Count
ReferenceId

Customer identifier. Must be unique within the customerSystem.

 String371
DateEstimated distribution date by carrier.2016-06-01Date (YYYY-MM-DD)101
SupportedByCarrier

Whether the customer address is covered by carrier.

true

Boolean4 | 51
GeoLocationDescribes the geographical area.   0 - 1
CompanyName of the qualifying distribution company.

SDØ

String<= 50 - 1
transportMain car number.8500Integer-0 - 1
subTransportSub car name, if any.Some name.String-0 -1
routeNoRoute number of the covering route.21618String100 - 1
addrSeqAddress sequence defining sorting on the associated route.51Integer30 - 1
SortKey

Key that can be used to sort the addresses in the sequence they should be packaged. Key will contain several geographical parts like SortingLocation,

Distribution Company, Transport, Route, Address sequence. The exact format will be defined at a later stage.

003001234500123401234TBDTBD

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.

6734687Integer-0 - 1
locationName / address of the pick-up point.Rostedsgate 8varchar600 - 1
locationDirectionsDirections associated with the pick-up point.Free text.varchar600 -1
linkedAddress  --?

linkedAddress

Field
Description
Example
Data typeSize
Count
countryCodeThe country of the address.

NO

String21
postalNameCity / place of the address.

Oslo

String<= 301
zipCodeZip code of the address.2500, 186 (leading zeros are stripped, this is postal code "0186" in Norway)Integer51
address

Customer address.

This can include street, house number, entrance and appartment number.

Christian Krohgs gate 54String<= 601

...