Get order by ID

Order UUID

Trading pair UUID

Order type: LIMIT or MARKET

Order side: BUY or SELL

Limit price (null for market orders)

Original order quantity

Quantity filled so far

Volume-weighted average fill price

Order status: SUBMITTED, PARTIALLY_FILLED, FILLED, CANCELLED, REJECTED, or EXPIRED

Trading mode: SPOT or MARGIN

Time in force: GTC, IOC, or FOK. Absent on MARKET orders, which have none.

Order creation timestamp (ISO 8601)

Last update timestamp (ISO 8601)

Order expiration date (ISO 8601)

Application (builder) taker fee this order paid, in quote token units, summed over the fills where it was the taker: each fill's fee as charged, rounded down to the quote token's smallest unit. A replacement order also includes the fills of the order it replaced. 0 on a liquidation order. An amount, not a rate.

Monaco protocol taker fee this order paid, in quote token units, summed over the fills where it was the taker: each fill's fee as charged, rounded down to the quote token's smallest unit. A replacement order also includes the fills of the order it replaced. A liquidation order carries the liquidation fee it was charged instead. An amount, not a rate.

Monaco maker fee on this order, in quote token units, summed over the fills where it was the maker; negative is a rebate credited to the maker. A replacement order also includes the fills of the order it replaced. An amount, not a rate.

Total taker fees charged in quote token (monaco_taker_fee + application_taker_fee)

Total amount paid by taker, in quote token units: the filled notional as the ledger booked it (each fill's price * qty, rounded down to the quote token's smallest unit) plus total_taker_fees. A replacement order also includes the fills of the order it replaced.

Total amount received by maker, in quote token units: the notional of its maker fills as the ledger booked it (each fill's price * qty, rounded down to the quote token's smallest unit) minus monaco_maker_rebate, so a rebate adds. A replacement order also includes the fills of the order it replaced.

Margin account UUID for margin orders

DEPRECATED derived compatibility value. Order side is authoritative.

Leverage for margin orders

Whether the order is reduce-only

Associated margin position UUID

Original order quantity in raw format (for precision)

Filled quantity in raw format (for precision)

Remaining unfilled quantity (normalized for display)

Remaining unfilled quantity in raw format (for precision)

Client-assigned correlation handle as stored: the value supplied on create or replace, with surrounding whitespace trimmed. Absent when the order carried none, including every order placed before the field was accepted on write. Uniqueness is enforced only among your orders that are RESTING on the book, so several of your orders may share one value over time and a lookup by it can be ambiguous: an order that never rests never takes the handle, and the value is released the moment any order reaches a terminal state. It is a correlation handle, not an idempotency key.

Timestamp when the order was cancelled (ISO 8601)

Timestamp when the order was fully filled (ISO 8601)

Timestamp when the order expired (ISO 8601)

Timestamp when the order was submitted (ISO 8601)

Timestamp when the order was acknowledged (ISO 8601)

Trigger price for stop/conditional orders

Quote volume of the order

Application UUID that created the order

Parent order UUID for linked orders

Batch UUID for batch orders

Stable terminal cause for a cancelled order: USER_REQUESTED, REPLACED, LIQUIDATION, INSUFFICIENT_MARGIN, REDUCE_ONLY_EXHAUSTED, POSITION_CLOSED, OCO_SIBLING_TRIGGERED, SELF_TRADE_PREVENTION, AUTO_DELEVERAGING, PRICE_BAND, SLIPPAGE_TOLERANCE, BANKRUPTCY_PRICE, CANCEL_ALL_AFTER, or SYSTEM. CANCEL_ALL_AFTER means your cancel-all-after timer ran out (POST /api/v1/orders/cancel-all-after). AUTO_DELEVERAGING means auto-deleveraging closed the position your risk bucket held and this resting order was cancelled with it; you were deleveraged as a counterparty, not liquidated. PRICE_BAND means the exchange's protective price band stopped the order and its remainder was cancelled, or, on a resting perp order, that the mark moved the order past the band, where no taker may trade with it; SLIPPAGE_TOLERANCE means your own slippageToleranceBps did. BANKRUPTCY_PRICE means a resting order was cancelled because filling it would have taken its risk bucket below zero equity in liquidation zero mode (its bankruptcy price).

Whether the order was placed post-only (maker-only). Absent for orders placed before the flag was persisted.

Opaque, compare-only revision counter for this order's state: the sequencer step that wrote it. A strictly higher value is strictly newer state for that order. The SAME counter is carried on every order WebSocket event and on the orders snapshot frame, so a reconnecting client reconciles on (id, version) — take the REST row when snapshot.version >= local.version, else keep local state. Note >=, not >: on the stream, equal versions mean the SAME STEP rather than identical state, because one step emits several events for one order (an OrderPlaced and then its fills) and a batch shares one step across every item. A REST row is that step's FINAL state, so it wins a tie. Between two REST reads the comparison is simpler — equal there does mean identical state. Do not read anything else into the number: it is not a count of updates, consecutive values are not expected (it is drawn from a global sequence shared by every order, so per-order values are sparse and gaps are normal), and it is not comparable across different orders. Absent means unknown: an order last written before this field existed. Fall back to a full field comparison for those rather than treating absent as version zero — and note that a comparison against an absent value is false in both directions, so an order held locally without one is never refreshed by the merge above; take the REST row unconditionally for those. Reconciling on this counter does NOT on its own close a reconnect gap: an order that filled or was cancelled while the socket was down appears in neither the resting snapshot nor the stream, so recover fills from getUserTrades (GET /api/v1/accounts/trades, newest first) and resolve anything your local state believes is resting that the snapshot no longer lists with a targeted getOrder. Unlike updatedAt, this value is identical on every REST endpoint that serves the same order state, and never advances without a state change.

The per-order self-trade-prevention override REQUESTED when this order was placed or replaced: CANCEL_MAKER, CANCEL_TAKER, CANCEL_BOTH, or SKIP. Absent when the order carried no override — including every order placed before the field was accepted on write — even though a wallet or platform default still governed its matching. This echoes the request, not the resolved default.

Present only on an order the engine placed for a take-profit or stop-loss trigger: the conditional order (GET /api/v1/orders/conditional/{conditionalOrderId}) that fired it. The reverse of ConditionalOrder.triggeredOrderId, so a close in order history can be attributed to the TP/SL that produced it without scanning the conditional list. Absent on every order a client placed itself, on TWAP slice children (those carry parentOrderId), and on triggered closes written before the field existed — there is no backfill, so a missing key on an older close means unknown, not placed by hand.

What placed the order: USER (the account itself, including its TP/SL triggers and TWAP slices), LIQUIDATION (the liquidation engine closing the account's position), ADL (an auto-deleveraging close), COPY (the copy trading engine mirroring a leader for one of the account's follows), or SYSTEM. Use it to label a row in order history: a liquidation is a reduce-only IOC limit order, so orderType, timeInForce and reduceOnly alone read the same as an order the user placed. The same labels as the origin key on the order WebSocket events. Present on every book order. Absent on a TWAP parent row and a conditional order row, which are the account's own instructions, not orders an engine placed. A plain string, not a closed set: a value added later must read as an origin this client does not know yet, not fail the response.

Monaco taker fee rate fixed when this order was placed (re-fixed on replace), in basis points. The fee actually charged on a fill can be lower for a maker rebate: a rebate never exceeds the taker fee of the same fill. Absent for orders placed before rates were stored.

Monaco maker fee rate fixed when this order was placed (re-fixed on replace), in basis points. Negative means rebate. The rebate actually paid on a fill can be smaller: a rebate never exceeds the taker fee of the same fill. Absent for orders placed before rates were stored.

The RFQ (block trade) this order filled in: set on RFQ orders only (origin RFQ). Read the RFQ itself with GetRfq.

Set on a maker's RFQ quote order only: the quote version's internal engine id the order rested for. It is not the public quoteId; the taker's order, which fills from several quotes, carries none.