We have introduced an endpoint which allows you to void payment associated with a sales order.

The endpoint accept an amount parameter that specifies the desired amount to void. If no amount is supplied the authorized amount will be used.

The full reference for the endpoint can be found here API reference - Void payment.

We have introduced an endpoint which allows you to refund payment associated with a sales order.

The endpoint accept an amount parameter that specifies the desired amount to refund. If no amount is supplied the full captured amount will be refunded.

The full reference for the endpoint can be found here API reference - Refund payment.

To support the new parties and customs fields introduced in Shipmondo, File integration on the Print Client has been updated accordingly.

These updates align with the recent changes to the Shipments API.

For details about the new and deprecated fields, please refer to the Changelog: Shipments - Parties and customs.

The updates to File integration apply to both JSON and XML files.

Effective Date: January 15, 2026

On January 15, 2026, we're releasing an update to Shipmondo's Shopify app that introduces a new format for shipping method codes. This change enables advanced shipping configurations for webshops while providing partners with better access to shipping method details via our API.

What's changing?​

New shipping method code format​

The Shipmondo app stores delivery information in the code field of shipping_lines in Shopify orders. We're transitioning from the existing format to a new, more flexible format.

Current format:

dk_gls_service_point_95433
dk_dao_service_point_1250
dk_dao_private

New format:

SHIPMONDO;{method_id};{pickup_point_id}

Example:

SHIPMONDO;12345;95433

Where:

• SHIPMONDO = prefix for unique identification of the source
• method_id = unique ID for a shipping method created in the Shipmondo app (e.g., 12345)
• pickup_point_id = ID for the pickup/service point (optional, depends on the shipping method, e.g., 95433)

In a greater effort to improve customs in Shipmondo, a number of fields have been introduced to shipments:

• parties array
• pickup_details object
• delivery_details object
• service_point_id string
• customs > freight_cost float
• customs > insurance_cost float

At the same time a number of fields have been deprecated:

• sender object
• receiver object
• pick_up object
• bill_to object
• service_point object
• return_to object
• customs > billed_to_custom_invoice_text string
• customs > sender_custom_invoice_text string
• customs > receiver_custom_invoice_text string

There are no current plan to remove these fields, but it is recommended to stop using them from now on, as new features will only be added to parties.

Guides​

Check out the new guide for parties for further details of the structure of parties.

Also check out the new guide for migration to parties from the deprecated address objects.

Also check out the updated API reference for reference of the structure of each new field.

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 environment, 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 environment instead.

Example​

Before​

POST https://app.shipmondo.com/api/public/v3/shipments

{
  "test_mode": true,
  "product_code": "PN_MC",
  ...
}

After​

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.