Active Kite Connect app rejects correct Zerodha client ID before request token

Siddhesh101
My Kite Connect app is active and has an active subscription. It is restricted to my Zerodha client ID, and I am signing in with that same ID.

The OAuth flow reaches the registered HTTPS redirect URL, but Kite returns an error before issuing a request_token. Therefore the token-exchange endpoint is never reached.

Checks already completed:

App status is Active.

Registered redirect URL is correct and HTTPS.

The Zerodha client ID in the app settings was re-saved.

The server uses kiteconnect Python package version 5.2.1.

No API key, API secret, request token, or access token is being exposed.

Please verify whether this client ID is enabled/mapped correctly for this Kite Connect app on the backend, and refresh the entitlement if needed. I can provide the app identifier privately if required.
Sign In or Register to comment.