Jorli imports completed trades from your own Zerodha account using a personal Kite API app. You create the app, save its credentials inside your verified Jorli account, and finish login on Zerodha. A paid live-price or historical-candle subscription is unnecessary for Jorli's current completed-trade import. This guide explains the journal connection, including the daily login requirement that can otherwise be easy to miss.
What you need
Have your active Zerodha trading account, its Client ID and a verified Jorli email address ready. The Kite developer account is separate from your usual trading login. Use your own details for both the developer app and Jorli setup. Do not borrow another person's API credentials or substitute a shared example key from a tutorial.
The official Kite Connect documentation describes developer apps, registered redirects and authentication. Jorli handles the server-side login exchange, so you do not need to run a script to generate tokens for the journal. If Zerodha changes a screen label, use the current official instructions alongside the setup panel inside Jorli.
1. Create a Kite Connect Personal app
- Open the Kite developer signup page. Create your developer account with your email, name, password, phone and state, and accept the terms.
- Choose Kite Connect Personal (Free). You do not need the paid market-data plan for Jorli's current trade import.
- Open My Apps → Create New App. Use a name such as My Jorli Journal, enter your own Zerodha Client ID and describe it as a personal trading journal integration.
-
Set Redirect URL to
https://app.jorli.in/broker/zerodha/callbackfor production Jorli. For another environment, copy the exact redirect displayed in its Broker Sync panel. - Leave the optional Postback URL empty, create the app and keep the resulting API Key and API Secret private.
The callback must match completely, including HTTPS, hostname and path. The Jorli marketing homepage is not a callback. A postback is a separate order-update mechanism; Jorli's trade-fetching flow does not need you to configure one. Keep the app's key and secret together so you do not accidentally combine credentials from different apps.
2. Connect from Profile → Broker Sync
In Jorli web, open Profile → Broker Sync → Set Up Zerodha. An existing connection shows Edit API. On mobile, use More → Broker Sync → Set up Zerodha. Enter your Client ID, API Key and API Secret, then choose Save & Connect. Jorli encrypts the credentials before storing them.
Complete login on Zerodha's page and return to Jorli. Check the displayed Client ID and active session before syncing. Passwords and OTPs belong only on the broker's login page; API secrets should never appear in screenshots or support messages. Jorli's integration does not place or modify orders, although the underlying broker credentials may carry broader trading permissions.
3. Check your first import
Choose Sync Now after closing a trade and inspect the journal. The Journal Day button opens a preview where you can select trades and add targets, stop losses or setup tags before importing. Sync fetches today's executions and imports fully closed symbol/day groups with equal total bought and sold quantities. Open or partially closed positions are skipped.
Several fills or round trips in one symbol on one day share an aggregate journal row. The imported prices are quantity-weighted averages. Repeating sync updates that broker record and retains its notes, tags and targets; it does not overwrite a separate manual entry. If you already typed the same execution, review the result for duplication rather than assuming manual and broker rows will merge.
4. Reconnect each trading morning
Zerodha sessions normally expire at 6 AM the next day and can be invalidated earlier. Creating a developer app does not remove that daily login requirement. Follow the expiry shown by Jorli and reconnect each trading morning if you want the day's manual or scheduled import to work. The Kite session documentation explains token expiry.
Optional auto-sync runs Monday to Friday at 4:30 PM IST, provided it is enabled and the session is valid. An 8:30 AM IST reminder is scheduled for enabled connections expiring before the day's sync. Check the last sync result and reconnect banner; a scheduled reminder is not a replacement for completing broker login.
Past trades, charges and common errors
Broker sync is for today. To bring in older Zerodha history, download a Tradebook CSV and follow the past-trade import guide. A No Trade Day is skipped by sync. If nothing appears, check the date, matching buy and sell quantities, account and session before changing credentials.
For redirect errors, compare the full callback URL. For invalid credentials, check that the key and secret came from the same personal app. Save updated credentials and reconnect; revisiting an old callback does not create a fresh session. Removing configuration disconnects the broker but leaves existing journal records intact. Reconcile estimated charges with the contract note using the NSE brokerage calculator.
A terminal-first alternative
The free Kite CLI is a separate tool for traders who prefer terminal commands. Its authentication and command documentation is at cli.jorli.in; installing it is optional and does not connect your journal automatically. Dhan users can follow the Dhan API setup guide. Once connected, add the context a broker cannot supply: your mood, sleep, checklist and one useful note.