Start booking shipments for shop orders asynchronously.
Request body data for Book shipment
Request payload for booking shipments for shop orders asynchronously. Contains shop identifiers, order references, shipping configuration, and email notification settings.
shipping service group from which to load the shipping services to use.
e-Mail address to which the results will be sent.
Muliple e-mail addresses can be specified by separating them with a comma.
ID of the shop from which the order data can be retrieved.
list of order identifiers for which the shipments need to get booked.
At least one order identifier needs to be specified.
Duplicate or empty order identifiers are not allowed.
1 - 2147483647 elementsThe weight of the packaging material used in kg.
Should not contain the weight of the shipment's content (eg: products).
x > 0A unique identifier for the request.
Used for tracing and to prevent duplicate shipment bookings.
This value is optional, if not included, a random requestUUID is generated.
A human readable reference for the request.
This will be included in the mail that is sent once the operation completes.
This value is optional, if not included, a random reference will be generated.
The
Optional length (in meters) of the shipment.
x > 0Optional width (in meters) of the shipment.
x > 0Optional height (in meters) of the shipment.
x > 0The height of the packaging material used in m.
Value is rounded to three decimal places.
x > 0The width of the packaging material used in m.
Value is rounded to three decimal places.
x > 0The length of the packaging material used in m.
Value is rounded to three decimal places.
x > 0Optional weight of the shipment's content in kg.
Should not contain the weight of the packaging material.
Use this field with care and in rare cases only, as it overrides the default weight calculation, which is based on the ordered product's weight.
Using this field can cause inconsistencies with the customs declaration and could result in errors during shipment booking.
x > 0If set to true, the fulfillment data (tracking number and provider) are transmitted to the shop system after the label was created.
If set to true, the shipment recipient's e-mail address is not transmitted to the carrier.
This means that the carrier is not able to contact the recipient of the shipment by e-mail.
Bad request - the request payload is invalid, missing required fields, or contains invalid data.