Adjustment Factor with Multiple Non-Runner

[gr33d]

Hello All,

I've seen some posts about this already, but one thing that isn't clear too me is how multiple non-runners work. Is it fair to assume that it's just an iterative process?

For example, you follow the below example for the first removal:

https://en-betfair.custhelp.com/app/...-be-treated%3F

Then when a second removal comes, you are applying the adjustment factor to the already adjusted prices?

It's my understanding that adjustment factors can also change as horses are removed, so is it best to use the adjustment factor returned from the Runner within MarketBook?

If I am not using the streaming API, but polling on my order status, if I make a call to listCurrentOrders with EXECUTION_COMPLETE in the OrderProjection, will the returned order details include the prices with the adjustment factor already applied? What about if I do the same in listMarketBook (with the OrderProjection similarly set)?

[gr33d]

I ended up raising a support ticket for this and got the following response incase anyone else has the same question in the future:

Yes, the reduction factor system is an iterative process, multiple reduction factors are simply applied to the already adjusted prices.

Once a runner is withdrawn, the remaining adjustment factors are updated so its best to use the adjustment factor returned from the Runner within listMarketBook.

Any prices returned by listCurrentOrders and the OrderProjection will include the prices with the adjustments already applied.