NautilusTrader
ConceptsEvents

Nightly docs

These docs track unreleased changes and may change without notice. Their code examples can use APIs that the latest release lacks, so run them with a development wheel or switch to the latest release docs.

OrderSubmitted

OrderSubmitted records that the system has sent an order to the trading venue and awaits acknowledgement. The ExecutionEngine applies it to the order, updates the Cache, and publishes it on the MessageBus.

Typical transition: INITIALIZED / RELEASED -> SUBMITTED. Handler: on_order_submitted.

Fields

Beyond the common Python order event fields, OrderSubmitted carries:

FieldPython typeRequired/defaultDescription
account_idAccountIdRequiredThe account associated with the order.

Example

Reading the event in a strategy handler:

def on_order_submitted(self, event: OrderSubmitted) -> None:
    self.log.info(f"Order {event.client_order_id} submitted ({event.account_id})")
  • Events - Event categories, dispatch, and the common order event fields.
  • Orders - Order types and the state machine.
Edit on GitHub

OrderReleased

OrderReleased records that the OrderEmulator has released an order after its trigger condition was met. The emulator applies the event to the order, updates...

OrderAccepted

OrderAccepted records the trading venue's acknowledgement that an order is received and valid (often a FIX NEW OrdStatus). The ExecutionEngine applies it to...

On this page

OrderSubmittedFieldsExampleRelated guides