Subject: Persistent 403 Invalid Checksum During Kite Connect Authentication
Hello Zerodha Kite Connect Support,
I am facing a persistent authentication issue with my Active Kite Connect Connect app.
I have followed the official Kite Connect V3 authentication flow exactly as documented:
1. Opened the official Kite Connect login URL using my API key. 2. Successfully completed Zerodha login and OTP. 3. Received a fresh request_token through the registered redirect URL. 4. Generated the checksum using: SHA-256(api_key + request_token + api_secret) 5. Sent a POST request to: https://api.kite.trade/session/token 6. Used the required header: X-Kite-Version: 3 7. Used application/x-www-form-urlencoded request data.
I have tested the authentication in multiple ways: - Python KiteConnect SDK - Independent direct HTTP implementation - Standalone authentication script - Manual extraction of the fresh request_token from the callback URL
All tests consistently return:
HTTP status: 403 Message: Invalid `checksum`
The login itself is successful and a fresh request_token is generated correctly. The failure occurs only when exchanging the request_token for the access_token.
My Connect app is Active, and the registered redirect URL is:
Since the issue persists with both the official SDK and an independent direct API implementation, could you please verify the following on your side:
1. API key and API secret mapping for my Connect app 2. Server-side configuration/activation of the app 3. Whether there is any credential propagation or synchronization issue 4. Whether the app needs to be reactivated or reset from your side
I have not exposed or shared my API secret, access token, or request_token.
Please investigate the app-side/server-side authentication configuration rather than only suggesting changes to the Python SDK, as the same error occurs with a direct HTTPS request to the documented token endpoint.
