Step by step
You log in on Angel One’s page, approve read access, and TradeLyser pulls executed trades from then on. Before you start, make sure the F&O and commodity segments are active. A demat-only or inactive trading ID connects but imports no trades.
Choose Angel One in TradeLyser
Go to Settings → Broker connections, pick Angel One and press Connect.
Log in on Angel One
Complete the Angel One or Spark login on the redirect page, with the OTP or 2FA your account uses.
Grant read access
Allow read-only access to orders and executed trades.
Let the first sync finish
Wait for the historical import to complete, and do not start tagging mid-import.
Check one session
Open Trades in the Spark order book for the latest session and match the row count and symbols.
What syncs from Angel One
What syncs
- Executed trades in delivery, intraday, futures and options
- MCX commodity trades, when the segment is active on your ID
- Smart, basket and cover orders, as individual legs
- Trades from Spark mobile and web alike, under one Client ID
What does not sync
- Files. There is no CSV or upload route for Angel One in TradeLyser.
- Trades on a dormant Angel Broking or demat-only profile
- Parent labels of smart and cover orders
- Expiry-week context. Add it as a tag.
How Angel One differs from the other guides
Sync only
One Client ID
MCX beside NSE
Old branding
Segments and how to tag them
| Segment | Angel One context | How to use it in TradeLyser |
|---|---|---|
| Equity delivery | CNC | Swing tags, kept out of intraday stats. |
| Intraday | Intraday products | Same-day round trips. Note square-off behaviour. |
| Futures | Index and stock futures | Separate tags for NRML and intraday futures. |
| Options | Single and multi-leg fills | Tag the playbook and add an expiry-week tag. |
| Commodity | MCX, where enabled | Commodity playbooks get their own tags. |
Expiry days are busy on Angel One, so fills can arrive in a batch a little after the bell. Smart, basket and cover orders resolve to individual executions. Partial exits on a scalp show as several rows; give them one tag.
Keeping a sync-only connection healthy
- Reconnect as soon as TradeLyser asks. With no CSV route, a lapsed token means missing days until you do.
- After 3:30 p.m., press Sync Now if the automatic run has not happened yet.
- If a day is still missing, retry on the morning of T+1 before contacting support.
- Keep a screenshot of the Spark order book on a disputed day, but treat the synced rows as the journal record.
- Corporate or HNI clients with several IDs should connect the one that holds daily NSE activity. A demat-only ID connects but imports nothing.

No CSV fallback for Angel One
Angel One has no file-upload route in TradeLyser, so the connection itself is your backup plan. When a day is missing, work through these in order.
- Check the Token column in Active Accounts. If it says expired, reconnect Angel One.
- Press Sync Now and give it a few minutes on busy expiry days.
- Retry on the morning of T+1.
- If the day is still missing, contact support with the session date.
Set a reminder to reconnect when TradeLyser emails you. Proactive reconnects beat discovering thin reports on Monday.
Trouble syncing?
Can I upload an Angel One CSV to TradeLyser?
No. Angel One works through sync only in TradeLyser. For a gap, reconnect and run the sync again.
Why did Angel One sync stop after a few weeks?
Access tokens expire. Reconnect from broker settings in TradeLyser. This is expected behaviour, not a broken integration.
Does sync include MCX commodity trades?
Executed MCX trades import when the commodity segment is active on your Angel One ID. Tag commodity playbooks apart from NSE F&O.
Should I connect the Spark app or Angel One web?
They are the same trading account. Connect once in TradeLyser, and fills from any device on that ID import on sync.
Are basket orders supported?
The individual executed legs import. Give all legs of one planned trade the same strategy tag.