☰
›

Getting incorrect OHLCV Data using the Kite connect api

ssshama
ssshama in Python client
Using the Python (historical_data) api when I retrieve the OHLCV Data for ADANIENT for 2024-06-19 I get
Date and Time : 19-06-2024 10:08
Open : 3261.25
High : 3314
Low: 3239
Close: 3262

But when I see the same data on the UI I am getting
Open : 3261.25
High : 3263
Low: 3260
Close: 3262

Not sure if this is a one off?
Tagged:
  • rakeshr
    rakeshr
    @ssshama
    It might be cache, if you would have requested in the same minute interval of candle creation. Can you retry the request for the same interval now?
  • ssshama
    ssshama
    The api was called 9 seconds after the close of the 19-06-2024 10:08

    Subsequently called it after 10 mins to check. It was the same problem.
  • ssshama
    ssshama
    @rakeshr
  • rakeshr
    rakeshr
    It's showing fine for us. Can you recheck?
  • ssshama
    ssshama
    Now it is showing correct. I am concerned about the incorrect data during trading hours. What can be done to avoid the same? @rakeshr
  • rakeshr
    rakeshr
    I am concerned about the incorrect data during trading hours. What can be done to avoid the same?
    Date and Time : 19-06-2024 10:08
    Open : 3261.25
    High : 3314
    Low: 3239
    Close: 3262

    But when I see the same data on the UI I am getting
    Open : 3261.25
    High : 3263
    Low: 3260
    Close: 3262
    Both the Kite web charts and the historical data API use the same chart backend. So, the difference in response can't arise. As stated above, discrepancies can only occur if you fetch data before or near the candle completion time. Historical data APIs are not meant to poll real-time data.
Sign In or Register to comment.