How to Import Angel One Trades Into a Trading Journal

Connection and CSV boundaries

The repository contains an authenticated Angel One client and a trade-book request. The normaliser accepts order ID, fill ID, symbol, exchange, side, fill size, fill price and fill time, then derives an equity segment for NSE and BSE records while preserving other exchange values.

Treat this as TradeLore's current connection boundary. Verify Angel One's current workflow before operating it, and do not promise CSV export or a retention window that has not been confirmed.

What is imported

Valid records with identifiers, a symbol, a timestamp, positive quantity and price, and BUY or SELL direction become common TradeLore trade orders. The shared pipeline then persists them and matches executions. The repository does not justify claims about unlimited historical access or every Angel One segment, so confirm those from the current response.

TradeLore uses this data for journaling and analytics. It does not place, modify or cancel orders.

Troubleshooting and security

• Re-authenticate when credentials or the session are rejected.
• Check that fill ID, order ID, symbol, time, quantity, price and side are present.
• Compare source trade-book totals before repeating an import.
• Use the broker's credential controls to revoke access when needed.

What you need before connecting Angel One

The current Angel One workflow is not an OAuth redirect flow. It expects an Angel One SmartAPI key and a JWT token generated through the broker's login process. TradeLore settings explicitly says it does not store the client PIN/password or TOTP secret; it stores the SmartAPI key and JWT token needed for read-only trade-book requests.

The precise SmartAPI setup and token handling can change. Follow Angel One's current authenticated developer documentation and never publish credentials, PINs, TOTP codes or tokens.

Step by step: save access and sync

1. Create or open the SmartAPI app and copy its API key. 2. Use the current Angel One SmartAPI login process with your client code, PIN/password and TOTP to obtain a JWT token. 3. Open TradeLore Angel One settings and paste the API key and JWT token into Save Angel One Access. 4. Click Save credentials. 5. Click Sync Angel One. The server sends the key and bearer token to the trade-book endpoint and returns the sync result.

The current flow does not require a redirect URL. If the JWT is rejected or expires, generate a fresh token and save it again. Treat the token like a credential: do not paste it into a public note, screenshot or support ticket.

What gets imported and matched

The adapter reads the Angel One trade book and accepts rows with an order ID, fill ID, symbol, transaction type, positive fill size, positive fill price and a usable fill or update time. It preserves exchange, product type, expiry, option type, strike, symbol token and instrument type where the source provides them.

For NSE and BSE rows, the normaliser maps the segment to EQ. Other exchange values are preserved as the segment. Option type CE or PE is retained when present; a generic option instrument type without a clear option type should not be treated as proof of the exact contract. Stable broker, user, order and trade IDs are used before the shared pipeline matches the trade.

Verify Angel One's current source fields and historical availability before promising either in customer-facing material.

Errors, duplicates and security

• API key or JWT missing: save both values before syncing.
• 401/403 response: generate and save a fresh JWT token.
• No imported rows: compare required identifiers and positive price/quantity.
• Unexpected totals: reconcile order ID and fill ID with the trade book.
• Sensitive token exposure: revoke or replace the token through Angel One.

Validate the first Angel One sync

Use a known session containing one equity trade and, if relevant, one derivatives trade. Compare exchange, symbol, side, quantity, price and timestamp before reviewing P&L. Then add the plan and exit reason in TradeLore. Only after this check should you sync a broader period; the adapter reads the broker trade book and does not promise unlimited historical backfill.