TradingView to Kotak Neo Copier: Simple Setup in 6 Steps

You've built the alert in TradingView. Now you want Kotak Neo to act on it without you at the keyboard. TPcopier handles TradingView to Kotak Neo with its Indian TvCopier, a Windows program that runs on your own PC or VPS. Each alert comes from TradingView to the program. Then the program places the order through Kotak's Neo Trade API, from the static IP you've registered with Kotak.

Before you start, gather three things. First, a TradingView plan that can send webhook alerts; TradingView offers webhooks on its paid plans. Second, access to Kotak's Neo Trade API. Third, a Windows machine with a static IP that stays on while the market is open, ideally with port 80 open to it. Kotak also has two habits that change how you write alerts, so read the next two sections before the steps.

What Kotak Neo needs each morning

You sign in to Kotak's API with a TOTP login each trading day. That one login returns two values: a trading token and a session id, which Kotak calls the sId. Both expire with the trading day, and the program needs both. Kotak checks them separately on every call, so one without the other fails like a dead token.

In the program, go to Accounts, press + Connect a broker and pick Kotak Securities (Neo). You'll see three boxes:

• Trading token: the token from the Neo TOTP login.
• Session id: the sId from that same login.
• Consumer key: from your Neo app registration, and optional here.

Then press Test the connection. A good answer reads "connected" along with the cash available on the account. A stale login shows "Kotak Neo refused the token or session id - both last one trading day". Sometimes Kotak answers with something other than a limits reply. In that case the message suggests the token or sId belongs to a different account.

Put a price in every Kotak alert

This is the Kotak habit that matters most. Kotak's trade API has no plain quote call; its market data comes over a websocket. So the app can only read a live price for something the account already holds. It gets that price from the position book.

That changes what an alert without a price does. At most brokers, Convert market signals into protective limits turns it into a LIMIT order 0.5% through the live price. At Kotak, a fresh entry has no live price to build from. The app then falls back to a plain market order.

The same gap switches off two other guards on new entries. Refuse if the price has moved more than can't compare prices it can't read. Also, Price to enter at: The live price has nothing to use, so it falls back to market too.

The fix is simple: give every Kotak entry alert a price, the option's premium. Keep Price to enter at on The alert's price. That way the order goes as a LIMIT at your number. One warning about {{close}}, though. On an index chart it's the index level, not the premium. The app refuses any option price above 20,000 for exactly that reason.

Set up TradingView to Kotak Neo in 6 steps

1. Take the demo key

Open the Indian Copier page on tpcopier.com and press Get the free demo. After sign-up, the TradingView copier's card in your account has Get my free demo key and the Windows download. The demo runs the whole app. Buying later happens through Binance Pay, and the demo key simply becomes lifetime. All sales are final, so try it first; the pricing page has the numbers.

2. Install, activate and register your IP

Install the program on the machine with your static IP and paste the key into its first screen. Its Dashboard shows the public IP it sends from, with a Copy button, so you can register the right address with Kotak. SEBI's framework has required that since 1 April 2026. Kotak describes its API on the Neo Trade API page; check there for fees and for how its TOTP login works.

The Dashboard and its Static IP band (example).

3. Add the Kotak account

Open Accounts, press + Connect a broker and pick Kotak Securities (Neo). Fill in the boxes as the morning section explains, then save and test.

A new Kotak Neo account: trading token and session id each day, consumer key optional (example).

4. Keep the entry on the alert's price

Scroll down to What this account does with an order. Leave Price to enter at on The alert's price, because the live price is the one thing the app can't read at Kotak. The same block holds Most lots in one order, which starts at 1.

One account's order block; Price to enter at sits at the bottom of the first column (example).

5. Open port 80 and copy the URL

With port 80 open, TradingView sends every alert straight to the program. On the program's TradingView page, press Allow port 80 in Windows Firewall, and Allow access if Windows asks about the network. At home, forward port 80 on your router to this PC; on a VPS, open it in the provider's firewall too. The page then checks, on this PC, that the program is listening on port 80, that the firewall rule is there, and which public address the machine has. On a home Jio or Airtel line TradingView usually can't reach the PC at all, because the address is shared, so use a Windows VPS with a static IP. Finally, copy the address under 1 The webhook URL, and keep it out of screenshots.

6. Build the alert in TradingView

Paste that address into the alert's Webhook URL, as TradingView's webhook guide shows. Then paste your JSON into Message, with a price in it. Plain text is refused.

How the app finds your contract in Kotak's scrip master

Kotak publishes its scrip master as one file per segment per day. The app reads the cash and derivatives files for NSE and BSE, plus MCX and currency. It re-reads them every six hours. Early in the morning, today's file may not exist yet, and on a holiday it never appears. So the app falls back to the file from up to four days before.

The file has quirks, and the app handles them. Strikes and tick sizes come in paise, so 2500000 means a strike of 25,000. Expiry dates count from 1980 rather than 1970. The app converts both before it matches your alert.

For shares, Kotak writes RELIANCE-EQ. You still write RELIANCE, and the app finds the -EQ row. For options, Kotak's own name looks like NIFTY26OCT25000CE. Never put that in symbol. Instead, write the underlying, the strike and CE or PE, and the app looks up Kotak's name. If part of the file failed to load, a "no such contract" refusal says so. That way you don't spend a morning re-checking a strike that was right.

An example alert for Kotak Neo

Here's an example of the format. It isn't a trade idea:

{
  "action": "BUY",
  "symbol": "NIFTY",
  "strike": 25000,
  "option_type": "CE",
  "lots": 1,
  "price": 96.5,
  "sl": 78,
  "source": "nifty 15m"
}

To close, send a second alert with the same contract and "action": "EXIT". The app reads the position book, adding today's fills to the carried-forward quantity. After that, it cancels any order still working on that contract and closes what's actually held. It matches by Kotak's trading symbol, so it closes the right strike.

Orders & P&L: running orders, the broker's own list for today, and what is held (example).

Products and order types at Kotak

Kotak's product codes map from the account's Product setting. Intraday goes as MIS. Delivery / carry goes as CNC on shares but NRML on options, because Kotak refuses CNC on an option. Order types are L, MKT, SL and SL-M. Validity is DAY, or IOC if you choose it.

Want the sl placed as a real order? Switch on Send the stop loss as a real order for the account. The app places it after the entry fills. Breakeven and trailing stops work while the position is open, since the position book has its price. If that price ever goes missing, the app leaves the stop where it is.

When Kotak says no

• "Kotak Neo refused the token or session id - both last one trading day": do today's TOTP login and paste both values again.
• "Kotak Neo has no NIFTY 25000 CE - check the strike is one the exchange actually lists": check the strike, and read the note about missing files if one follows.
• "... is not in the Kotak Neo cash list": the share name doesn't match Kotak's list.
• An HTTP 429 message: that's Kotak's rate limit, not a problem with the order, and it clears by itself in a second.

TPcopier's own set-up guide asks Kotak Neo users to place one small order first. Do that, then read the journal row in the program's Signal Feed before you trade size.

FAQ

How often do I log in to Kotak Neo for TradingView alerts?

Every trading day. One TOTP login gives you the trading token and the session id, and both expire with the day. Paste both into the account, then press Test the connection.

Why does TradingView to Kotak Neo need a price in the alert?

Kotak's trade API has no plain quote call, so the app can't read a live price for a contract you don't hold. Without a price, a new entry goes at market. With one, it goes as a LIMIT order at your number.

Is the consumer key required?

No. Every call runs on the trading token and the session id, so the program treats the consumer key as optional.

Can I trade Sensex options at Kotak Neo?

The app reads Kotak's BSE derivatives file as well as NSE's. So a Sensex option with its strike on the 100 step resolves like a Nifty one.

Does TradingView to Kotak Neo work if my PC is off?

No. The program has to be running to take each alert. A missed alert never trades later. Keep the PC or VPS on during market hours.

Start with one small Kotak order

Create a TPcopier account and take the demo key from the Indian Copier page. Then send one priced, one-lot alert and read the result. If your calls arrive on Telegram instead, see Telegram to Kotak Neo. The Indian brokers overview shows what the other nine brokers ask for, and the Indian TvCopier setup guide goes through the program screen by screen. The TradingView webhook copier for Indian brokers page explains what happens to a plain-text alert.

Risk warning: trading options and shares carries a high risk of losing money and is not suitable for everyone. Nothing here is investment advice.