Connecting Indian Brokers

Without an integration, the Indian retail workflow has a seam in it. You analyse a chart in TradingView, decide on a level, then move to your broker's own terminal, search the same symbol again, and retype the price, the quantity and the stop. Every one of those retyped numbers is a place where a level you carefully identified can become a level you did not intend, and the seam adds seconds you may not want to spend during a fast move.

With an integration, the Trading Panel at the bottom of the chart switches from simulation to a live connection with your broker. The order ticket now reads its symbol, price and quantity from the chart in front of you, and pressing Buy or Sell hands that instruction to your broker over an authenticated connection. The broker does everything it always did — validates the order against your available margin, applies its own risk checks, routes it to the NSE or BSE, and reports the fill back. TradingView then reflects that fill in the Positions tab.

It is worth being precise about the direction of travel. Information flows both ways, but authority flows only one way. TradingView sends instructions; your broker decides whether to accept them. If you do not have the margin, the broker rejects the order and TradingView shows the rejection reason. If the exchange is closed, the broker rejects it. If your broker has a client-level risk block on a scrip, the broker enforces that block. Nothing about connecting TradingView bypasses a single control your broker already applies to you.

The practical effect is that the level you drew and the level you traded become the same level. Right-click a support zone you have marked on NSE:HDFCBANK, choose 'Trade at' that price, and the limit order carries the exact figure off the chart. Drag the stop-loss line to sit under a recent swing low and the working stop order at your broker is amended to that price. The analysis and the order stop being two separate acts of typing.

The list of brokers you can connect is not something you configure — it is a fixed list maintained by TradingView, built from the brokers that have completed TradingView's integration programme. You see it by opening the Trading Panel at the bottom of a chart and reading the broker selector. Whatever appears in that selector, in your account, today, is the authoritative answer for you. Anything written in an article, including this one, is a snapshot that can go out of date.

Indian brokers that have appeared in that selector include Dhan, Fyers, Angel One and Kotak Securities. That is a neutral factual list and nothing more: no ordering is implied, no assessment of any of them is intended, and this page does not compare their charges, their features or their service. Choosing a broker is a decision about your own circumstances and about terms that change frequently, and it is a decision to make from each broker's own current disclosures — not from a technical article about a charting platform.

If your broker is not in the selector, there is no workaround and no setting to enable. The integration requires work on both sides — the broker must build and maintain an interface that TradingView's Trading Panel can speak to — so its absence simply means that interface does not exist. You can still use TradingView for every piece of analysis and place your orders in your broker's own terminal; you just do not get chart-to-order routing.

One more structural point. A broker being in the list does not mean every one of its segments or order types is exposed through TradingView. Each integration decides what it publishes, so a broker might route NSE equity and NSE F&O but not MCX commodities, or might support market and limit orders but not a bracket. The Trading Panel shows you what is available once you are connected, and the broker's own integration documentation is the place to confirm the details before you rely on them.

The connection uses OAuth 2.0, which is the same delegated-authorisation pattern you already use when an app asks to sign in with your Google or Apple account. Its entire purpose is to let one service act on your behalf at another service without ever learning your password. Understanding the four steps it takes is what turns 'is this safe' from a feeling into something you can reason about.

Step one: TradingView redirects you. When you press Connect, TradingView opens a new browser window pointed at a web address belonging to your broker. Check that address bar before you type anything — the domain shown must be your broker's own domain. If it is not, close the window. This single check is the one that defeats the most common phishing pattern, and no legitimate flow will ever ask you to enter broker credentials on a page that is not served by your broker.

Step two: you authenticate at your broker. You enter your client ID, your password and your second factor — the OTP or TOTP your broker requires — on your broker's page. TradingView is not in this exchange at all. It cannot read the page, it does not receive the keystrokes, and it never learns the password. This is the structural reason the arrangement is safer than the alternative it replaced, where third-party tools asked you to hand over broker credentials directly.

Step three: you approve a scope. Your broker then shows a consent screen listing what it is about to allow TradingView to do — typically read your holdings, read your positions, and place, modify and cancel orders. This is the moment that matters, and it deserves to be read rather than clicked through. You are granting a defined set of permissions, and the list is what defines the blast radius if anything ever goes wrong. Approving it is your decision, and you can decline.

Step four: the broker issues a token. Instead of a password, your broker mints an access token — a long random string that means 'the holder of this may do the approved things, for this client, until it expires'. The token goes to TradingView, which stores it and attaches it to every subsequent order instruction. Because it is scoped and time-limited, a token cannot be used to log into your broker's own app, cannot withdraw funds, and cannot transfer securities. And because your broker issued it, your broker can revoke it: every Indian broker exposes a list of connected applications in its own settings, and removing TradingView there kills the connection immediately, from the broker's side, without touching TradingView at all.

The click path is short, but it is worth walking through carefully once, because the same path is the one you will repeat every morning. Open a chart, then click the Trading Panel tab along the bottom edge of the window. A drawer slides up. If it opens as a thin strip, drag its top border upward. Inside it is the broker selector; open it and you get the list described above, with 'Paper Trading' sitting alongside the real brokers.

Select your broker and press Connect. The OAuth popup opens on your broker's domain. Verify the address bar, sign in with your client ID and password, complete the second factor, and read the consent screen before approving. Popup blockers are the single most common failure here — if nothing appears when you press Connect, your browser has silently blocked the window, and you need to allow popups for tradingview.com and try again. On the desktop application the same flow opens in an embedded window rather than a browser tab.

When the popup closes, the Trading Panel repopulates. You should see your account identifier, your available funds and margin, and — if you are holding anything — your existing positions synced from the broker, not from TradingView. That sync is the confirmation that the link is live in both directions. Before placing anything, glance at the account selector: some brokers expose more than one account or segment on the same login, and the panel places orders against whichever one is currently selected.

Reconnecting is the same sequence, and you will do it often. Indian broker sessions are deliberately short-lived — most tokens are invalidated daily, so a link established on Tuesday will not survive to Wednesday. The practical routine is to reconnect before the market opens rather than at the moment you want to trade: open TradingView shortly before 09:15 IST, run the connect flow, confirm the balance and positions have populated, and only then start working. A reconnection attempted during a fast move is a reconnection attempted at the worst possible time.

Finally, know how to disconnect. The same broker menu carries a Disconnect option, which drops the link on TradingView's side. If you want the permission itself withdrawn rather than merely the session ended, do it from your broker's connected-applications settings, because that is where the token actually lives.

Three separate settings decide what actually happens to an order, and Indian trading is unusual in requiring all three to be right. The segment says which market the instrument belongs to. The product type says how long you intend to hold it. The order type says how the fill is triggered. Get the second one wrong and a position you meant to hold for a month can be squared off automatically the same afternoon.

Segment first. NSE Equity covers cash-market stocks like NSE:RELIANCE, NSE:TCS, NSE:HDFCBANK and NSE:INFY. NSE F&O covers index and stock derivatives — NIFTY, BANKNIFTY and single-stock futures and options. BSE Equity covers BSE-listed cash. MCX covers commodity futures such as gold, silver and crude. NSE Currency covers pairs like USD/INR. Your broker enables these segments per client, which means an order can be rejected simply because the segment was never activated on your account — nothing to do with TradingView.

Product type second, and this is where the real money mistakes live. CNC (Cash and Carry) is delivery: the shares settle into your demat account and there is no forced exit. MIS (Margin Intraday Square-off) is intraday: your broker gives higher leverage, and in exchange it will square off anything still open near the end of the session, typically in the window before 15:30 IST — the precise cut-off is set by your broker, not by the exchange or by TradingView. NRML is the normal margin product for carrying F&O positions overnight to expiry, at full margin. If you enter with MIS intending to hold for weeks, the position closes itself that afternoon at whatever price the market happens to be.

Order type third. Market fills immediately at whatever price is available. Limit fills only at your price or better and waits otherwise. SL (Stop-Loss Limit) releases a limit order when a trigger price is touched; SL-M (Stop-Loss Market) releases a market order instead, which fills but does not guarantee the level. Bracket and cover products, where a broker offers them, bundle an entry with its exits. GTT (Good Till Triggered) is a broker-side standing instruction that waits for days or months rather than expiring with the session — it lives at your broker, so it survives even when your TradingView session does not.

Live orders only reach the exchange during market hours: 09:15 to 15:30 IST for NSE and BSE equity and derivatives, with MCX running a longer evening session. Outside those hours, whether you can queue an After-Market Order (AMO) at all, and until when, is entirely your broker's policy. If an order is rejected at 09:05 IST, the pre-open session is the reason, not the connection.

A TradingView alert can do more than notify you. Every alert can carry a webhook URL, which means that when the alert condition becomes true, TradingView sends an HTTP request containing a message you defined to an address you nominated. That is the whole mechanism — TradingView is a signal generator, and the webhook is how the signal leaves the platform.

TradingView itself does not place the resulting order. The address you nominate belongs to something else: your broker's own API endpoint if it accepts requests in that shape, or a middleware service that sits between the two and translates. The middleware receives the JSON payload shown above, maps the ticker and quantity into the format your broker's API expects, adds the authentication your broker requires, applies whatever safety limits you configured, and only then submits the order. There are three parties in this chain, and a failure at any one of them silently breaks it.

The pieces you write are the Pine Script that defines the condition, the alert message template that carries the fields, and the middleware configuration that turns those fields into an order. TradingView's placeholders — {{ticker}}, {{close}}, {{timenow}} — are substituted at fire time, so the payload describes the exact bar that triggered it. Note that an alert set to fire 'once per bar close' behaves very differently from one set to fire on every tick, and the difference is entire orders.

The risks here are structural rather than occasional. A condition that is true for many consecutive bars fires repeatedly and submits an order each time. A network failure between the middleware and your broker loses an exit instruction while the entry has already gone through. A Pine Script that repaints — one whose historical signals move as new data arrives — will look flawless in backtest and behave unrecognisably live. And an automated system will keep working while you are away from the screen, which is precisely what you wanted and precisely what makes it dangerous.

Almost every integration problem an Indian trader meets falls into one of five buckets, and each has a different fix. Working through them in order takes about a minute and saves the guesswork.

The first and by far the most common is an expired session. Indian brokers invalidate access tokens on a daily cycle as a security measure, so yesterday's authorisation is simply gone this morning. The symptom is a Trading Panel that still displays your account but rejects or ignores every order, sometimes with a 'session expired' or 'invalid token' message. The fix is to run the connect flow again, which is why reconnecting before 09:15 IST belongs in your routine rather than in your troubleshooting. This is designed behaviour, not a fault.

The second is a segment or permission mismatch. If an order on a NIFTY option is rejected while an order on NSE:RELIANCE goes through, the connection is fine and the F&O segment is not enabled on your account — a broker-side setting you change with your broker, not in TradingView. Read the rejection message the broker returns; it is usually specific about which permission is missing.

The third is a symbol that does not resolve. TradingView carries many symbols your broker cannot trade, including index values, continuous futures constructions and instruments from other exchanges. Always search with the exchange prefix — NSE:INFY rather than bare INFY — so you are on the tradeable listing. Newly listed scrips and contracts near a series roll can take time to appear correctly, and an expired option contract will chart but will never accept an order.

The fourth is a position or balance mismatch between TradingView and your broker's own app. The broker's app is always the source of truth. Disconnect and reconnect to force a fresh sync, then compare again. If they still disagree, stop placing orders through the integration and work in your broker's terminal until it is resolved — trading against a stale position view is how a hedge becomes a naked exposure.

The fifth is timing. Orders reach the exchange only within market hours, so a rejection at 09:05 IST during the pre-open, or at 15:35 IST after the close, is the session and not the software. Whether you can place an After-Market Order outside that window depends on your broker's policy. And if none of the five apply, check the obvious environmental causes before assuming a platform bug: a blocked popup, a browser extension interfering with the OAuth window, or a broker-side maintenance notice.