Get Order History
Retrieve your orders with optional filters for state, mint, and pagination.Query Parameters
Response
Additional Fields for Filled Orders
Orders that have been fully or partially filled include extra fields:Execution Attempts
Order history includes execution attempts for each order. When an order fails to execute (due to slippage, quote generation failure, or other reasons), the attempt is recorded in the history. The reason for failure is not included in the response. Users can adjust slippage settings via the update endpoint if execution keeps failing due to slippage.Event Types
Each order includes anevents array tracking its lifecycle:
Each event includes
type, timestamp, and state. Events that involve token movement (deposit, fill, withdrawal) also include:
Fill events include additional fields:
Order States
Orders follow a state machine from creation to completion. TheorderState field provides a human-friendly state, while rawState shows the exact internal state. For a high-level view of how an order moves through these states, including OCO and OTOCO branching, see the Lifecycle page.
Display States
Raw States
TherawState field exposes the internal processing state. Multiple raw states map to each display state:
State Flow
cancelled automatically (displayed as oco_cancelled in the raw state).
For OTOCO orders, the child OCO pair only activates after the parent order reaches filled. If the parent expires or fails, the children are never created.