Skip to main content
POST /v1/org/shipments/imports/file
The same published structure, delivered as a file — for nightly extracts and larger volumes, or simply because a file is what your system already produces. One row per goods line. Repeat the shipment columns on each line of a multi-line shipment and keep those lines together. Column order does not matter and optional columns may be omitted.
Start from shipments-template.csv — the header row with a worked example, including a two-line shipment.

Authorization

string
required
Your organisation API key (dzk_live_…).

Form fields

file
required
.csv or .xlsx, up to 50 MB. The first row must be the header row.
string
Your own reference for this push. Defaults to the filename.

The header row is checked before anything is queued

A structure mistake is yours to fix, so you hear about it on the request rather than minutes later. The response names exactly what is wrong:
Once the header passes, the file is queued and every row is validated individually during the import — see Check an import.

Response

202 Accepted, the same shape as the JSON lane, except received is absent — the row count is not known until the file is parsed.

Errors