Order Executions
An order execution is a fill: one buy-side order crossed with one sell-side order. The economic snapshot — price, quantity, the two parties' orders — is immutable from the moment of the cross. Only the settlement status moves.
Executions are read-only through the API. You create trading intent with Order Submissions; the matching engine creates executions when submissions cross.
Settlement lifecycle
| Status | Meaning |
|---|---|
PENDING | Matched, settlement not yet started |
SETTLING | Settlement in flight: charge, payout, inventory transfer |
IN_DISPUTE | The buyer raised a dispute mid-settlement; frozen until it resolves. In flight, not terminal |
SETTLED | Fully settled |
FAILED | Settlement failed; awaiting retry or intervention |
REVERSED | Unwound after settlement (refund / clawback) |
Settlement is what decides whether an order actually filled. Your submission's status re-derives from its executions on every transition — a cross that fails settlement rolls the quantity back rather than reporting a fill you never received.
API surface
| Query | Purpose |
|---|---|
getOrderExecution | Fetch one fill — see Querying |
listOrderExecutions | Page your fills with filters |
recentOrderExecutions | Latest fills, newest first |
For push delivery of fills as they happen, see Real-time.