Ticks of some stocks giving incorrect low and high values in ohlc data

waltons
{'buy_quantity': 3404, 'sell_quantity': 1927, 'mode': 'quote', 'volume': 0, 'ohlc': {'close': 621.85, 'low': 0.0, 'open': 0.0, 'high': 0.0}, 'last_quantity': 0, 'average_price': 0.0, 'tradeable': True, 'instrument_token': 128063748, 'last_price': 0.0, 'change': -100.0, 'depth': {'buy': [{'orders': 1, 'quantity': 2, 'price': 620.0}, {'orders': 1, 'quantity': 1, 'price': 617.0}, {'orders': 1, 'quantity': 10, 'price': 616.55}, {'orders': 1, 'quantity': 5, 'price': 616.25}, {'orders': 1, 'quantity': 1, 'price': 615.0}], 'sell': [{'orders': 1, 'quantity': 10, 'price': 626.9}, {'orders': 1, 'quantity': 4, 'price': 629.2}, {'orders': 1, 'quantity': 1, 'price': 630.0}, {'orders': 1, 'quantity': 1, 'price': 634.85}, {'orders': 1, 'quantity': 1, 'price': 635.0}]}}

low and high values of `KSBPUMPS` is being sent as 0 in the websocket tick while the Kite dashboard is showing correct finite values. This is dangerous for those relying on these values in their strategies. Please fix this asap. Same issue with `SIMPLEXINF`.

Correct me if I am wrong, isn't the websocket API same for Kite dashboard and Kite subscription Api service?
  • sujith
    Hi @waltons,

    Yes, Kite web and Kite Connect use same websockets. You are looking at BSE scrip.
    We have informed it to concerned team. It will be fixed soon.
    For now i would suggest you to use NSE scrip.
  • waltons
    @sujith For GRINDWELL NSE scrip, the API is returning 0 for low and high values when it has already traded a lot in the first hours of today's trading session.
  • sujith
    @waltons,
    Can you paste instrument token?
  • sujith
    @waltons,
    I just checked and OHLC is as follows o 326.9 h 339.9 l 325.0 c 328.7
    I don't think this scrip had any issues today because Kite web also uses the same and nobody reported this.
    Let me know if it happens again.
Sign In or Register to comment.