The validateShipment call provides the advantage of validating shipment data _before _a createShipment call will persist a shipment in the database.

📘

• There is no general answer, what the validateShipment call will check beforehand.
• It is also good to know that the validateShipment will not be successful for all carriers. When the validateShipment call does not check anything or is not implemented yet, the response will be "The carrier does not support carrier-specific route validations."

Pre-validation

Pre-validation checks, if the shipment with the given carrier, service, and consignee (postal code and country validation) will succeed when it comes to label printing.

🚧

What's not included in the pre-validation

In most cases, package data influences checks as well e.g. package weight, dimensions, or quantity reglementation. The same applies to shipment items which are required for hazardous goods or shipping to third country. This will not be checked in the pre-validation. However, successful routing for the selected addresses and services will provide a useful indication to the carrier.

Request parameters

The important parameter in the request is the validation mode. The different modes must be separated by | if more than one mode wants to be used, at the same time. Valid values are:

{
  "validationParms": {
    "validationMode": "ROUTE_SERVED|SERVICE_COMPLIANT"
  }
}

<validationParms>
   <validationMode>ROUTE_SERVED|SERVICE_COMPLIANT</validationMode>
</validationParms>

Potential validation results and their reasons

For the response, there are several possible scenarios.