Versions Compared

Key

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

...

Depending on the current state, the service may return the results or a status indicating what is happening or what happened with the request.

FetchAddressCheckRequest

FieldDescriptionExampleCount
uuidUnique identifier for the processing unit, obtained in the response for the SUBMIT (SubmitAddressCheckV1) action.388f70cd-3e0c-4be6-a51a-35f32e7e96d91

 

FetchAddressCheckResponse

Field
Description
Example
Count
uuid

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

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

1
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

1
status

Describes the current status of the unit.

Processing statesResult statesError states

QUEUED

COMPLETED

 

REJECTED_BUSY

INPROGRESS

COMPLETED_PARTIAL

 

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

1
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 shuld provide reasonable min, max and default values for the delay.

1201
productProduct name for the unit.

AFM

1
customerSystemName of the customer system for the unit.

AFT

1
batchIdClient-side identifier for the unit (may be empty). 1
skipRouteCheckWhether the route check was performed or not for the customer addreses in the unit.false1
requireExactMatchWhether an exact match on a customer address was required to mark it as supported.false1
transportDateThe transport date used by the system to obtain the address coverage results. Format is yyyy-mm-dd.2015-12-211
deliveryDateThe delivery date used by the system to obtain the address coverage results. Format is yyyy-mm-dd.2015-12-211
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 SubmitAddressCheckV1.
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.

...

This terminal result state means that the batch has been processed and that the partial results are included in the response. Partial means that one or more processing units (authorities, or source systems, ) were unavailable and/or timed out. This means that the items associated with that unit all have supportedByCarrier unconditionally set to false.

...

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.

...

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
Count
customerId

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

 

1
supportedByCarrier

Whether the customer address is covered by carrier.

true

1
authority

The authority / source system that made the decision about the customer address being supported by carrier or not.

The value NOT_PROCESSED indicates that the item for some reason wasn't processed by any authority (due to an error state). These will have supportedByCarrier unconditially set to false.

DI

1
companyName of the qualifying distribution company.

MANU

0 - 1
terminalTerminal name, if any.MALAP0 -1
transport
What is this precisely?8500
Main car number.8500 Some name0 - 1
subTransportSub car name, if any.Some name.0 -1
rotueNoRoute number of the covering route.5234430 - 1
routeName

Name of covering route.

Keskusta 201 0 - 1
addrSeqAddress sequence defining sorting on the associated route.510 - 1
locationWhat is this precisely?Patamäenkatu 9
deliveryPointIdNumeric 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.67346870 - 1
locationName / address of the pick-up point.Patamäenkatu 90 - 1
locationDirectionsDirections associated with the pick-up point.Free text.0 -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.

Files

View file
nameFetchAddressCheckV1.xsd
height250
View file
nameFetchAddressCheckV1.wsdl
height250