Fyers Integration — Auto-Sync Your Trading Journal

Fyers positions itself as a technology-forward broker — Fyers Web and Fyers App for execution, simplified pricing, and a trader community accustomed to API-aware workflows. TradeLyser connects to Fyers so executed trades flow into journaling, strategy analytics, and weekly review without manual copy-paste from order books. This guide covers Fyers-specific authorisation, what sync includes for cash and F&O segments, quirks that trip traders migrating from other platforms, CSV fallback paths, and a practical TradeLyser workflow after the bell. New journalers should read What Is TradeLyser?; F&O-focused users should pair this page with NSE F&O journal guide. Feature depth: Auto-sync and Journaling product; broker status: Supported brokers.

Why Fyers traders use TradeLyser

Fyers gives clean execution and transparent dashboards; it does not track whether your breakout tag improved after you halved size, or whether revenge trades cluster on RBI days. TradeLyser fills that gap by syncing Fyers fills into a single journal with strategy board separation and discipline scoring. Fyers users who already think in APIs and automation adapt quickly — the win is consistency of review, not learning a new order window. Confirm your account type on Supported brokers before connecting.

Connect Fyers to TradeLyser

Fyers integration uses OAuth-style authorisation through Fyers’ third-party app mechanism — you log in with Fyers credentials, approve TradeLyser’s read access to trade history, and return to TradeLyser for the first import. Fyers may require app PIN or TOTP depending on your security settings.

• TradeLyser → Settings → Broker connections → Fyers (or Fyers tile on Supported brokers).
• Tap Connect; complete Fyers login on the redirect page.
• Enter PIN / 2FA as configured on your Fyers account.
• Grant read permissions for orders and trades — write access is not required for journaling.
• Return to TradeLyser; allow initial historical sync to finish.
• Validate last session: compare fill count with Fyers order book → Trades tab.

If you use multiple Fyers products (individual vs corporate), connect the ID that actually holds your NSE/BSE trading segment. Demat-only IDs without active trading will connect but import empty execution history.

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

TradeLyser imports executed orders from Fyers with symbol, quantity, transaction type, product code, timestamps, and charges when available. Fyers product codes map to intraday, margin, and carry-forward behaviour — use them to filter tags correctly.

Fyers Smart orders and basket features still resolve to individual fills in history — sync tracks economics, not parent order names. Partial exits on scalps appear as multiple rows; keep one strategy tag across legs of the same planned trade.

Fyers-specific quirks

• OAuth token lifetime: Fyers sessions expire; TradeLyser notifies you to reconnect — do it before Monday review, not after noticing a blank week.
• API rate limits on heavy expiry days: if sync lags, wait and retry off-peak; avoid duplicate CSV unless gap persists past T+1.
• Symbol naming on Fyers Web vs app: same underlying, consistent internal symbol in sync — trust imported symbol for tagging.
• Corporate action adjustments: occasional symbol changes need manual notes when comparing multi-year backtests.
• Fundamentals sidebar noise: Fyers UI mixes research with execution — journal tags belong in TradeLyser, not Fyers watchlists alone.
• Weekend crypto curiosity: Fyers crypto is separate from NSE sync scope — only connect the equity/F&O trading ID relevant to TradeLyser.

Fyers publishes API documentation publicly; traders sometimes expect custom scripts to replace journaling — scripts store fills, not discipline. Sync plus TradeLyser tags remains the lighter path for most retail users.

CSV fallback: Fyers reports export

From Fyers Web or app reports, export trade history or P&L CSV for the gap period. Import via TradeLyser CSV upload (see Auto-sync). Fyers export columns include trade date, symbol, buy/sell, qty, and price — map explicitly if headers differ from another broker’s export you used before.

Use CSV for archival backfill when moving years of Fyers history into TradeLyser for the first time, or when OAuth maintenance blocks API pulls for a known window. After backfill, rely on live sync to prevent drift.

TradeLyser workflow with Fyers

• Post 3:30 p.m.: trigger manual sync if auto-run has not fired; confirm trade count.
• Tag strategies while Fyers Web is still open for reference — not from memory on weekends.
• Log violation flags on winners and losers; Fyers green P&L does not mean rules were followed.
• Use weekly review to split MIS from NRML and index from stock F&O per NSE F&O journal guide.
• Leverage Journaling product discipline fields for pre-market max-loss notes.
• Monthly reconciliation: one random day vs Fyers tax P&L export for fee alignment.

Fyers traders comfortable with automation should still keep human review — sync removes entry friction; edge validation stays in your Friday checklist.

Common mistakes with Fyers + TradeLyser

• Assuming API-savvy broker means sync never needs re-auth — tokens still expire.
• Blending stock options with index options in one tag because both are “F&O.”
• Importing CSV weekly while OAuth works — double entries follow.
• Ignoring partial fills when sizing discipline — three scalps are three process checks.
• Using Fyers day P&L screenshot as journal substitute — no strategy separation.
• Deferring tags until expiry week ends — context lost, tags become guesses.