Carts & orders

Changing carts or validating them requires WRITE (Authentication & scopes). GET on carts and orders works with READ.

Carts and order_id

A cart is still an order in Fleet’s model. That is why endpoints use order_id even before checkout, and why create-cart returns an order_id.

Line items and catalog

Each cart line references a catalog product, a delivery country, and optional fields such as assignee, shipping address, and keyboard layout (when required).

Acquisition mode

Orders distinguish leasing vs one-time purchase (BUY). Leasing is the default unless you override it.

Patching a cart

You can change purchaser, replace line items, or adjust acquisition mode. At least one of those dimensions must be present in a patch.

Validate

Validate is the transition from cart to order lifecycle. It closes the “draft cart” phase and starts order processing in Fleet.
At this step you provide the purchaser and optional signatory, and the API checks that the order is ready to move forward.

Orders after checkout

List orders returns a paginated summary. Get order returns a richer read model for one order.

Next steps

• Catalog — choosing products and layouts before building lines.
• Devices — how hardware on validated orders ties to device records.
• API reference — Carts and Orders tags for concrete requests and responses.