get sales order
One order and everything hanging off it: its lines with what has been fulfilled and returned, what each line holds and where, the fulfilment requests sent to a warehouse, the shipments, returns and invoices against it, its open exceptions, and the booking it was born from. ship_to is served here and on no list or export, because an address is the document's and not the page's.
cancellation_receipt is the immutable original cancellation: version, actor (nullable), reason (nullable), recorded_at, previous_lifecycle and lifecycle. Null means no receipt was recorded; never infer the cancelling actor from the creator.
after_ship says what followed the shipment and what is next, null until the order ships: shipment (the latest truck; state is typed, reported or no_cartons), shipping_notice (the 856; not_sent, queued, sent or refused, with the network's reason where refused), invoice (the latest invoice not voided, or null; books.state is not_connected, pending, posted or refused and network.state the 810's, each with its reason where refused) and next_act (pack_cartons, send_shipping_notice, invoice, retry or none). Its facts are the same ones shipments and invoices carry.
Scope: orders:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/sales/orders/{order_id}
- Auth: HTTP bearer
Path parameters
The order's id.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The order.
Changes
No recorded changes to this operation across all 1 revision of this API.