Authorizations
Generate a JWT access token through a Custom Global Integration and provide it with each request in the Authorization
header prefixed with "Bearer" and then a single space.
Path Parameters
The id
of the referenced Shipment
.
x >= 1
Body
Optional request parameters for packing, labeling, and printing operations.
Describes each package and its contents.
If true, completes the packing process.
This includes creating a shipping label (if applicable) and marking the shipment as 'Packed'.
Required to be true
if return_label
or print_label
is true
and no existing label exists.
true
Whether to return the generated shipping labels in the response as base64-encoded PDF data.
Requires complete_packing
to be true
or an existing shipping label to be present.
Labels are returned in the response under the labels
key.
false
Whether to send the generated labels to the specified printers.
Requires complete_packing
to be true
or an existing shipping label to be present.
Must specify appropriate printer parameters based on shipment type.
false
Specifies the printers to be used. The required printers depend on the shipment contents and type when print_label
is true.
small_label
is required for printing SSCC labels when the print target is configured for small labels.label
is required for parcel shipping labels or for SSCC labels when the print target is configured for standard labels.laser
is required for freight shipments, hazmat shipments, or other documents like customs forms and bills of lading.
URL to send shipment data to after successful packing operation. Must be a valid HTTP or HTTPS URL. Shipment data including ID, tracking info, and package data will be transmitted to this URL via an HTTP POST request synchronously. Any 200 response will be considered a success. Any non-200 response will be considered an error, and the request body will be truncated to 255 characters and displayed to the user and added as a history comment to the order.
The JSON-encoded payload contains the following keys: shipment_id
, external_id
, order_unique_id
, order_ref
, carrier_code
, shipping_method
, batch_tag
, automation_data
, website_code
, store_code
, shipment_weight
, shipment_weight_unit
, order_weight
, order_weight_unit
, is_international
, is_documents_required
, and stock_id
.
"https://automation.example.com/shipment/packed"
Packing solution override parameters for manual or automatic solution adjustment. Used to specify alternative packing solutions or create new ones.
Whether to mark the current packing solution as invalid/disabled.
When true
, disables the current solution after packing is complete.
Cannot be used in combination with other solution override parameters.
false
ID of the initial packing solution to set on the shipment before processing. Used to establish a baseline solution before applying any overrides.
54321
Whether to pack the shipment in offline mode without carrier API integration.
When true
, skips carrier API calls and address validation.
Useful for situations where carrier services are unavailable.
false
Object mapping instruction IDs to quantities for order instructions that have been confirmed. Keys are instruction IDs (as strings), values are the quantities confirmed. Used to record fulfillment of special order instructions during packing.
{ "123": 2, "456": 1 }
Response
Shipment packed successfully
Any warnings generated during the packing process
["Address validation warning"]
Base64-encoded PDF labels (returned only when return_label
is true
).
Available keys depend on shipment type and requirements.
Status messages about printing operations (returned only when print_label
is true
)
[
"Labels have been sent to the label printer (label-printer-01).",
"Customs Documents have been sent to the laser printer (laser-printer-01)."
]