New endpoint for deleting sales orders
We have introduced an endpoint which allows you to delete sales order.
The reference for the endpoint can be found here API reference - Delete a sales order.
We have introduced an endpoint which allows you to delete sales order.
The reference for the endpoint can be found here API reference - Delete a sales order.
We have introduced tags
for sales orders.
tags
allows you to add and remove custom tags that are then filterable on your Shipmondo account.
The field is available on all response, as well as create and update methods. e.g. Create sales_order
We have introduced customer_number
on shipment responses.
customer_number
allows you to identify the shipping agreement used for the shipment(s).
The field is available on all response bodies representing shipments. e.g. List all shipments
Since we have introduced Sandbox enviroment, we have decided to deprecated test_mode
on the POST /shipments endpoint.
The date of removal of test_mode
is yet unknown, but we highly encourage you to stop using this parameter and use the Sandbox enviroment instead.
POST https://app.shipmondo.com/api/public/v3/shipments
{
"test_mode": true,
"product_code": "PN_MC",
...
}
POST https://sandbox.shipmondo.com/api/public/v3/shipments
{
"product_code": "PN_MC",
...
}
We have introduced a new field named internal_reference
on the parcel objects.
internal_reference
allows you to assign a reference to track and identify each parcel within your shipment.
You can specify this field in the request body when creating a shipment. It will be stored with the parcel object and accessible via the API.
internal_reference
will neither be displayed on any label nor be transmitted to the carrier.
We have introduced a new field called additional_reference
for shipments.
additional_reference
allows you to specify a secondary reference when creating a shipment.
This field is optional and can be used to provide additional information or identification for your shipment.
The additional_reference
field is introduced at every endpoint relevant to shipments.
For more details, please refer to the API Reference.
Note: Unlike
reference
,additional_reference
is not guaranteed to be printed on the label.
We have introduced a new parcel field called stackable
for shipments. As of now, this field is relevant for those booking DHL Freight Sweden shipments with the following product codes:
DHLFSE_EUC
DHLFSE_S
DHLFSE_PT
DHLFSE_EUL
DHLFSE_HD
DHLFSE_HDR
stackable
allows you to specify whether an individual parcel can be stacked, providing more flexibility and efficiency in handling your shipments. stackable
defaults to true
if not specified.
The stackable
field is introduced at every endpoint relevant to shipments.
For more details, please refer to the API documentation.
A new API endpoint has been introduced, enabling creation of shipment for specific a fulfillment.
The reference for the endpoint can be found here API reference - Fulfillment create shipment.
Carrier setup files now include a new field, service_point_product
, which indicates whether a product is a service point product or not.
Read the full guide on how to retrieve and use the carrier setup file here.
A new API endpoint has been introduced, enabling users to retrieve a comprehensive file containing the full list of your available carriers, products and services.
For detailed instructions on how to access and utilize the carrier setup file, refer to the guide: Retrieve and use the carrier setup file.