Advanced Historical Data - How do I interpret updates?

Each batb/batl update contains the following [Level (0-2), Price, Volume Available]

For example, [0,2.2,20] indicates [Level '0' (best price), 2.2 (price), 20 (volume)]

Working through the following initial ADVANCED data messages as an example.

Initial Market Definition and Market Change (mc) Update

{"op":"mcm","clk":"11532844742","pt":1719210499670,"mc":[{"id":"1.229978426","marketDefinition":{"bspMarket":false,"turnInPlayEnabled":true,"persistenceEnabled":true,"marketBaseRate":5.0,"eventId":"33356803","eventTypeId":"1","numberOfWinners":1,"bettingType":"ODDS","marketType":"MATCH_ODDS","marketTime":"2024-07-01T00:00:00.000Z","suspendTime":"2024-07-01T00:00:00.000Z","bspReconciled":false,"complete":true,"inPlay":false,"crossMatching":true,"runnersVoidable":false,"numberOfActiveRunners":3,"betDelay":0,"status":"OPEN","runners":[{"status":"ACTIVE","sortPriority":1,"id":54786,"name":"Jamaica"},{"status":"ACTIVE","sortPriority":2,"id":15302,"name":"Venezuela"},{"status":"ACTIVE","sortPriority":3,"id":58805,"name":"The Draw"}],"regulators":["MR_INT"],"discountAllowed":false,"timezone":"GMT","openDate":"2024-07-01T00:00:00.000Z","version":5992177054,"name":"Match Odds","eventName":"Jamaica v Venezuela"}}]}

First Runner Change (rc) Update

{"op":"mcm","clk":"11532845730","pt":1719210538287,"mc":[{"id":"1.229978426","rc":[{"batb":[[0,1.04,169.29],[1,1.03,169.33],[2,1.02,169.39]],"ltp":0.0,"tv":0.0,"id":54786},{"batb":[[0,1.04,169.29],[1,1.03,169.33],[2,1.02,169.39]],"ltp":0.0,"tv":0.0,"id":15302}]}]}

For selectionId (id:54786) the first available best available to back prices and available volumes are:

• 1.04, 169.29 - Best Price
• 1.03,  169.33 - 2nd Best Price
• 1.02,  169.39 - 3rd Best Price

For selectionId (id:15302) the first available best available to back prices and available volumes are:

• 1.04, 169.29 - Best Price
• 1.03,  169.33 - 2nd Best Price
• 1.02,  169.39 - 3rd Best Price

Second Runner Change (rc) Update

{"op":"mcm","clk":"11532851382","pt":1719210747064,"mc":[{"id":"1.229978426","rc":[{"batb":[[0,1.01,1]],"ltp":0.0,"tv":0.0,"id":58805}]}]}

For selectionId (id:58805) the first available best available to back prices and available volumes are:

• 1.01, 1 -   Best Price
• Empty -   2nd Best Price
• Empty, - 3rd  Best Price

Third Runner Change (rc) Update

{"op":"mcm","clk":"11532851710","pt":1719210758566,"mc":[{"id":"1.229978426","rc":[{"batb":[[0,1.05,15.23],[1,1.04,169.29],[2,1.03,169.33]],"ltp":0.0,"tv":0.0,"id":54786},{"batb":[[0,1.02,15.23],[1,1.01,1]],"ltp":0.0,"tv":0.0,"id":58805}]}]}

For selectionId (id:54786) the first available best available to back prices and available volumes are now:

• 1.05, 15.23 - Best Price
• 1.04,  169.29 - 2nd Best Price
• 1.03,  169.33 - 3rd Best Price

For selectionId (id:58805) the first available best available to back prices and available volumes are now:

• 1.02, 15.23 - Best Price
• 1.01,  1- 2nd Best Price
• Empty - 3rd Best Price

Fourth Runner Change (rc) Update

{"op":"mcm","clk":"11532851724","pt":1719210758979,"mc":[{"id":"1.229978426","rc":[{"batb":[[0,1.05,15.23],[1,1.04,169.29],[2,1.03,169.33]],"batl":[[0,13.5,3.38]],"ltp":0.0,"tv":0.0,"id":15302}]}]}

The above update indicates changes to selection (id:15302)

• 1.05, 15.23 - Best Price
• 1.04,  169.29 - 2nd Best Price
• 1.03 - 169.33 - 3rd Best Price

How to handle conflicting updates

It's safe to assume that if an update is received that conflicts with a prior update, all previously placed conflicting orders have either been matched or canceled and the remaining orders are moved to the top of the book.

For example for the two consecutive updates shown below:

Update 1

{"op":"mcm","clk":"1282931005","pt":1584392071986,"mc":[{"id":"1.170159365","rc":[{"batb":[[0,2.2,20]],"ltp":0.0,"tv":0.0,"id":10829201}]}]}

Update 2

{"op":"mcm","clk":"1282974035","pt":1584393504411,"mc":[{"id":"1.170159365","rc":[{"batb":[[0,1.4,3.7]],"ltp":2.0,"tv":5.52,"id":10829201}]}]}

This indicates that the top of book batb is now 1.4 for selection 10829201

Please note The initial bet unmatched bet at the top of the book (2.2, 2.0) was cancelled (but no explicit update was sent).