Skip to main content
POST
Dispatch and Manifest Orders
When a carrier rejects a batch as a whole, Nash doesn’t leave every order in it stranded. Each delivery is noted as resubmitted individually and sent again one shipment at a time, so a single shipment the carrier won’t take — a bad receiver contact, an instruction it can’t parse — fails alone. Each such failure is its own entry in errors[], with the order’s identifier and orderId, stage: "manifest", and the carrier’s own message, while manifests[].delivery_ids lists only the shipments that were accepted. A shipment that fails stays dispatched and untagged, so a later call retries it once you’ve fixed the order. If nothing in the batch gets through, the original batch error is returned. The single-purpose Manifest Orders call keeps its all-or-nothing behavior.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Create, dispatch, and manifest orders in a single request.

orders
ManifestOrderInput · object[]
required

Orders to create, dispatch, and manifest.

Response

OK

manifests
ManifestResultSerializer · object[]
required

Manifest results for orders that successfully created, dispatched, and manifested.

errors
ManifestOrderErrorSerializer · object[]

Per-order failures encountered during create, dispatch, validate, or manifest.