"Historical API: 'Insufficient permission' for all NFO instruments, NSE equities work fine

NATWAR
My Kite Connect app (API key: 7mevudc4n3l6jr3a) has the historical data add-on active. Historical candle requests for NSE equities and indices work perfectly (over 1 million candles fetched today). However, every historical request for NFO instruments (stock futures, e.g. TRENT26JULFUT, TVSMOTOR26JULFUT) is rejected with "Insufficient permission for that call" — tested with both short (30-day) and long date ranges, same error.

Does my historical data subscription cover the NFO/derivatives segment? If not, how do I enable derivatives historical data on this app? If it should already be covered, please advise why these requests are being rejected.
  • nagavenij
    nagavenij edited July 20
    We were able to fetch historical data for the NFO segment successfully from our end. Kindly download the latest instruments file, verify that you are using the correct instrument token, and try again.
    Historical data access is enabled by default with the Kite Connect subscription.
    Note: Please ensure that you remove or mask any app-specific API keys, client tokens, access tokens, or other sensitive credentials before sharing the logs.
  • salim_chisty
    With Kite Connect subscription, the historical data access is enabled by default; it covers all supported segments, including NSE, NFO, BSE, CDS, MCX, BFO, and INDICES.

    You can access intraday historical data for active options contracts. However, historical data for expired options contracts is not available. For futures, you can retrieve day-level historical data for expired contracts by using the continuous feature. Please refer to the historical data API documentation for more details. Please ensure that you are using the correct instrument token or trading symbol from the latest instrument dump.


    If the issue persists, please enable debug mode in your Kite Connect client and share the complete request-response log or stack trace.

    Note: Please ensure that you remove or mask any app-specific API keys, client tokens, access tokens, or other sensitive credentials before sharing the logs.
Sign In or Register to comment.