I am writing to report a critical issue with the historical data fetched via the Zerodha API. The values retrieved from the API do not match the actual data displayed on Zerodha’s own charts.
Issue Details: The Open, High, Low, Close (OHLC), and volume values from the API differ from what is shown on the Zerodha chart.
This discrepancy is affecting multiple stocks, including Reliance, Tata Steel, and others.
The issue persists across different timeframes.
This inconsistency is causing problems in my trading analysis and strategies.
I have attached screenshots comparing the API data with Zerodha’s chart for reference. Kindly investigate this issue and provide a resolution as soon as possible.
Please let me know if you need any further details.
I just checked for the mentioned candle `'2025-03-28 09:47:00'` for SILVERMIC25APRFUT. Both the source(kite web and kite connect historical APIs) values are same.
I’m reaching out to report and seek clarity on a recurring issue where the OHLC (Open, High, Low, Close) and volume data retrieved via the Kite API differ from the data shown on the Zerodha charting interface (TradingView charts).
Issue Summary: I have attempted fetching OHLC data using:
WebSocket streaming with mode=full The REST endpoint /quote/ohlc Historical data API /instruments/historical/{token}/{interval}
However, in all methods tested, the Open, High, and Low values are often different from the values shown on the Zerodha chart — not just the Close, which I understand can be based on VWAP or auction adjustments.
This discrepancy is not limited to one or two instruments. For example:
BSE, KALYANKJIL, and INOXWIND — as attached — show different values in the API/WebSocket vs the Zerodha chart.
Request for Clarification: Why do these discrepancies occur between the API/WebSocket OHLC data and the charting data? Is this behavior expected or common due to architectural or data feed differences? Is there any way to retrieve the exact same OHLC values that are shown on Zerodha's TradingView chart via the API or another mechanism?
This inconsistency is creating challenges for ensuring data integrity in my trading systems, and I’d appreciate your help in understanding the root cause and any
I’m reaching out to report and seek clarity on a recurring issue where the OHLC (Open, High, Low, Close) and volume data retrieved via the Kite API differ from the data shown on the Zerodha charting interface (TradingView charts).
Issue Summary:
I have attempted fetching OHLC data using:
WebSocket streaming with mode=full
The REST endpoint /quote/ohlc
Historical data API /instruments/historical/{token}/{interval}
However, in all methods tested, the Open, High, and Low values are often different from the values shown on the Zerodha chart — not just the Close, which I understand can be based on VWAP or auction adjustments.
This discrepancy is not limited to one or two instruments. For example:
BSE, KALYANKJIL, and INOXWIND — as attached — show different values in the API/WebSocket vs the Zerodha chart.
Request for Clarification:
Why do these discrepancies occur between the API/WebSocket OHLC data and the charting data?
Is this behavior expected or common due to architectural or data feed differences?
Is there any way to retrieve the exact same OHLC values that are shown on Zerodha's TradingView chart via the API or another mechanism?
This inconsistency is creating challenges for ensuring data integrity in my trading systems, and I’d appreciate your help in understanding the root cause and any