I am integrating Kite Connect API v3 into a private Python application using a localhost redirect endpoint.
The browser successfully opens the official Kite login page, and the account login and 2FA complete. The browser then returns to my registered localhost callback, but my application's strict callback validator rejects the redirect.
I found an October 2024 forum response confirming that a successful redirect can include:
1. Is `type=login` still an expected parameter in successful Kite Connect v3 redirects? 2. Should applications treat `action`, `type` and `status` as mandatory, or can any be omitted? 3. When custom parameters such as `state` are supplied through URL-encoded `redirect_params`, are they returned as ordinary top-level query parameters? 4. Are there any other standard callback parameters that an application should recognize?
Our goal is to implement a strict but compatible callback validator without weakening state verification or exposing authentication credentials.
