6 posts tagged with "API"

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 stucture of each new field.

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.

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.

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.

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.

We are introducing a series of updates to our API responses and requests, specifically targeting shipment payloads. These changes are aimed at improving data consistency and ensuring clearer documentation for developers. Here’s a breakdown of the changes you need to be aware of: