Skip to content
English
Go to shippypro.com
  • There are no suggestions because the search field is empty.

How to connect Dachser to ShippyPro

Discover here how to connect Dachser in just a few steps.

Let's see how you can connect Dachser to ShippyPro in just a few steps.

 

Summary

  1. Before you start

  2. Connection steps

  3. Supported services

  4. Additional options

  5. Troubleshooting & errors

 

1. Before you start

 

To connect the carrier, you must first ask your Dachser Sales Person for credentials such as the API Token.

Before attempting to connect Dachser to ShippyPro make sure that you have an active subscription with both TRANSPORTORDER and SHIPMENTHISTORY APIs.

 

2. Connection steps

 

Then you can insert the credentials on the Carriers page, by clicking on the Dachser logo.

3. Supported services

 

Service

  • Targospeed > Express service.

  • Targospeed 10 > Premium express service with delivery by 10 AM the next day.

  • Targospeed 12 > Premium express service with delivery by 12 PM the next day.

  • Targospeed Plus > Extended express service with delivery beyond regular business hours.

  • Targoflex > Economy service designed for shipments that don't require express delivery.

  • Classic Line > Standard delivery service.

Terms of service

  • Ex works

  • Free delivered

  • Ex works including delivery against invoice

  • Free border; uncleared excluding duty & tax

  • Free delivered; uncleared excluding duty & tax

  • Free delivered; cleared excluding duty & tax

  • Free delivered; cleared including duty, excluding tax

  • Free delivered; cleared including duty & tax

  • Free delivered; insured, uncleared, excluding duty & tax

  • Service goods, insured; only by arrangement with the consolidator

 

4. Additional options

 

Besides your credentials, you'll also see some further options, let's take a look at them!

 

  • Goods Group
    You can ship pallets via Dachser service by adding them as Goods Group as following:

    GG = 10 for goods transported with packaging type “EU” (Euro pallet)
    GG = 11 for goods transported with packaging type “PA” (Parcel/Packet)

  • Label Type gives you the possibility to choose the correct label format for your printer.

  • Manual closeout: shipments are sent to Dachser only when you perform the Close work day from the Orders page 
  • POD: available in the ‘My Documents’ section

  • If you want, you can also enter a Custom Label to recognize the connection among all the others.

WARNING: There is no Test Endpoint (Test Mode), but if the carrier has provided you with test credentials, you can use them on the production endpoint. Make sure to replace them with production credentials once the carrier has activated the production Token.

 

5. Troubleshooting & Errors


Internal Server Error


The Dachser server is currently unavailable. Please try generating the labels again in a few minutes.

Terms: are incorrect (invalid or not assigned)

The Term of Service you selected in the carrier configuration is not valid for your shipment. Go to Carriers click edit on your Dachser connection and change Terms of service option.

If you are connecting the carrier for the first time and receive the error "Unable to validate credentials with the carrier," verify that the API Token entered is correct and that it has been activated by the carrier. A correct but inactive API Token will return a credentials error.

Why do I get HTTP 401 Unauthorized with an active production token?

Does saving your Dachser connection fail even though your production token is active? Here's one authorization issue to check.

In an investigated case, the carrier connection-validation logs showed a request to /rest/v2/shipmenthistory returning HTTP 401 Unauthorized. Dachser confirmed that a token subscribed only to TransportOrder does not authorize access to Shipmenthistory.

To address this missing authorization:

  1. Log in to the DACHSER API portal.
  2. Subscribe to the Shipmenthistory API.

📌 Note: An active production token may still lack authorization for an API. This is different from an invalid or inactive token. A missing Shipmenthistory subscription is one possible cause of HTTP 401 Unauthorized, not the cause of every 401 response.

Can I get the carrier API request JSON for Dachser?

ShippyPro Support can share its carrier API calls only directly with the carrier. If Dachser requests the API request JSON or carrier connection logs, contact our Support Team and provide the email address of a direct Dachser contact requesting them.

If, during your initial shipments, you encounter the error "An error occurred while processing the request. Please try again later," check with your contact to ensure that the API Token is active in production (not just in test mode). The carrier typically activates test mode first for preliminary testing before switching the Token to production mode.

 

Why is the "Address 2" field always empty?

Please note that the carrier does not support the Address 2 field, so any information entered in that field is not transmitted.

We recommend using Automation to format the recipient's address data instead. For more information, see the article "Automation – Use Cases and Templates."