Kite Access Token Management
Generate & Re-Generate Kite Connect v3 Access Token via Zerodha Login Redirect
đ
Time Remaining Until 6:00 AM Next Day
Client ID
đĒ Zerodha
ZD8434
Kite Connect User ID
Token Created At
đ
Timestamp
â
Session start time
Expires At (Rule)
â° Next Day 6:00 AM
â
Strictly valid until 6:00 AM next day (IST)
Active Access Token
đ Masked
âĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸâĸ
In-memory & persisted in account.json
đĒ
1-Click Generate Kite Access Token via Zerodha Login
Per official Kite Connect documentation (kite.trade/docs/connect/v3/user/), user authentication requires logging in through Zerodha's login portal. Clicking the button below opens the Zerodha Kite login interface. Upon successful login, you will receive a
request_token to exchange for your daily access token.
OFFICIAL ZERODHA LOGIN URL:
https://kite.zerodha.com/connect/login?v=3&api_key=...
đ
Dedicated Redirect Page:
Redirect URL
/KiteCallbackUrl
In your Zerodha Developer Console (developers.kite.trade), set your Redirect URL to http://localhost:3000/KiteCallbackUrl. Upon login, Zerodha returns to this page where the request_token is saved in the database (Account & kite_callbacks) and converted into an Access Token valid until 6:00 AM next day.
đ
Exchange Request Token for Access Token
Kite Session API
After logging in at Zerodha, you are redirected with a URL containing ?request_token=XXXXX. Paste that request_token here to complete the SHA-256 session exchange and activate your access token immediately.
âī¸
Direct Access Token / API Key Settings
Advanced Admin
đĄ
Connection Diagnostics
Click Run Test Now to verify if the active access token successfully authenticates with Zerodha Kite Connect servers (
api.kite.trade/user/profile).
âąī¸
Token Validity Lifecycle Rule
Strict Rule
-
1Daily Expiration at 6:00 AM: Regardless of when a token is generated, it remains valid strictly until 6:00 AM next day (06:00:00 IST).
-
2When Token Expires: The system automatically flags the session as EXPIRED and provides a 1-click button to re-generate the token via:https://kite.zerodha.com/connect/login?v=3&api_key=xxx
-
3Persistent Storage: The active token, created timestamp, and calculated expiry are saved in
account.jsonand the backend database tableAccount.
đ
Official Kite Documentation
Official Docs â
The Kite Connect User Authentication Flow follows these steps:
- Redirect user to Kite login URL with
api_key. - User logs in with 2FA; Zerodha redirects back with
request_token. - Exchange
request_tokenusingSHA256(api_key + request_token + api_secret)for the sessionaccess_token.
Reference: https://kite.trade/docs/connect/v3/user/