Jorli can import today's completed Dhan trades into your journal so you can spend your review time on decisions rather than retyping executions. You create an individual API app in your own Dhan account and connect it inside Jorli. You do not need to write code, paste a daily access token or purchase a market-data subscription for Jorli's current trade import.
Before you begin
You need an existing Dhan trading account and a Jorli account with a verified email address. Use your own credentials, not someone else's API app or a screenshot from a tutorial. The API key and secret identify your personal integration. The login session is separate from those longer-lived credentials, so creating an app does not guarantee that every future sync can run without reconnecting.
Dhan's official authentication documentation distinguishes individual traders from partners and describes the available authentication methods. These steps cover the individual API-key flow supported by Jorli. Broker screens can change; if labels move, check the official guide and the setup instructions displayed inside Jorli before continuing.
1. Create your individual API app
- Sign in to Dhan Web and open My Profile → Access DhanHQ APIs.
- Select API key, rather than generating a temporary access token. Name the app something recognisable, such as My Jorli Journal.
-
Set the Redirect URL to
https://app.jorli.in/broker/dhan/callbackfor production Jorli. If you are using another environment, copy its exact callback URL from Jorli's Broker Sync panel. - Leave the optional Postback URL empty. Jorli fetches trades; this integration does not need order-update postbacks.
- Generate the API key and secret. Note your numeric Dhan Client ID as well, and keep all credentials private.
The redirect tells Dhan where to return after you finish authorisation. It is not the marketing homepage, the CLI documentation address or a URL you choose yourself. Match the protocol, hostname and complete callback path. Copying the URL directly from Jorli avoids a small typo turning into a confusing redirect error.
2. Save the credentials in Jorli
On the web, open Profile → Broker Sync → Set Up Dhan. If already configured, choose Edit API. Enter your own Client ID, API Key and API Secret, then select Save & Connect. On mobile, the corresponding controls are under More → Broker Sync. Jorli encrypts the saved broker credentials before storage.
Finish login and verification on Dhan's own page, then return to Jorli. Check that the connected Client ID belongs to you and that the displayed session is active. Enter your broker password or OTP only on the broker's login page. Never put an API secret in a journal note, support message, public post or repository.
3. Test a completed trade before enabling auto-sync
After closing a trade, choose Sync Now and inspect the resulting journal entry. The Journal Day broker button offers a preview where you can select trades and add details before importing. Broker sync imports today's fully closed date/symbol groups with equal bought and sold quantities. Open and partially closed positions are skipped, as are journal days marked No Trade Day.
Several fills for the same symbol on the same day can be aggregated into one journal row with weighted average prices. Repeated sync updates the existing Dhan record and preserves notes, tags and targets. A manually entered copy remains separate, so check for duplication if you have already typed that execution yourself. This is a journal import, not a complete holdings or tax reconciliation.
4. Understand the 4:30 PM schedule
Enable auto-sync if you want Jorli to attempt the weekday import at 4:30 PM IST, Monday to Friday. It requires a valid broker session at that time. Check the expiry and last result in Broker Sync. An enabled connection expiring before the scheduled run is eligible for an 8:30 AM IST reconnect reminder; a reminder does not itself restore broker access.
Dhan's API key and secret last 12 months in the documented individual setup. Sessions expire separately: use the expiry shown by Jorli and reconnect when required. Trading APIs are free; paid Data APIs are a separate offering and are unnecessary for this completed-trade sync. A free trading API does not remove the broker's normal transaction charges.
When something does not import
First check the account, session, auto-sync toggle and last sync result. Confirm the execution is from today, the bought and sold quantities match, and the day is not marked No Trade Day. A redirect mismatch calls for checking the exact callback; invalid credentials call for checking the key, secret and Client ID belong together. Reusing an old callback URL does not reconnect a session.
Jorli does not place or modify orders through this integration. The credentials themselves can have broader trading permissions, however, and should not be described as inherently read-only. Removing the saved configuration disconnects Dhan while leaving existing journal records intact. Reconnect after replacing credentials.
Prefer working in a terminal?
The free Dhan CLI is a separate terminal client with documented authentication and commands. Setting it up is optional and does not replace connecting Dhan inside Jorli. For another broker, read the Kite API setup guide. For costs, try the NSE charges calculator; for the review routine, see what to log in a trading journal.