It would be good to add the intermediate order status "UPDATE" as most orders are executed partially and we may have to place the stop loss for the partially executed orders.
@Sandeep_Prakash, The order update events are async and are send by the OMS. We just relay them. The correct practice is to pull orderbook or order history when you receive an order update.
UPDATE is not a real status of the order, it is a place holder in postbacks or order updates. You can check all interim statuses in order history API.
For the partially filled orders I would want to place the StopLoss immediately and not wait for the complete order to be filled.
NOTE: Here the Order is filled almost immediately. But suppose the price doesn't return to the LIMIT price, then Partial order will remain as it is.
No doubt, I can add "UPDATE" as a String, and live with it. It's just that it may be a good idea as I think many may use it.
If order status "OPEN" will be sent mandatorily.
Also, please correct me if I'm wrong, these events are async and "OPEN" order can come after "UPDATE" or even after "COMPLETE" is it not?
And the intermediate status like "UPDATE" may not be sent at all.
The order update events are async and are send by the OMS. We just relay them. The correct practice is to pull orderbook or order history when you receive an order update.
UPDATE is not a real status of the order, it is a place holder in postbacks or order updates. You can check all interim statuses in order history API.