Level2 data
Access to aggregate and non-aggregate order book collections.
Last updated
Access to aggregate and non-aggregate order book collections.
Last updated
Order book (or level2) is a collection of buy and sell orders for specific instruments organized by price level. Each level has three important values - price, size and side. This collection is dynamic, in other words, it is constantly updated in real time during the day.
Many professional traders develop their strategies using order book data. Quantower API provides users an easy way to get aggregated and non-aggregated order book snapshots. To use it you just need to execute the "" method and pass the parameters you need. This method is located at the "" class. Each instrument has its own "" object.
There are two method overloads:
This method takes the “’-object with properties:
- enum, type of aggregation (“Price level” by default)
CustomTickSize - aggregation step (cannot be less than symbol tick size)
LevelsCount - number of levels required
CalculateCumulative - set ‘true’ if you need cumulative value for each price level.
This method takes the “”-object with properties:
- the object described above.
CalculateImbalancePercent - set ‘true’ if you need ‘imbalance’ value for each price level.
These methods return a ‘’ object with two lists - ‘Asks’ and ‘Bids’. Each collection contains instances of class. There are our price levels.
In this topic we will develop a simple indicator which will draw ‘Cumulative’ values as histogram.
First, let’s define input parameters. We want to manage the number of levels and set custom tick size.
Populate constructor of our class. Define name and add line series.
In the ‘OnUpdate’ method we skip the historical part and then get a level2 snapshot. Be sure to check that the ask/bid collections have values. Then we get the required levels and set ‘Cumulative’ values into our indicator buffers.
In the ‘OnClear’ don’t forget to unsubscribe from the ‘NewLevel2’.