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
validateShipmentcall will check beforehand.
- It is also good to know that the
validateShipmentwill not be successful for all carriers. When the
validateShipmentcall does not check anything or is not implemented yet, the response will be "The carrier does not support carrier-specific route validations."
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.
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:
|Checks if a shipment can be sent to the consignee address with the specified carrier and service.
|Checks if the shipment data are in compliance with the carriers requirements.
For the response, there are several possible scenarios.
|No or invalid validation mode in the request.
|Master data problem of the carrier configuration or route is not valid.
|Required data is missing in the request.
|Carrier does not support validateShipment or it is not implemented yet.
|Validation was successful.
Updated 4 months ago