Trackings/Orders
Our powerful API integration allows you to submit each individual parcel and order, get instant feedback, and have the most flexible data structures.
Create or Update a Tracking/Order
Create a new order record with shipment and recipient data.
Account to which this order belongs
Order number (customer facing)
Retailer reference (e.g. internal system ID) for this order, unique.
Name of the technical client / shop (corresponds to the system setup), e.g. 'mybrand-a.com'
Destination country ISO 3166-1 alpha 3 code
ISO 639-1 language code of the recipient, if known, required for localized communication
Delivery method (e.g. 'standard shipping'), needs to be set up in the system
Recipient email address, must be provided, in case email is not known or should be unset, use the literal string '_unset' instead.
Recipient name
Customer number (e.g. from the retailer)
Invoice number (e.g. from the retailer)
Payment method (e.g. 'credit card')
Total amount of the order (usually after tax & discount)
^-?\d{0,8}(?:\.\d{0,2})?$Tax amount of the original order
^-?\d{0,8}(?:\.\d{0,2})?$Net amount of the order (usually before tax)
^-?\d{0,8}(?:\.\d{0,2})?$Discount amount of the order
^-?\d{0,8}(?:\.\d{0,2})?$Currency of the order, e.g. USD, EUR (ISO 4217)
Payment details (for future use)
Date and time when the order was placed
Channel through which the order was placed (e.g. 'webshop')
Announced delivery date
Announced delivery date range of order (min)
Announced delivery date range of order (min)
Timezone of the recipient, if known, not required, but strongly recommended
Current status of the order, as setup in the system
Indicates this order has been split into multiple shipments
Datetime when the order was cancelled
Reason for cancellation
customer- Customerinventory- Inventorypayment- Payment-relatedother- Other
customer- Customerinventory- Inventorypayment- Payment-relatedother- Other
Tags for the object, format :e.g. 'category:Home Apparel'
No response body
No content
Create a Tracking/Order
Create a new order record with shipment and recipient data.
Account to which this order belongs
Order number (customer facing)
Retailer reference (e.g. internal system ID) for this order, unique.
Name of the technical client / shop (corresponds to the system setup), e.g. 'mybrand-a.com'
Destination country ISO 3166-1 alpha 3 code
ISO 639-1 language code of the recipient, if known, required for localized communication
Delivery method (e.g. 'standard shipping'), needs to be set up in the system
Recipient email address, must be provided, in case email is not known or should be unset, use the literal string '_unset' instead.
Recipient name
Customer number (e.g. from the retailer)
Invoice number (e.g. from the retailer)
Payment method (e.g. 'credit card')
Total amount of the order (usually after tax & discount)
^-?\d{0,8}(?:\.\d{0,2})?$Tax amount of the original order
^-?\d{0,8}(?:\.\d{0,2})?$Net amount of the order (usually before tax)
^-?\d{0,8}(?:\.\d{0,2})?$Discount amount of the order
^-?\d{0,8}(?:\.\d{0,2})?$Currency of the order, e.g. USD, EUR (ISO 4217)
Payment details (for future use)
Date and time when the order was placed
Channel through which the order was placed (e.g. 'webshop')
Announced delivery date
Announced delivery date range of order (min)
Announced delivery date range of order (min)
Timezone of the recipient, if known, not required, but strongly recommended
Current status of the order, as setup in the system
Indicates this order has been split into multiple shipments
Datetime when the order was cancelled
Reason for cancellation
customer- Customerinventory- Inventorypayment- Payment-relatedother- Other
customer- Customerinventory- Inventorypayment- Payment-relatedother- Other
Tags for the object, format :e.g. 'category:Home Apparel'
Retrieve All Orders
The pagination cursor value.
Which field to use when ordering the results.
Retrieve Orders by ID
^(?!info)[^/.]+$Payload
Data ModelCredentials
Code Samples
Last updated
Was this helpful?