As of July 2026, connecting Angel One to TradingView comes in two very different flavours, and confusing them is the mistake I fix most often. The first is Angel One’s native TradingView broker integration — free, official, and used for placing orders manually from a chart. The second is full webhook automation, where a Pine Script strategy fires an alert that a bridge server turns into a live order through Angel One’s SmartAPI — no clicking required. Only the second is true “algo” automation. This guide is a dedicated, Angel One-only walkthrough of both, including the SEBI rules that changed on 1 April 2026.

In my 8 years building Pine Script strategies and broker bridges for clients across 14+ countries, the single most common Angel One question I get is some version of “I connected my Angel One angel TradingView algo account, so why don’t my strategy alerts place orders automatically?” The answer is that the native integration was never designed to. Let me untangle exactly what each path does, and give you working code for the automation path.

Angel One TradingView integration: what it actually is

Angel One is now a natively supported broker on TradingView. You can link your Angel One account directly inside TradingView and place, modify and track live orders from the chart itself. It is available to all Angel One clients at no extra cost; standard brokerage and exchange charges still apply.

Connecting takes under a minute:

1. Log into your TradingView account.
2. Open any chart and click the Trading Panel at the bottom (or the Buy/Sell buttons on the chart).
3. Select Angel One from the broker list and click Connect.
4. You are redirected to Angel One’s secure login; enter your credentials and authorise.
5. You are sent back to TradingView, now connected, and can trade from the chart.

Segments supported mirror what is enabled on your account: equity cash (NSE/BSE), NSE F&O, and MCX commodities, with BSE F&O flagged as coming soon. Orders placed on TradingView appear in your Angel One order and position book, and vice-versa — though some order types (OCO, AMO, scheduled orders) may not surface on TradingView. If something looks out of sync, Angel One’s own app is always the source of truth.

Here is the critical limitation: this native integration is manual. You still click Buy or Sell. It does not read your Pine Script strategy() signals and fire orders on its own. For hands-off automation you need the webhook path below.

Native integration vs SmartAPI webhook automation

If you also trade Fyers alongside Angel One, my older combined walkthrough on the TradingView to Angel One & Fyers webhook setup covers the two-broker angle; this article stays deliberately Angel One-only and goes deeper on the 2026 SmartAPI specifics.

How the SmartAPI webhook bridge works

The automation chain has three links:

1. TradingView alert — your Pine Script strategy fires an alert whose message is a JSON payload, sent as an HTTP POST to a webhook URL.
2. Bridge server — a small Flask app (on a VPS with a fixed IP) receives the POST, validates it, and calls SmartAPI.
3. Angel One SmartAPI — the placeOrder call routes the order to the exchange under your account.

Step one, the Pine Script side. This is a minimal Pine Script v6 EMA-cross strategy that emits buy/sell actions:

//@version=6
strategy("Angel One Webhook Signal", overlay=true)

fastLen = input.int(9,  "Fast EMA")
slowLen = input.int(21, "Slow EMA")

fast = ta.ema(close, fastLen)
slow = ta.ema(close, slowLen)

if ta.crossover(fast, slow)
    strategy.entry("Long", strategy.long)
if ta.crossunder(fast, slow)
    strategy.close("Long")

plot(fast, color = color.aqua)
plot(slow, color = color.orange)

In the alert dialog, set the condition to your strategy and paste a JSON message like this (the secret guards against strangers spamming your endpoint):

{"secret":"YOUR_SECRET","action":"{{strategy.order.action}}","symbol":"SBIN-EQ","token":"3045","qty":1,"price":{{close}}}

Step two and three, the bridge. Angel One’s official Python SDK is smartapi-python (the SmartConnect class), and it authenticates with your API key, client ID, PIN and a rotating TOTP:

from flask import Flask, request, abort
from SmartApi import SmartConnect
import pyotp

app = Flask(__name__)

API_KEY  = "YOUR_SMARTAPI_KEY"
CLIENT   = "YOUR_CLIENT_ID"
PIN      = "YOUR_PIN"
TOTP_KEY = "YOUR_TOTP_SECRET"
SECRET   = "YOUR_SECRET"

def broker():
    obj  = SmartConnect(api_key=API_KEY)
    totp = pyotp.TOTP(TOTP_KEY).now()
    obj.generateSession(CLIENT, PIN, totp)
    return obj

@app.route("/angel-webhook", methods=["POST"])
def hook():
    data = request.get_json(force=True)
    if data.get("secret") != SECRET:
        abort(403)

    side  = "BUY" if data["action"] == "buy" else "SELL"
    order = {
        "variety":         "NORMAL",
        "tradingsymbol":   data["symbol"],
        "symboltoken":     str(data["token"]),
        "transactiontype": side,
        "exchange":        "NSE",
        "ordertype":       "LIMIT",     # MARKET is banned for algos from Apr 2026
        "producttype":     "INTRADAY",
        "duration":        "DAY",       # IOC is banned for algos
        "price":           str(data["price"]),
        "quantity":        str(data["qty"])
    }
    resp = broker().placeOrder(order)
    return {"status": "ok", "orderid": resp}, 200

if __name__ == "__main__":
    app.run(host="0.0.0.0", port=5000)

Notice the LIMIT order type and DAY duration. Those are not stylistic choices — as of the 1 April 2026 framework, MARKET and IOC orders are prohibited for algorithmic trading, so a bridge that hard-codes them is compliant by design. That is the kind of detail that separates a bot that keeps running from one the broker starts rejecting.

Want this deployed, monitored and SEBI-compliant end to end without touching a server yourself? WhatsApp me at +91 77352 68199 and I’ll scope it with you.

The SEBI & Angel One rules that changed on 1 April 2026

The API price is not what makes 2026 different — the compliance layer is. Angel One rolled out mandatory SmartAPI changes to align with the NSE/SEBI retail algo framework, effective 1 April 2026. If you automate through SmartAPI, these apply to you:

• Static IP is mandatory. API order execution is accepted only from your registered primary static IP. You register it in the SmartAPI dashboard via “Add App,” can add a secondary IP for redundancy, and may update it no more than once per calendar week. Orders from any other IP are rejected — which is exactly why your webhook bridge belongs on a VPS with a fixed IP, not your home broadband.
• 10 orders-per-second threshold (TOPS). Below 10 OPS per exchange/segment, your algo needs no individual registration and uses a generic exchange-provided algo ID. Above 10 OPS, the strategy must be registered with the exchange for a unique ID. Most single-strategy retail bots sit comfortably under this.
• No MARKET or IOC orders for algos — use LIMIT with DAY duration, as in the code above.
• Hosting. Retail algos should be hosted on the broker’s servers, with an exception for “tech-savvy” clients who host their own logic behind a registered static IP. Running your own Flask bridge on a static-IP VPS is the self-hosted route.

These rules are consistent across Indian brokers. I wrote a full checklist in my developer’s guide to building SEBI-compliant algos in 2026, and the mechanics closely mirror what I documented for Zerodha Kite Connect API pricing and rate limits — same static-IP and Algo-ID logic, different broker. If you want the full production build, that is exactly what my Pine Script development service delivers.

Frequently asked questions

What is the Angel One TradingView integration?

It is Angel One’s official broker integration on TradingView that lets you log into your Angel One account inside TradingView and place, modify and track live orders directly from the chart. It is free and works for NSE/BSE equity, NSE F&O and MCX. It is manual, though — it does not auto-execute Pine Script strategy alerts.

Does the Angel One angel TradingView algo account place trades automatically?

No. The native integration routes orders you click on the chart. For fully automatic execution of Pine Script strategy signals you need a webhook bridge that receives TradingView alerts and places orders through Angel One’s SmartAPI.

How do I connect TradingView to Angel One for automation?

Create a SmartAPI app to get an API key, run a small Flask bridge on a VPS with a static IP, and point your TradingView strategy alert (a JSON webhook) at that server. The bridge authenticates with SmartConnect and calls placeOrder. Working code is in the section above.

Is Angel One algo trading via SmartAPI legal in 2026?

Yes, provided you follow the framework mandatory from 1 April 2026: register a static IP, stay under 10 orders/second per exchange (or register the strategy above that), and avoid MARKET and IOC order types. Every algo order also carries an exchange-assigned algo ID.

Do I need a static IP for the Angel One SmartAPI?

Yes. Since 1 April 2026, API order execution is accepted only from a registered primary static IP; you can add a secondary IP for redundancy. A cloud VPS with a fixed IP is the standard way retail traders meet this requirement.

Ready to automate your Angel One strategy properly — compliant, reliable and hands-off? Message me on WhatsApp at +91 77352 68199.

Risk disclaimer: Trading and investing in securities carry a substantial risk of loss and are not suitable for every investor. Automated strategies can amplify both gains and losses. Nothing in this article is investment advice or a guarantee of returns. Verify all broker features, API behaviour and regulatory requirements directly with Angel One, NSE and SEBI before deploying capital, as these can change. Trade only with money you can afford to lose.