KOTAK NEO LATEST SDK

[brotechnical77-ctrl]

NEW KOTAKNEO SDK HAVE HISTORICAL DATA FEATURE,IS IT SUPPORTED NOW ON OPENALGO

[Kxrma47]

Not yet in the current OpenAlgo Kotak adapter. Its get_history() is still a placeholder that logs “not supported” and returns an empty DataFrame (source); the supported-interval lists are also empty (source). The newer Kotak Neo SDK capability therefore still needs to be wired into this adapter before /history can use it.

[marketcalls]

Yes, this is supported now.

@Kxrma47's answer was accurate when it was written earlier today, and we turned the implementation around within a few hours of it. Historical data for Kotak Neo is now on main in commit 44c488c, so get_history() is no longer a placeholder and the supported interval lists are no longer empty.

What you get

• Intervals: 1m, 3m, 5m, 10m, 15m, 30m, 1h, D, W
• Exchanges: NSE, BSE, NFO, BFO, NSE_INDEX, BSE_INDEX

Verified against a live Kotak session: a two year 1-minute pull returns 184,595 candles across 497 trading sessions, with no duplicates and no gaps at the chunk boundaries. Every index symbol returns both intraday and daily data, including NIFTY, BANKNIFTY, FINNIFTY, MIDCPNIFTY, NIFTYNXT50, INDIAVIX, SENSEX and BANKEX.

Implementation note: direct REST API, not the vendor SDK

To answer the SDK part of the question directly: OpenAlgo does not wrap the kotakneoapi Python SDK. It calls the Neo historical endpoint over REST directly, which is deliberate and is what keeps it fast.

The request path stays short, and every call shares OpenAlgo's pooled HTTP/2 client, so a long pull reuses one connection instead of paying SDK and per call connection setup overhead on every chunk. It also means no extra dependency to track, and no waiting on an SDK release when an endpoint changes.

For scale, the two year 1-minute pull above is 25 chunked requests and completes in roughly 10 seconds end to end.

Point to note: MCX and CDS have no historical data

Kotak does not serve history for the commodity and currency segments. The API refuses every MCX and CDS contract with:

HTTP 400 {"status":"ERROR","fault":{"code":400,
          "message":"Historical data is not supported for this exchange."}}

We confirmed this across four MCX commodities (CRUDEOIL, GOLDM, SILVERM, NATURALGAS) and multiple exchange segment spellings, so it is a broker side limitation rather than something OpenAlgo can work around.

MCX and CDS continue to work normally for quotes, depth, orders and streaming. A history request on those exchanges returns a clear error rather than an empty series, so it will not be mistaken for a market holiday.

Open interest is not yet populated by Kotak in this phase, so the oi column reads 0 for now.

Getting it

git pull on main.

Separately, Kotak is deprecating the existing HS market feed on 15 September 2026 (see #2010). Migration to the new market feed integration is planned for the coming week.