13 posts tagged with "API"

Four new optional attributes entries are now supported on shipments booked with DACHSER products. They are declared through the existing attributes arrays:

• order_group (shipment level) - free text.
• goods_group and goods_group_quantity (parcel level) - these two belong together. If only one of them is given on a parcel, the shipment is rejected with an error naming the missing field.
• pallet_places (parcel level) - accepts up to two decimals (e.g. 0.25 for a quarter pallet). Values are summed across all parcels and sent to DACHSER as a single number. If no parcel declares the attribute, nothing is sent - so declare 0 explicitly if you want to report zero pallet places.

{
  ...
  "attributes": [
    {
      "name": "order_group",
      "value": "A"
    }
  ],
  "parcels": [
    {
      "weight": 250000,
      "attributes": [
        { "name": "goods_group", "value": "B" },
        { "name": "goods_group_quantity", "value": "2" },
        { "name": "pallet_places", "value": "1.5" }
      ]
    }
  ],
  ...
}

DACHSER expects specific values in goods_group and order_group - agree these with DACHSER, as Shipmondo does not validate them.

Find the full specification in our Shipments API reference.

We have introduced two new endpoints that allows you to hold (pause) and unhold (resume) sales orders.

• PUT /sales_orders/:sales_order_id/hold
• PUT /sales_orders/:sales_order_id/unhold

We have introduced two new endpoints:

• GET /statistics/invoices — aggregated statistics for your invoices and credit notes, e.g. spend by category, and net/VAT/gross totals.
• GET /user_ledger_entries — your account statement: individual balance movements (refills, charges) with a running balance.

See the API reference for /statistics/invoices, and here for /user_ledger_entries.

The EU has introduced a requirement to provide product identifiers for goods imported into the EU. New attributes entries are now supported on objects in the customs.goods array, letting you declare them: m_pid (assigned by the seller or platform), ns_pid (a non-standardised manufacturer identifier) and s_pid (a standardised manufacturer identifier, such as an EAN or ISBN).

Product identifiers are accepted today for DHL Express, FedEx, UPS and unspecified-carrier shipments, with a couple of carrier-specific requirements. See Product identifiers (PID) for EU import for the full details.

You can now request a specific DPI for ZPL labels via a new optional label_dpi query parameter on GET /shipments/{id}/labels.

Supported Values​

• 200
• 300

If label_dpi differs from the shipment's saved label DPI, the label is converted on the fly. If it matches, the label is returned unchanged. This only applies to ZPL formats; other formats ignore the parameter.

For detailed information, see the Shipments API reference.

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.

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 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.