Supported order types

OrdType	Execution on strategy subaccounts and broker accounts	Execution on virtual accounts
Market	Sent directly to broker	Executed by the next tick price
Limit	Sent directly to broker	Executed by the limit price
Stop Market
Market If Touched*	Triggering checked against the next tick price internally. Once triggered, is converted a market order and sent to the broker	Triggering checked against the next tick price. Once triggered, is executed by the tick price.
Stop Limit	Triggering checked against the next tick price internally. Once triggered, is converted to a limit order and sent to the broker	Triggering checked against the next tick price. Once triggered, converts to the limit order.

** — Market if Touched behaves like a stop order, but the triggering conditions are those of a limit order.*

Order IDs

There are 3 fields responsible for identification of an order:

ClOrdId — an arbitrary string provided by the strategy when placing an order. If provided, and another order with the same ClOrdId exists on the strategy’s account, the new order will be rejected.
OrderId — the primary identifier of the order, assigned once the order is recorded by the Accounts Service. This ID is unique within the AS (so, if there several AS in your installation, order IDs may overlap).
ExternalId — string, the ID assigned to the order by the broker.

Linked orders (OCO and OTO)

When submitting an order, it can be linked to other orders. There are two link types: One-Triggers-Other and One-Cancels-Other. The reference to the order is by ClOrdId.

OTO: usually, a main order is submitted along with suspended linked orders. When the main order gets filled (partially or fully), linked orders are activated. If there are no orders with the given ClOrdId, nothing happens.
OCO: once the order gets executed (partially or fully), the linked orders are canceled.

Time in force

There are two options:

GoodTillCancel (default)
GoodTillTime

Suspended orders

If an order is placed as suspended, it will not be sent for execution or triggered (for limit and stop orders) until activated. The order is activated:

Either by ActivationDt