Thank you for the response.
can you help me?
I have already performed the standalone authentication test as suggested, following the exact Kite Connect V3 login flow from your documentation.
The following was tested independently of my SENSEX application:
1. Official Kite Connect login URL with the API key
2. Successful Zerodha login and OTP
3. Fresh request_token received after login
4. Checksum generated as:
SHA256(api_key + request_token + api_secret)
5. Direct POST request to:
https://api.kite.trade/session/token6. Header:
X-Kite-Version: 3
7. Content-Type:
application/x-www-form-urlencoded
I have tested this both with:
- Python KiteConnect SDK
- Independent standalone HTTPS implementation
I also performed a manual-token test where I copied the request_token directly from the browser callback URL, eliminating the possibility of an issue with my application's callback handling.
Despite this, the standalone/direct API request consistently returns:
HTTP 40
September 9
