{"componentChunkName":"component---src-templates-simple-markdown-js","path":"/docs/direct-carrier-connections/dispatch/","matchPath":"","result":{"data":{"markdownRemark":{"html":"

Dispatch

\n

Dispatch tenders a shipment to a specific carrier — asking them to commit to picking it up and hauling it — and follows that booking through to delivery.

\n

How it works

\n

A dispatch request is typically created from a rate you've already received (or, directly from shipment details). Like rating, dispatch is asynchronous: creating a dispatch request returns immediately, and the carrier's confirmation, and the shipment's progress, arrive as the booking moves through its lifecycle.

\n

Endpoints

\n\n

Dispatch lifecycle

\n

A dispatch generally moves from being tendered, to confirmed by the carrier, to dispatched, in transit, and finally delivered. Not every shipment passes through every stage, and a dispatch can be cancelled or end in an error at various points along the way. See Statuses for the full list of dispatch statuses.

\n

The current status and the confirmed carrier appear on the shipment itself, along with pickup and delivery details for each stop:

\n

\"A

\n

Carrier response

\n

After a shipment is tendered, the carrier responds in one of three ways:

\n\n

You're notified as the carrier responds, so you can re-tender to another carrier if one declines or revokes. See Statuses for the full list of carrier response types.

\n

Cancelling a dispatch

\n

A dispatch can be cancelled while it's still in an eligible stage (for example, before pickup). Cancellation is not available for every carrier — see Supported Carriers.

\n

API reference

\n

Coming soon.

\n

Next steps

\n

Once a shipment is dispatched, track it in transit and request the eBOL and delivery documents as they become available.

","headings":[{"value":"Dispatch","depth":1},{"value":"How it works","depth":2},{"value":"Endpoints","depth":2},{"value":"Dispatch lifecycle","depth":2},{"value":"Carrier response","depth":2},{"value":"Cancelling a dispatch","depth":2},{"value":"API reference","depth":2},{"value":"Next steps","depth":2}]},"contentItem":{"data":{"lastModified":"2026-08-26T14:38:06.000Z","enableToc":null,"disableLastModified":null,"tocMaxDepth":null,"requestLogin":false}},"siteConfig":{"enableToc":true,"disableLastModified":false,"tocMaxDepth":4}},"pageContext":{"matchPath":"","id":"e3423fe5-bf34-54b4-b176-76282283fd96__redocly content/docs/direct-carrier-connections/dispatch/","seo":{"title":"Dispatch","description":null,"image":"","keywords":null,"jsonLd":null,"lang":null,"siteUrl":null},"pageId":"docs/direct-carrier-connections/dispatch.md","pageBaseUrl":"/docs/direct-carrier-connections/dispatch","type":"markdown","toc":{"enable":true,"maxDepth":4,"headings":[{"depth":1,"value":"Dispatch","id":"dispatch"},{"depth":2,"value":"How it works","id":"how-it-works"},{"depth":2,"value":"Endpoints","id":"endpoints"},{"depth":2,"value":"Dispatch lifecycle","id":"dispatch-lifecycle"},{"depth":2,"value":"Carrier response","id":"carrier-response"},{"depth":2,"value":"Cancelling a dispatch","id":"cancelling-a-dispatch"},{"depth":2,"value":"API reference","id":"api-reference"},{"depth":2,"value":"Next steps","id":"next-steps"}]},"data":{"title":"Dispatch"},"catalogInfo":null,"link":"/docs/direct-carrier-connections/dispatch/","sidebarName":"developerPortal","isLanding":false,"showPrevButton":null,"showNextButton":null,"apiVersions":null,"apiVersionId":null,"isDefaultApiVersion":null}},"staticQueryHashes":["1123603147","1302185487","1344209882","1398840060","1520077861","1975142765","2667623876","2950305614","3240152602","3743992808","561138138"]}