POST /v1/org/shipments/importsSending the same shipment twice is safe. A
shipmentId already in the ledger is
updated, not duplicated — its goods lines are replaced by the ones you send. Retries,
re-runs and corrected re-sends all do the right thing.Authorization
string
required
Your organisation API key (
dzk_live_…).Body
Shipment[]
required
1–100 shipments. See Shipment structure for every field.
Each shipment needs at least one entry in
items, at most 500, and the batch as a
whole may carry at most 10,000 goods lines — send bigger runs
as a file.string
Your own reference for this push — a batch id, run date or filename. It is echoed on
the import and recorded against every shipment it creates, so a shipment can be traced
back to the run that sent it.
Response
200 OK — the shipments are written.
created and updated both mean the shipment is in the ledger; only failed needs
action. Valid shipments are never held back because others in the batch were wrong.
There is no import id to poll: this response is the outcome. Your customer still sees the
submission in their Dyspach Activity Center, and your own sourceDetails is recorded
against every shipment, so a specific push can always be traced back later.

