STOP
order will be triggered once the given trigger_price
is reached and new order of trigger_price_type
will be created.
TP_SL
order placed, three algo orders will be created in Orderly system.
TP_SL
order, user must send the edit order request on the root_algo_order
and must pass both root_algo_order
and child_orders
as parameters. User may pass only one child_order
for editing. If the goal is to edit quantity
, both child_order
must be passed and the quantity
need to be identical.
TP_SL
orders.
POSITIONAL_TP_SL
order.
TP_SL
orders support triggering Limit orders.BRACKET
order is to use track a regular order and close its position with TP_SL
\ POSITIONAL_TP_SL
order. In this example, assume the regular order under BRACKET
order as leg_1
and the TP_SL
\ POSITIONAL_TP_SL
child order under BRACKET
order as leg_2
.
leg_1
= BRACKET
and the triggered regular order
leg_2
= POSITIONAL_TP_SL
\ TP_SL
and their triggered child orders
BRACKET
+ TP_SL
: The quantity of TP_SL
order is determined by the executed_quantity
of leg_1
.
BRACKET
+ POSITIONAL_TP_SL
: The quantity of POSITIONAL_TP_SL
order is determined by the user’s position at the time of triggering.
Note: For BRACKET
+ POSITIONAL_TP_SL
, when leg_2
’s POSITIONAL_TP_SL
order is triggered, the previously active POSITIONAL_TP_SL
orders will be canceled. If there were existing triggered POSITIONAL_TP_SL
order, leg_2
will be canceled.
Makes sure there’s only one active POSITIONAL_TP_SL
order. For any of the regular order under leg_1
being executed, leg_1
and leg_2
will be cutoff such that leg_2
becomes an independent POSITIONAL_TP_SL
order.