Order Handling
Open orders in HaasScript
Last updated
Open orders in HaasScript
Last updated
For order status monitoring there are 6 commands available. Generic commands and specific command that require an order identifier.
The generic commands don't require an orderId and will work on all orders.
Will return true when the bot as any open order active. Can be used to skip or execute parts that depend on having an order open or not.
Will be true if the engine has received a finished order between the last and current update cycle. The order can be rejected, cancelled, partially filled or filled order. Basically everything not active on the exchange. The command can be used to skip parts of the script that handles orders of that kind.
Requests to cancel all the current open orders once the script is executed.
The specific commands require an order id and will only control that specific order.
Will return true when the order is still active on the exchange.
Will only return true when the order is filled 100%.
Requests to cancel a specific open orders once the script is executed.
The command returns a collection of every order detail known. When used in the script editor, we can index properties in 2 different ways. Both will return the same value.
Returns all the current open orders associated with the bot. The items in the collection are the same as the result of OrderContainer.
Returns a collection of the last 50 (partially) filled orders. The items in the collection are the same as the result of OrderContainer.
Returns the amount filled when the order is not active on the exchange anymore.
Returns the remaining amount the order is not active on the exchange anymore.
When the order is still active on the exchange it will return the time-span in seconds. If the order is not active, it will return the total time it was live on the exchange.
