Integration

DACHSER integration

DACHSER is a European road freight and contract logistics provider. Its customer APIs track shipments (current status and full event history), fetch proof of delivery, freight costs and quotations, create, label, send and delete forwarding (transport) orders, generate labels, SSCC codes and routing codes, and read warehouse stock, delivery order status, delivery notes and incoming goods documents. Each API is a separate subscription on the DACHSER API portal, approved by DACHSER for existing customers, with per-API daily call limits; a test token cannot send orders. Authentication is an API token from the DACHSER API portal, sent in the X-API-Key header.

Connect DACHSER How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DACHSER.Built from the 19 DACHSER tools below, on the connection you add once.

What you can do with DACHSER

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Transport order, 5 operations

create_transport_orderCreate transport orderPOSTCreates a forwarding order in a basket: imported (editable, no label), labelled (labels returned) or sent (order transferred to DACHSER for real, billed freight). Returns the order id, state, labels and SSCCs.
delete_transport_orderDelete transport orderDELETEDeletes a forwarding order that has not yet been sent to DACHSER. Irreversible.
list_transport_ordersList transport ordersGETLists your forwarding (transport) orders, optionally between two dates, with id, state, transport date, weight and parties.
list_transport_orders_by_basketList transport orders by basketGETLists your forwarding orders in one basket (imported, labelled or sent), optionally between two dates.
send_transport_orderSend transport orderPOSTSends a forwarding order to the DACHSER transport system for real (billed transport): it can no longer be modified. Labels are returned for an order from the imported basket. Not allowed with a test token.

Label, 2 operations

create_shipping_labelCreate shipping labelPOSTGenerates DACHSER shipping labels (PDF or ZPL, base64) for a shipment, with the SSCC codes used and the routing relation. Labels must accompany an EDI order carrying the same SSCCs.
get_transport_order_labelsGet transport order labelsPOSTGenerates and returns the labels of a forwarding order (PDF or ZPL, base64). After labels are generated the order normally cannot be modified in eLogistics.

Shipment, 2 operations

get_shipment_historyGet shipment historyGETReturns every status event (full Track and Trace history) of the shipments matching a tracking number. At most 50 shipments, last 180 days. For only the latest status use get_shipment_status.
get_shipment_statusGet shipment statusGETReturns the current transport status (Track and Trace) of the shipments matching a tracking number: shipment ids, references, parties and the latest status event. At most 50 shipments, last 180 days.

Delivery note, 1 operation

list_delivery_notesList delivery notesGETReturns the digitised delivery notes produced by the DACHSER warehouse system for delivery orders matching a reference or a date. At most 50 documents, last 400 days; file contents come base64 encoded.

Delivery order, 1 operation

list_delivery_order_statusList delivery order statusGETFor contract logistics (warehouse) customers: returns the current status of warehouse delivery orders matching a reference, a delivery order date or a date plus status. Last 90 days, at most 500 orders.

Freight cost, 1 operation

get_freight_costsGet freight costsGETReturns the net freight costs invoiced for one consignment, found by tracking number. Last 365 days; no result when the consignment has several invoices.

Incoming goods document, 1 operation

list_incoming_goods_documentsList incoming goods documentsGETReturns the digitised documents of warehouse inbound deliveries (supplier delivery notes and related papers) matching a reference or a date. At most 100 documents, last 180 days.

Proof of delivery, 1 operation

get_proof_of_deliveryGet proof of deliveryGETReturns the proof of delivery documents (signed delivery papers) of shipments matching a tracking number, each file base64 encoded. At most 50 shipments, last 180 days.

Quotation, 1 operation

create_quotationCreate quotationPOSTCalculates the road freight cost of a transport order from your tariff (or DACHSER standard conditions): total amount and costs per service type, VAT excluded. Creates no order.

Routing, 1 operation

get_routingGet routingGETReturns the routing of a consignee destination: the 4-digit long distance relation (LDR) code and country, needed on labels for pallets handled in DACHSER Eurohubs.

Sscc, 1 operation

generate_ssccsGenerate ssccsPOSTIssues new unique SSCC codes (serial shipping container codes) from your agreed DACHSER SSCC number range. Each call consumes codes from that range. Requires an agreement with your DACHSER branch.

Stock, 1 operation

list_stockList stockGETReturns current warehouse stock of articles. Filters must be cumulative: article-number with product-variant, then optionally lot, best-before-date, blocking-reason and variable-classification, in that order.

Transfer list, 1 operation

get_transfer_listsGet transfer listsGETReturns the transfer lists (lists of shipments per consolidator) of the forwarding orders of one order date.

Use DACHSER from Claude Code, Cursor or Codex

Connect DACHSER in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DACHSER operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect DACHSER

Create your workspace
Sign up free. Nothing to install.
Connect DACHSER once
Add your DACHSER connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.