APIs

0
No votes yet

shipmentstatus (REST API) (2.0.1)

The web service shipmentstatus provides the latest status information about one or several shipments. The request could be done on a customer order number, a DACHSER consignment number, House Bill of Lading, House AirWay Bill, Container number or shipping container codes (SSCC).

The shipment status is provided for the last 90 days. Furthermore within one request the status for a maximum of 50 shipments is given.

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

0
No votes yet

stock (REST API) (2.0.2)

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.

0
No votes yet

label (REST API) (2.0.3)

The web service label provides full labels (in PDF or ZPL) to the customers i.e including SSCC (using the web service sscc) and the long distance relation (LDR) (using the web service routing).

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

0
No votes yet

sscc (REST API) (2.0.4)

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.

The service is consumed by customers to set up an EDI connection without having their own GLN and therefore are not able to generate SSCC’s. As valid SSCC's are mandatory 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.

0
No votes yet

routing (REST API) (2.0.4)

The web service routing provides 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 maximum of 1000 calls per day.

0
No votes yet

deliveryorderstatus (REST API) (2.0.2)

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 transport shipments please use the transport related API shipmentstatus.

0
No votes yet

deliverynotes (REST API) (2.1.1)

The web service deliverynotes provides the customers the digitalised delivery note generated by MIKADO (DACHSER’s WMS)

Therefore the searching criteria are dedicated references or by date.

The search is done only on the last 35 days and a maximum of 50 documents are sent back.

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

0
No votes yet

incominggoodsdocuments (REST API) (2.1.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.

The search is done only on the last 35 days and a maximum of 100 documents are sent back.

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

0
No votes yet

pod (REST API) (2.0.3)

The web service pod provides digitised prove 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 request could be done by customer order number, the DACHSER consignment number, House Bill of Lading, House AirWay Bill, Container number or SSCC (bar codes)

The search is done only on the last 35 days and a maximum of 50 documents are sent back.

Please note for the plan free you will be limited to 3 calls per minute and a maximum of 10 calls per day, whilst with the plan full you will be limited to 1 call per second and a maximum of 1000 calls per day (here an agreement between the customer and the Dachser branch has to be established).

0
No votes yet

shipmenthistory (REST API) (2.0.1)

The web service shipmenthistory provides all statuses (delivery events) about one or several shipments. The request could be done by customer order number, the DACHSER consignment number, House Bill of Lading, House AirWay Bill, Container number or SSCC (bar codes).

The shipment history status is provided for the last 90 days. Furthermore within one request the history status for a maximum of 50 shipments is given.

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

DACHSER's 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

Placeholder

Warehouse

Placeholder