---
title: "get sales order"
method: GET
path: "/api/v1/sales/orders/{order_id}"
tags: ["orders"]
---

# get sales order

`GET /api/v1/sales/orders/{order_id}`

## Request

- Base URL: `https://api.app.tightly.io`
- URL: `https://api.app.tightly.io/api/v1/sales/orders/{order_id}`
- Auth: HTTP bearer

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`.

## Path parameters

- `order_id` string, required

## Headers

- `Tightly-Version` string

## Response `200`

The order.

- object
  - `data` object: The order, its lines and the documents against it.
  - `message` object: severity, service and desc.

## Other responses

- `401`: No usable key: malformed, unknown, revoked, expired or stopped.
- `403`: The key does not hold Orders (`scope_missing`), or is issued to one account and the record is not that account's (`account_mismatch`).
- `404`: No order with that id is on file.
- `429`: The key has spent its allowance for this minute. 600 reads and 120 writes a minute, counted per key, refused calls included. `Retry-After` says how long to wait.
- `503`: The database is briefly out of reach, which is what a failover or a full connection pool looks like from outside. Wait the seconds `Retry-After` names and send the request again. A read is safe to repeat. A write is not, because the connection was lost in the middle of it, so read the object back before sending it a second time. Branch on the status rather than on `code`, which is `POSTGRES_UNAVAILABLE` from one of the two seams that raise this and `SERVICE_UNAVAILABLE` from the other.

---

[API](https://skmtc.dev/tightly/apis/tightly-api.md) · [All operations](https://skmtc.dev/tightly/apis/tightly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/tightly/apis/tightly-api/revisions/199f7eb35afb?raw)