As you are aware, to everyone's frustration, we had yet another incident on Monday at Thomson Reuter's (TR) end despite their promises and efforts to improve the reliability of the backend (I'd made a detailed post about this last month) which affected all Kite users.
We've reached an agreement with TR to scrap the current backend layer they've given us, which is used by Kite, completely. Instead of relying on TR's high level APIs, we'll build a new API layer from scratch that speaks to TR's OMS using their proprietary low level TCP protocols. The work's starting this week. I don't have a timeline, but we're going to put in our best effort to finish the development as fast as possible. We hope this will put an end to the reliability issues once and for all.
does this change affect latency(the time taken for placing order at the terminal and response time)?I assume since now the new APIs works on TCP latency is essentially reduced? What are your thoughts on this?
@sampath_topc Yeah these are for core api calls such as order placing, order book, holdings and positions etc. Websocket streaming and historical api are separate piece and it doesn't affect them.
As said before we are facing issues in with the websocket API too. There is some delay in the price. We are already discussing that in our other thread and others have confirmed similar issues. Have a look.
Eg. Days, or few Weeks or Months?
As said before we are facing issues in with the websocket API too. There is some delay in the price. We are already discussing that in our other thread and others have confirmed similar issues. Have a look.