search

Kotak-Neo / kotak-neo-api

113 stars 105 forks source link

websocket response issues #31

Open conquistadorjd opened 1 year ago

conquistadorjd commented 1 year ago

Thanks for updating web socket documentation however it is still not complete. Can you please clarify the response structure for futures and options as well ?

Currently you have specified for Index, Stocks and Depth Can you please specify same for futures and options as well ?

Another issue: Many times we are getting response which does not have ltt and ltp. e.g. {'ftm0': '09/01/1970 13:18:36', 'dtm1': '09/10/1971 01:35:43', 'fdtm': '08/08/2023 15:30:00', 'v': '221422800', 'ltq': '50', 'tbq': '209550', 'tsq': '509000', 'bp': '82.10', 'bq': '1450', 'bs': '200', 'to': '17623040652.00', 'name': 'sf', 'tk': '47876', 'e': 'nse_fo'}

Also, If I don't want depth details only ltt and ltp is required, is there any way to request on these ( not receive depth)

Kotak-Neo commented 1 year ago

Have updated for FnO as well :) Also you can use quotes for your use case.

conquistadorjd commented 1 year ago

Can you please clarify why ltt is not always part of the response. e.g. most of the times I am getting only ~20 ticks per minute for ATM option. I verified this with other data source and there I am getting 50 to 60 ticks per minute. Why less ticks in Kotak neo ?

conquistadorjd commented 1 year ago

any update on this @Kotak-Neo ?

Most of the time I dont get ltp, I keep getting below response type

{'ftm0': '02/01/1970 09:22:59', 'dtm1': '28/03/1971 12:36:41', 'ltq': '50', 'tbq': '286500', 'bs': '37750', 'name': 'sf', 'tk': '52323', 'e': 'nse_fo'}

Prrix commented 11 months ago

As it is a websocket it gives ltp in response only when ltp changes!!