Dhan Integration — Sync F&O and Equity Trades to TradeLyser

Dhan has grown quickly among active traders who want a modern mobile-first stack with competitive F&O pricing and straightforward account opening. TradeLyser’s Dhan integration pulls your executed NSE and BSE trades into the same journal workflow Zerodha and Fyers users run — strategy tags, discipline scores, and F&O-aware review without maintaining a parallel spreadsheet. This page explains Dhan-specific connection steps, what sync covers for cash and derivatives, quirks that differ from legacy brokers, CSV fallback when API access hiccups, and how to wire Dhan fills into a repeatable TradeLyser routine. Start with What Is TradeLyser? if you are new; options-heavy books should read NSE F&O journal guide alongside this guide.

Why Dhan traders connect TradeLyser

Dhan’s app surfaces P&L and positions well for the trading day — it does not replace a structured journal with strategy-level expectancy, rule violations, or mentor-ready exports. Many Dhan users trade index options and intraday equity in the same account; without segment filters, a good month on Bank Nifty can hide a bleeding stock-options book. TradeLyser auto-sync from Dhan feeds the strategy board and weekly review loop described on Auto-sync and Journaling product. Confirm Dhan is listed and active on Supported brokers before you plan your first import week.

Connect Dhan to TradeLyser

Dhan connection uses TradeLyser’s broker authorisation flow tailored to Dhan’s API — you authenticate with the same credentials you use on the Dhan app or web, grant read access to trade history, and TradeLyser schedules periodic pulls. Exact screens may update as Dhan expands API coverage; the path always starts from TradeLyser broker settings or the Dhan card on Supported brokers.

• Log into TradeLyser → Settings → Broker connections → Dhan.
• Tap Connect — you are redirected to Dhan login (mobile OTP or password per your Dhan security setup).
• Select the trading account if multiple profiles exist; retail traders usually have one active trading ID.
• Approve read-only trade history permission.
• Wait for initial backfill; first sync may take longer on accounts with heavy F&O history.
• Cross-check yesterday’s closed P&L on Dhan against imported trade count before strategy tagging.

Ensure F&O segment activation completed on Dhan before connecting — equity-only accounts import cash fine but options fills stay empty until segment approval clears. If you recently enabled F&O, trigger a manual sync after activation rather than assuming historical options backfill is instant.

What syncs: cash, intraday, and F&O on Dhan

Imported rows reflect Dhan executions: symbol, side, quantity, execution time, product type, and fees when exposed by the API. Dhan’s product naming may differ slightly from Zerodha — focus on economic behaviour (intraday vs carry) when tagging, not label familiarity from another broker.

Dhan users often concentrate in Nifty and Bank Nifty weeklies — tag expiry week explicitly because the API will not. STT and brokerage on options sell-side can turn small gross wins into net losses; synced charges support honest weekly review per NSE F&O journal guide guidance.

Dhan-specific quirks

• Newer broker, evolving API: occasional delayed backfill after high-volume expiry sessions — retry sync next morning before CSV panic.
• Mobile-first account settings: segment toggles and bank linkage are in the Dhan app; connection fails silently if KYC or segment pending.
• Single-app habit: if you trade only from phone, fills still import — but verify AMO and GTT executions appear next session.
• Options chain speed vs journal lag: your journal updates on sync cadence, not tick-by-tick — tag after session, not between scalps.
• Pledge and MTF books: delivery trades with margin products may classify differently — note product type when tagging swing vs pure CNC.
• Holiday shortened sessions: half-day imports may batch oddly — reconcile count against Dhan order history.

Traders migrating from another broker sometimes expect identical CSV column names — Dhan exports use Dhan headers. Use TradeLyser’s mapping UI rather than assuming Zerodha Console column order.

CSV fallback when Dhan sync is unavailable

Download trade history or P&L export from Dhan’s reports section (wording varies by app version — look for tradebook, ledger, or transaction export). Select the date range missing from TradeLyser, export CSV, and import through the CSV path documented on Auto-sync. Match on execution time, symbol, and quantity to avoid duplicates when OAuth returns.

Use CSV for one-off gaps — closed account final export, API maintenance window, or pre-TradeLyser history deeper than API backfill. Do not run daily CSV if OAuth works; manual habit drifts within two weeks.

TradeLyser workflow with Dhan

• End of session: open TradeLyser after Dhan positions are flat; confirm sync timestamp.
• Assign one strategy tag per planned trade; multi-leg options share the playbook tag.
• Mark rule breaks while memory is fresh — Dhan’s green day can hide process violations.
• Use discipline diary fields from Journaling product for emotion tags on revenge sequences.
• Weekly: compare intraday vs positional tags; Dhan active traders often overweight index options — verify capital allocation.
• Share mentor view if applicable — permissioned access beats screenshots from Dhan P&L cards.

Treat Dhan sync as source of truth for executions; your edge lives in tags and review cadence TradeLyser adds. Re-auth when TradeLyser prompts — Dhan tokens expire like any OAuth integration.

Common mistakes with Dhan + TradeLyser

• Connecting before F&O segment approval, then assuming “sync is broken.”
• One tag for all index products — Nifty, Bank Nifty, and Finnifty have different volatility profiles.
• Reviewing gross P&L from Dhan dashboard while ignoring synced net charges on high churn weeks.
• Skipping sync verification on expiry Thursdays when API load peaks.
• CSV import without date-range overlap check — duplicates inflate win rate.
• Journaling only on red days — winners need violation tags too (oversize, late entry).