Kite connect

Mano2211
I am facing a persistent Kite Connect session-token authentication issue with a newly created Personal API app.

Manual Zerodha login completes successfully and produces a fresh request_token.

However, immediately exchanging that token through:

POST /session/token

returns:

HTTP 403
error_type: TokenException
Invalid checksum

I have verified the following:

- App is Active
- API key and API secret are from the same app
- API secret was regenerated and retested
- A completely fresh request_token is generated for every attempt
- The request_token is used immediately
- No leading/trailing whitespace is present
- Login uses the official v=3 flow
- Checksum is SHA256(api_key + request_token + api_secret)
- Request is application/x-www-form-urlencoded
- Fields are exactly api_key, request_token, checksum
- X-Kite-Version is 3
- The issue reproduces in an independent standalone script outside my main application

Could you please check whether there is any app-side, account-side, or session-generation issue associated with this Kite Connect application/account?

I will not post the API secret, request_token, or access_token publicly.
  • salim_chisty
    The error message indicates that your request token might have expired. A request token, however, is valid for only a few minutes and can be used just once. To resolve this, you need to fetch a new request token and exchange it for an access token.
    Please note that the exchange mandates that traders log in manually at least once a day, and we do not recommend automating the login process.

    Here are the key details:
    - Access tokens are flushed daily at 7:30 AM, and new tokens are generated at 7:35 AM.
    - Ensure you generate the access token after 7:35 AM on the same trading day. The token will remain valid throughout the day unless you log out.

    Additionally, please follow the login flow as outlined in the Kite Connect API documentation. For further guidance, you can refer to this webinar.
Sign In or Register to comment.