The scope is deliberately narrow - what you hold, and buying or selling. The access token has to be renewed through Zerodha's login flow by hand, which is the part to plan around.
A small Python server over Zerodha's Kite Connect API with three calls: read the holdings in the account, place a buy order, place a sell order.
- The holdings in your Zerodha account, read live
- A buy order placed through Kite Connect
- A sell order placed the same way
- Credentials read from a .env file rather than written into the code
Python with uv, a Zerodha account with Kite Connect API access, and your API key and secret in a .env file. The access token is obtained by hand: generate the login URL, log in, copy the request token out of the redirect, and exchange it for an access token. Orders placed here are real orders on a live account.
Build from source — clone the repository and build it, then point your client at the binary
