Shipping Orders
CRUD operations for shipping orders
List of Shipping Orders
Returns list of created shipping orders. In addition to the data you sent, shipping orders contain additional attributes such as shippingNumber and shipmentTracking.
query Parameters
createdFromStart of date range, format yyyy-MM-ddTHH:mm:ss
createdToEnd of date range, format yyyy-MM-ddTHH:mm:ss
referenceNumbersFilter shipping orders by reference number, you can specify multiple values
idsFilter shipping orders by ID, you can specify multiple values
shippingNumbersFilter shipping orders by shipping number, you can specify multiple values
statusFilter shipping orders by shipping status, you can specify multiple values
courierID of courier
courierProfileID of courier configuration
pagePage number, cannot be less than 1
pageSizeNumber of items per page, cannot be less than 1 and greater than 50
List of Shipping Orders › Responses
Successful response
pageCurrent page number
pageSizeNumber of items per page
totalPagesTotal number of pages
nextPageIndicates if there is a next page
previousPageIndicates if there is a previous page
itemsCountTotal number of items
Array of result items
Shipping Order
Returns shipping order by ID. In addition to the data you sent, shipping order contains additional attributes such as shippingNumber and shipmentTracking.
path Parameters
idID of shipping order
Shipping Order › Responses
Successful response
idID of shipping order
referenceNumberReference number of shipping order
externalReferenceExternal reference
referenceSourceSource of data
sourceIdentifierSource identifier
courierID of courier
courierProfileID of courier profile
shippingNumberShipping numbers returned by courier
createdDate and time when shipping order was created (format yyyy-MM-ddTHH:mm:ss)
codPriceCreate Shipping Order(s)
The request is used for the creation of new shipping order(s) in the courier system. After successful execution, shipping numbers are returned, which can be used to retrieve the shipping label.
The request can end with failure. There are two types of failure:
- Validation problem: Returns 400 Bad Request with validation response, same as in the validation request
- Courier API failure: Returns 200 OK with failure details in the
failedattribute
- For single shipping order creation, use Content-Type: application/cham.shipping-order+json
- For multiple shipping orders creation, use Content-Type: application/cham.shipping-orders+json
If a shipping order with the same reference number already exists, the previous shipping order will be removed.
Source attribution: every shipping order is recorded under a ReferenceSource + SourceIdentifier pair, which defaults to api / default. Set both fields to attribute an order to one of your connected sources instead — notification triggers, statistics and order-state synchronization back to your e-shop or ERP are keyed on that pair. The pair is also part of the identity used by the duplicate-replacement rule above, so an order created under a different pair does not replace an existing one with the same reference number.
Note that if duplicate-order prevention is enabled on your API key, that separate check matches on the reference number alone and ignores the source pair — it will reject a reference number already used under a different source.
path Parameters
courier_idID of courier
query Parameters
profileID of configuration
Create Shipping Order(s) › Request Body
ReferenceNumberUnique value that identify entity in the application Chameleoon
ExternalReferenceReference that identify entity in your system
ReferenceSourceOptional. System the shipment is attributed to. Defaults to api when omitted, empty or blank, so existing integrations that never send this field are unaffected. Notification triggers, statistics attribution and order-state synchronization back to your e-shop or ERP are keyed on the ReferenceSource + SourceIdentifier pair, so set it when you want a shipment routed as if it originated in one of your connected systems. Use the identifier of a source connected to your account (see GET /configurations/sources).
The pair is validated against the sources activated on your account (see GET /configurations/sources); a pair that matches none of them is rejected with 422. The values must match the configured source and profile ids exactly, casing included. The pair api / default is always accepted.
ReferenceSource and SourceIdentifier must be supplied together — send both or neither.
SourceIdentifierOptional. Identifier of the concrete instance of ReferenceSource, used to distinguish several instances of the same source (for example two e-shops on the same platform). Defaults to default when omitted, empty or blank.
ReferenceSource and SourceIdentifier must be supplied together — send both or neither.
Create Shipping Order(s) › Responses
Shipping order creation completed (can include both successful and failed items)