Duplicate market data charges when using .net SDK (Client side)
Why do we have to pay an extra market data charge to use the .net SDK API?
Currently if I want CME market data on the .net SDK api then I have to pay the market data charge to have CME market data on my TT front end and again to use is it in a .net SDK api application which I'm running on the same device.
If the market data is all through the same ISV and on the same machine it should be covered by a single market data charge. This is even more annoying as for the .net SDK api I only actually want pricing for my own synthetic spreads but I need to pay a second charge for all the markets that the autospreader relies on.
We don't pay a second market data charge for deploying say an ADL algo so why is this the case with the API? Just to reiterate, this is for the client side api, not the server side.
When using many markets, market data is a major charge and doubling that charge makes the total all in cost of TT much less attractive compared to other ISVs that don't do this.
@jchapman - please send me your details at andrew@trade.tt so we can discuss. As a preview, this is an exchange mandate, not one imposed by TT.
@jchapman : did you find an answer to this? Very confused by the duplicate charge as well.
Apparently SDK applications are considered a separate piece of software to the main TT software. As such the exchanges view it as being a separate device and worthy of another market data charge.
