Order entry
Last updated
Last updated
GTC
Good til canceled
GTD
Good til date
goodTilDate
IOC
Immediate or cancel
The send_limit_order
method will wait for the order to be accepted by the exchange before returning. Depending on the time-in-force instruction, the order may require additional parameters.
Orders are canceled by reference to their id
.
The cancel_order
method does not wait for the order to be confirmed canceled before returning. A working order is only canceled when the exchange confirms the cancellation, which can be checked by polling the order status.
Subscribe to all orderflow events. The lifecycle of an Architect order is designed to allow for fast order submission and defensive order status determination. Orders IDs are globally unique.
Order state is represented by a set of status flags:
OPEN
: Order is submitted and assumed to be imminently executable
REJECTED
: Order was rejected by the exchange
ACKED
: Order was accepted by the exchange
FILLED
: Order was filled, partially or fully
CANCELING
: Order was requested to be canceled
CANCELED
: Order was confirmed cancelled by the exchange
OUT
: Order is confirmed to be no longer executable by the exchange, either because it was rejected, filled fully or cancelled
STALE
: Architect couldn't determine the status of the order after some time, manual intervention is required
Any combination of flags is a possible order state, although some flag combinations expected to be extremely rare and indicative of serious counterparty fault (e.g. Open | Out). Generally, the expected order lifecycle is as follows:
Orders are retrieved by reference to their id
. Open orders and recently closed orders can be queried by this method. For a list of valid order states, see .