Step by step
Zerodha connects through Kite’s own login. You sign in on Zerodha’s page, approve access, and TradeLyser keeps a token to pull trades on a schedule. Your Kite password stays with Zerodha.
Choose Zerodha in TradeLyser
Go to Settings → Broker connections, open the broker picker and choose Zerodha, then press Connect Zerodha.

Figure 1. The broker picker. Zerodha sits in the Active Brokers group. Log in on Kite
You are sent to the Kite login. Enter your Client ID and password, then the TOTP or SMS code your account uses.
Approve access
Approve the permission screen. Read access to trade and order history is all a journal needs.
Let the first import finish
Back in TradeLyser, the historical import runs. How far back it reaches depends on your account age and Kite API limits.
Check one session before tagging
Compare the trade count for your last session with the Kite order book. If it matches, start tagging.
What syncs from Zerodha
What syncs
- Executed trades in CNC, MIS and NRML: symbol, quantity, side, timestamp and product type
- Charges, where the Kite API provides them
- Partial fills and scale-outs, one row each
- Child fills of bracket and cover orders, plus GTT and AMO orders once they execute
What does not sync
- Expiry-day or expiry-week labels. Add them as tags.
- Parent order IDs for bracket and cover orders
- Trades older than the API backfill. Use the Console tradebook.
- MCX commodity, which the supported brokers table does not list for Zerodha
How each Kite product shows up
Every synced row carries the symbol, quantity, side, timestamp, product type and the charges Kite reports. The product type is what lets you split reviews later, so keep it in mind when you tag.
| Segment | Kite product | What to expect in the journal |
|---|---|---|
| Cash delivery | CNC | Full fills with charges. Hold time tells swing trades apart from investments. |
| Intraday | MIS | Same-day round trips. An auto square-off arrives as its own exit fill. |
| Futures | NRML or MIS | Contract month, lots and side. Review overnight NRML apart from intraday MIS. |
| Options | NRML or MIS, CE and PE | Strike, expiry and option type. A spread lands as separate legs. |
Partial fills and scale-outs import as several rows, which is correct. Give every leg of one planned trade the same strategy tag rather than merging rows. Bracket and cover orders resolve to their executed child fills, because sync follows executions and not parent order IDs.
Zerodha quirks worth knowing
- Kite access expires. When a pull fails, TradeLyser asks you to log in again. Do it before your weekly review, not after Monday goes missing.
- MIS auto square-off around 3:20 p.m. looks like an ordinary sell. If your plan was to hold to the close, note that the broker closed you out.
- GTT and AMO orders import when they execute, so the fill time can differ from when you placed the order.
- It does not matter whether you traded from Kite mobile or web. Only the Client ID counts.
- Corporate actions can rename a symbol and split its history. Write the event into your notes if you compare long periods.
- Contract notes post after settlement, so sync is faster for daily journaling. Console stays the record for tax.

A routine that keeps the journal honest
- After the close, confirm the sync ran and the trade count matches the Kite order book.
- Tag each trade with one strategy, such as opening drive, CNC swing or Nifty expiry iron condor, and flag rule breaks like oversize or revenge entries.
- On Friday, filter MIS apart from NRML and Nifty apart from Bank Nifty, and read net P&L after synced charges.
- Once a month, check one random day against the Console contract note to catch fee drift.
CSV fallback: the Console tradebook
Use a CSV when Kite access is down for a while, or when you want history from before the API backfill reaches. The tradebook CSV is easier for bulk imports than contract notes, which are PDF-first.
- In Console, go to Reports → Tradebook (or download the contract note bundle) for the missing date range.
- Open the CSV import in TradeLyser and upload the file.
- Map the columns to symbol, date, quantity, price and charges.
- Remove duplicates against synced rows by matching the order timestamp and symbol.
- Reconnect Kite so new sessions sync on their own again.
Write the uploaded date range in your notes. Weeks that mix manual and synced days are where duplicates come from.
Trouble syncing?
Does TradeLyser store my Zerodha password?
No. You log in on Zerodha’s own Kite page and approve access there. TradeLyser keeps a token to pull trades, not your password.
Why did my Zerodha trades stop syncing?
Kite access expires, and when a pull fails TradeLyser asks you to log in again. Reconnect from broker settings and run a sync. If history is still empty, check in Console that the equity and F&O segments are active on the same Client ID.
Will MIS auto square-off trades import correctly?
Yes. A forced square-off appears as a normal exit fill with its own timestamp. Note in your journal whether the exit was the broker’s or your planned stop.
How far back does Zerodha sync go?
The first backfill depends on Kite API limits and your account history. For older trades, import the Console tradebook CSV once, then let sync handle new sessions.
Do synced trades include F&O charges and STT?
Rows include charges when the Kite API provides them. Review net P&L in TradeLyser for F&O, because gross figures on Kite understate the cost of high churn.
I trade on Kite mobile and web. Does that matter?
No. Sync is tied to your Client ID, not the device. Every executed order on that ID imports on the next pull.