Skip to main content
Only cancels, last 50:
Returns limit and stop order events — Placed, Updated (re-priced), Canceled, Executed — newest first. A cancelled limit creates no order row, so neither getOpenOrders nor getOrders shows it; this does. On OstiumClient, user defaults to the connected trader.

Parameters

limit must be a positive integer.

Response schema

Reading one order’s history

A slot is reused once its order ends, so one order’s history runs from a Placed event to the next Canceled or Executed on the same limitId. On Executed, limitId matches Fill.limitId on the position it opened, and oid matches that fill’s oid.
  • Updated events only re-price, so they carry no size fields.
  • The subgraph keeps side and order type only for the order currently in each slot, so side and orderType are omitted on events from earlier orders in a reused slot.
  • Events the indexer has not linked to a slot are left out rather than reported as slot 0.