Avikashvi

**Subject: Historical Data API returning Insufficient Permission despite Active Kite Connect subscription** Dear Zerodha Kite Connect Support Team, I have subscribed to the paid Kite Connect plan (₹500/month) for my application: **App Name:** Alok_Nifty50_Scanner **App Status:** Active **Subscription:** Kite Connect – Active My API authentication is working successfully. I can: - Generate a fresh access token. - Access my Zerodha profile using `kite.profile()`. - Retrieve the NSE instrument list using `kite.instruments("NSE")`. - Identify the NIFTY 50 instrument successfully. However, when I request historical 5-minute candle data using the Python Kite Connect SDK, I consistently receive: `Insufficient permission for that call.` I have verified that: 1. The API Key in my local application matches the API Key of my paid Kite Connect app. 2. The subscription is showing Active. 3. I have generated a fresh access token after confirming the subscription.

About

Username
Avikashvi
Joined
Visits
2
Last Active
Roles
Member

Activity

  • **Subject: Historical Data API returning Insufficient Permission despite Active Kite Connect subscription**

    Dear Zerodha Kite Connect Support Team,

    I have subscribed to the paid Kite Connect plan (₹500/month) for my application:

    **App Name:** Alok_Nifty50_Scanner
    **App Status:** Active
    **Subscription:** Kite Connect – Active

    My API authentication is working successfully. I can:
    - Generate a fresh access token.
    - Access my Zerodha profile using `kite.profile()`.
    - Retrieve the NSE instrument list using `kite.instruments("NSE")`.
    - Identify the NIFTY 50 instrument successfully.

    However, when I request historical 5-minute candle data using the Python Kite Connect SDK, I consistently receive:

    `Insufficient permission for that call.`

    I have verified that:
    1. The API Key in my local application matches the API Key of my paid Kite Connect app.
    2. The subscription is showing Active.
    3. I have generated a fresh access token after confirming the subscription.

    5:33AM