API Library | DACHSER API Portal

-->> IMPORTANT INFORMATION ABOUT NEW DACHSER API GATEWAY << --

Dear API users,

In order to improve the quality of our services, we are changing the infrastructure of our API Gateway. All APIs are now available on the new gateway.

On February 2, 2023 the current gateway will be deactivated and therefore we ask you to migrate to the new one before this date, if not already done.

The migration consists of changing :

• The domain from "api.dachser.com" to "api-gateway.dachser.com"
• The header name "X-IBM-Client-Id" to "X-API-Key".

The API tokens are synchronized between the old and the new gateway.

If you encounter any problems afterwards, please contact our Service Desk at support@dachser.com.

DACHSERs API Library

Our API are made to simplify your business and improve our logistics services.
New API are regularly created, come back often and check our new offers.

The DACHSER API follow the REST/JSON paradigm as it offers more flexibility to the web service consumer.
You will find information and recommandations how to use the API as well as FAQ in the menu Support

Transport

freightcosts plan

2.11.0

The web service freightcosts provides the net costs that are invoiced for a specific consignment.

The search can be done by

Customer order number
DACHSER consignment number
Delivery Note Number
Purchase Order Number

Please note that

no result is returned if there are several invoices for one consignment. In this case, please contact the branch.
the costs can be provided for shipments of the last 365 days
for each API token the limits are 5 calls per second and a maximum of 1000 calls per day
you can use the API once you received the approval for your

freightcosts (REST API) 2.11.0

label plan

2.11.0

The web service label provides complete DACHSER labels to the customer [i.e including SSCC (using the web service sscc) and the long distance relation (LDR) (using the web service routing)]. It returns the labels in the requested format (PDF or ZPL) together with all generated SSCC and the LDR.

The labels are not self-sufficient and must be used in addition to an EDI where the sscc must be included.

Please note that for each API token the limits are 3 calls per second and a maximum of 3000 calls per day.

In order to subscribe to this plan you have to [create your account](

label (REST API) 2.11.0

pod plan

2.11.1

The web service pod provides digitised proof of deliveries. They are for instance the DACHSER digital proof of delivery or any paper documents (e.g. the shipper delivery notes, ...) signed by the consignee that have been digitalised and saved in the archive in relation to one shipment.

The search can be done by

Customer order number
DACHSER consignment number
Delivery Note Number
Purchase Order Number
SSCC (bar codes)

Please note that

only the first 50 shipments matching the criteria are returned.
the pod can be provided for shipments of the last 180 days.
the **plan

pod (REST API) 2.11.1

quotation plan

2.11.2

The web service quotation calculates the transport costs of one road transport order (distribution and procurement).

It needs to receive all information about the transport order ( consignor, consignee, term of delivery, weight, handling units, etc etc (please the API see description)).

The calculation is based on the transport order data you provided and on your personal tariff conditions with Dachser (if they exist) otherwise the DACHSER standard conditions will apply.

quotation will return both the total amount and the detailed costs (per service type) where VAT are not included.

quotation (REST API) 2.11.2

routing plan

2.11.0

The routing web service provides the routing information which includes the 4-digit code for the long distance relation (LDR) and the consignee country code. The routing information is used to identify the consignee destination.

It is mandatory for handling the pallets in the DACHSER Eurohubs and needs to be printed on the label by the customer in case of direct shipments to the Eurohub. Additionally it can be agreed bilaterally by the customer and its responsible DACHSER branch due to business process needs.

Please note that for each API token the limits are 3 calls per second and a

routing (REST API) 2.11.0

shipmenthistory plan

2.11.1

The web service shipmenthistory provides all statuses (delivery events) for one or several shipments.

The search can be done by

Customer order number
DACHSER consignment number
Delivery Note Number
Purchase Order Number
SSCC (bar codes)
House Bill of Lading (HB/L)
House AirWay Bill (HAWB)
Container number
Invoice Number
Batch Number
Packing List Number

Please note that

collection orders are not supported
only the first 50 shipments matching the criteria are returned
the shipment events can be provided for shipments of the last 180 days
for each API

shipmenthistory (REST API) 2.11.1

shipmentstatus plan

2.11.1

The web service shipmentstatus provides the current status information about one or several shipments.

The search can be done by

Customer order number
DACHSER consignment number
Delivery Note Number
Purchase Order Number
SSCC (bar codes)
House Bill of Lading (HB/L)
House AirWay Bill (HAWB)
Container number
Invoice Number
Batch Number
Packing List Number

Please note that

collection orders are not supported
only the first 50 shipments matching the criteria are returned
the shipment events can be provided for shipments of the last 180 days
for each API

shipmentstatus (REST API) 2.11.1

sscc plan

2.11.0

The web service sscc provides serial shipping container codes (SSCC) from a specific number range of the DACHSER SSCC pool. The issued numbers are unique and contain a valid check digit at the end. This service can be used by customers who want to set up an EDI connection without having their own GLN and therefore are not able to generate SSCC. As the provision of a valid SSCC is a prerequisite for an EDI interface with DACHSER this service opens up great opportunities.

Please note that for each API token the limits are 3 calls per second and a maximum of 500 calls per day.

sscc (REST API) 2.11.0

transportorder plan

2.11.5

The web service transportorder offers the possibility to create, label and send transportorders as well as to download the transfer list.

Create a forwarding order

The order is created only if all information are correct, otherwise all errors are returned in the API response.

In case of error, the information has to be corrected in the customer ERP system prior to ask again to "create" the forwarding order.

When the is no error you can proceed with the following functions:
Get the labels (in pdf or zpl format)
Send the order to DACHSER

This is the step to

transportorder (REST API) 2.11.5

Warehouse

deliverynotes plan

2.11.1

The web service deliverynotes provides customers with the digitised delivery notes generated by MIKADO (DACHSER’s WMS).

Therefore the searching criteria are dedicated references or by date and only the first 50 documents matching the criteria are returned.

The deliverynotes generated within the 400 days can be provided.

Please note that for each API token the limits are 1 call per second and a maximum of 1000 calls per day.

In order to subscribe to this plan you have to create your account. After logging in, please register an application[ (link)](

deliverynotes (REST API) 2.11.1

deliveryorderstatus plan

2.11.1

If you are a contract logistics customer the web service deliveryorderstatus provides current status information about one or several warehouse delivery orders. No historic status can be seen only the actual one. The request could be done on a reference, a delivery order date or combination date/status.

The search is done only on the last 90 days and a maximum of 500 delivery orders are sent back.

Please note that for each API token the limits are 5 calls per second and a maximum of 1000 calls per day.

NOTE: If you are interested in the status information about your

deliveryorderstatus (REST API) 2.11.1

incominggoodsdocuments plan

2.11.1

The web service incominggoodsdocuments provides the customers digitalised documents from the warehouse incoming goods process. These documents are typically the supplier delivery notes and all other corresponding papers that have been digitalised and saved in the archive in relation to one physical inbound.

Therefore the searching criteria are dedicated references or by date and only the first 100 documents matching the criteria are returned.

The documents archived within the last 180 days can be provided.

Please note that for each API token the limits are 1 call per second and a

incominggoodsdocuments (REST API) 2.11.1

stock plan

2.11.0

The web service stock provides current stock information about one or several articles at the moment when the request is raised. The request could be done on an article number, a variable classification or a blocking reason.

In case you need to implement stock comparison, this can be done via EDI. Please contact your DACHSER branch for more information.

Please note that for each API token the limits are 1 call per second and a maximum of 1000 calls per day.

In order to subscribe to this plan you have to create your account. After logging in, please

stock (REST API) 2.11.0