TradeBridge — User Guide

TradeBridge is a Windows application, and it runs on a Windows cloud machine — see Before you start for why that is required rather than optional. Minimum specification: 1 vCPU · 4 GB RAM · 50 GB HA NVMe. You can bring your own or use MyAlgoMate's cloud server.

Getting the installer. After your purchase, sign in to your MyAlgoMate account and open your subscriptions. Your TradeBridge subscription is listed there with a Download button.

1. Download the installer from that page.
2. Connect to your cloud machine (Remote Desktop).
3. Copy the installer across, run it, and start TradeBridge.

Sign in with your MyAlgoMate account. That is the email and password you registered with. These are not your broker credentials. You add brokers later, one account at a time.

Remember me is ticked to begin with. Leave it on and your email and password are saved on this machine, so the next start goes straight in. Untick it and nothing is saved. That choice sticks, so the box stays unticked next time too.

On first start the application downloads the day's instrument list. Until that finishes START stays unavailable and the footer reads Downloading instruments…. It happens once per day.

Figures shown in screenshots throughout this guide are sample data for illustration, not results.

Everything happens in one window.

• The menu bar — Session, Accounts, Portfolios, Strategies, View, Settings, Help. Everything you can do is in one of those.
• Seven tabs — Portfolio, Strategies, Legs Detail, Order Book, Position, A/C Management and Index Summary. Each answers a different question about what is happening.
• The log panel at the bottom, with Application Logs and Execution Logs.
• The footer shows internet and feed status, and the date and time.

The command bar carries the controls you will use most, and the badge that matters most.

In Paper mode the whole system runs. Signals arrive, contracts resolve and positions appear. No order reaches your broker.

Run a new setup in Paper first. It is the only way to watch a strategy behave end to end without money involved.

A/C Management lists every broker account you have added.

Each row carries its own controls: Login / Logout, Exit All for that account, RMS for its risk limits, and a … menu for the rest. They sit alongside its login status, P&L, funds, margin, risk caps and multiplier.

To add one, open Accounts ▸ Add Account… and pick your broker.

Enlarge

The same menu holds Login All Accounts, Login Selected, Auto Login on startup, and Save / Load Account Template… for moving a set-up between machines.

Every broker asks for something slightly different. Where you find those values is a question about your broker, not about TradeBridge.

So the dialog links straight out to the answer. Pick your broker and a How to get [broker] credentials link appears under the dropdown. It opens that broker's page on myalgomate.com, which lists the exact steps for that broker. If your broker has no page yet, the link reads Broker setup guides and takes you to the index.

The page opens in a TradeBridge window, not in your browser, so the steps sit beside the form you are filling in. Leave it open while you copy the keys across, and close it when you are done.

Every account starts with the same three fields: A/C Name (your own label), Client ID and Multiplier. The rest of the form then changes to match the broker you picked.

Most brokers ask for some combination of a password or MPIN, a TOTP secret, and an API key and secret that you generate in your broker's own developer portal. A few also want a vendor or dealer code, a base URL, or your date of birth.

The exact fields for your broker are listed on our brokers page: myalgomate.com/brokers. That page is kept up to date as brokers change their requirements.

Brokers running on the XTS platform share one longer form instead:

Enlarge

Market and Interactive API Key and Secret Key pairs, a Base URL, a User Type, and optional Hostlookup and Dealer Code.

Two sections at the foot of the form are shared by every account: Telegram alerts, and a Proxy if your network needs one.

Get the API key and secret from your broker's own developer or API portal. TradeBridge cannot create them for you.

Running several accounts does not mean running the same size on all of them, or assigning every account by hand every time.

Multiplier — sizing per account

Set it per account in the Add Account form; it is also a column in the A/C Management grid. The strategy's lot count is multiplied by it on that account.

Example. You build a strategy with 2 lots. On an account whose multiplier is 3, that account trades 2 × 3 = 6 lots. An account left at multiplier 1 trades the 2 lots as written.

That is how one strategy serves a large account and a small one at the same time — you size the strategy once and let each account scale itself.

Groups — assigning accounts without remembering them

A group is a named set of accounts. Open Accounts ▸ Group Manager….

Type a name, press Create Group, tick the accounts that belong to it, and Save Members.

Add an account to a group later and it inherits everything that group already runs.

Accounts must be logged in before you start the trading session — logging in is not available afterwards.

Each row in A/C Management also has its own Login / Logout button, and the Login Status and Login Message columns tell you what happened if one fails.

A portfolio is a group of related strategies. You assign accounts to the portfolio once, or a group of accounts. Every strategy inside it then runs on them. You do not repeat that assignment for each strategy.

Open Portfolios ▸ Create Portfolio….

1. Portfolio Name — must be unique. It is how executions are tracked and reported.
2. Run Portfolio For — choose Account or Group.
3. Tick the accounts or groups it runs on. The count of what you have selected is shown as you go.
4. Press Create Portfolio.

Because the accounts live on the portfolio, changing them moves every strategy inside it at once — which is the point. Build your strategies, drop them in a portfolio, and manage the account assignment in one place.

From the Portfolio tab and the Portfolios menu you can also:

• Activate / deactivate a portfolio with the toggle on its row.
• Exit Selected or Reset Selected for the whole portfolio at once.
• Fire a pending portfolio immediately by hand rather than waiting for a signal.
• Import Portfolios… and Export All Portfolios… — a backup, and the way to move a configuration to another machine.

Open Strategies ▸ Create Strategy…. The top band is the whole identity of the strategy.

##### The same form, three segments

The dialog changes with the segment. Three complete strategies, so you can see what yours should look like before you build it.

Equity — no Index: the symbols arrive from the scan. Chartink is the integration, the leg is an EQ buy, and the Trade limits box carries both equity caps.

Enlarge

Indices — Index: NIFTY is fixed for the life of the strategy, the leg is a CE buy with its strike chosen live, and there is one Max No of Trade.

Enlarge

MCX — the same shape as an index strategy, with Index: CRUDEOIL and the commodity's own expiry.

Enlarge

The times start out matched to the segment. A new Equity or Indices strategy opens with Stop Entry 15:00 and Exit 15:15, against the 15:30 close. A new MCX strategy opens with Stop Entry 23:00 and Exit 23:15, because commodities trade until 23:30. Switch the segment and the times move with it, unless you have typed your own. Your own times are never overwritten.

A leg is one instrument you trade. A short straddle is two legs; an iron condor is four.

Each row sets instrument type (CE / PE / FUT / EQ), buy or sell, size, how the strike is chosen, and its own Target, SL, Trail and Expiry. Copy a leg, delete it, or ADD LEG up to eight per side.

Only option legs are asked for a strike. Set a leg to CE or PE and you choose how its strike is picked. Set it to FUT or EQ and the strike box is switched off and shows a dash, because a future or a share has no strike. One strategy can hold a FUT leg next to a CE leg, and only the CE leg is asked. Switch a leg back to CE or PE and your earlier strike choice comes back.

Entry sides sits above the table: Long only, Short only, or Long and short. A new strategy starts on Long and short, so you see two tabs from the outset: Long legs and Short legs. Each has its own eight legs and its own counter. Fill in both, or switch Entry sides to Long only or Short only if you trade one way.

New legs already point the right way. A fresh leg is built from the segment and the side you are on. An untouched default is never the opposite of your signal:

Options express direction through the option being bought — a bought Call is a long view, a bought Put a short one, and both are BUYs. Futures and cash equity have no Put, so there the direction is the buy/sell itself. MCX starts on the future because commodities are traded that way far more often than through their options; the options are still there in the C/P column. These are starting points, not recommendations; change any of it.

Changing the Segment rewrites the legs you already have. It keeps their direction. A bearish leg stays bearish. SELL EQ becomes BUY PE when you move to Indices, and BUY PE becomes SELL EQ on the way back. It is the view that is carried across, not the buy/sell — so do not read a flipped B/S as a mistake.

Choosing the strike — evaluated live when the signal fires, never fixed in advance:

Tick Hedge and every leg gains a hedge configuration, pairing a short option with a long one for the margin benefit.

Sizing is fixed lots, or capital-based: give the capital plus a minimum and maximum lot count and TradeBridge sizes the leg to fit.

A strategy accepts long entries, short entries, or both — set by Entry sides, above the legs table. Choose Long and short and one strategy carries two leg sets, with one Max Profit and one Max Loss covering both directions. A new strategy starts here.

The two leg sets are independent. Each has its own eight legs, its own strikes and its own per-leg Target, SL and Trail. They share the name, the index, the schedule, the order settings — and, the point of the whole thing, one Max Loss and one Max Profit across both.

"Long legs" means the legs that fire on the long signal. It does not mean legs that are Buys. A bullish position is often a sold Put or a bought Call; a bearish one a bought Put. Read the tab as which signal starts this, and use the B/S column inside the table for the order side.

A worked example — NIFTY, both ways

Both legs are BUYs, and that is correct. On the long side you buy a Call, because you expect the index to go up. On the short side you buy a Put, because you expect it to go down. Nothing here is a recommendation — it is the simplest shape that shows how the two sides sit together.

One pair of URLs per side. With both sides on, the Webhook panel shows four URLs: LONG ENTRY, LONG EXIT, SHORT ENTRY and SHORT EXIT. Each is colour-coded, and the direction is written into the address itself, so a URL pasted into the wrong alert is easy to spot.

If you only trade one way, switch Entry sides to Long only or Short only. You get one leg table and one pair of URLs, exactly as before.

Many systems are always in the market. A buy closes the short and opens a long. A sell does the reverse.

Tick Stop and reverse and TradeBridge does exactly that. The option appears once Entry sides is set to Long and short. The opposite entry closes whatever side is open before it opens the new one, so you need no exit URLs at all.

The Webhook panel drops to two rows: LONG ENTRY and SHORT ENTRY. Two URLs, two alerts, for a system that is always in the market.

A worked example — always in NIFTY

1. Entry sides: Long and short. Tick Stop and reverse.
2. Long legs: BUY CE, ATM, 1 lot. Short legs: BUY PE, ATM, 1 lot.
3. Generate the two URLs. Put LONG ENTRY in your buy alert and SHORT ENTRY in your sell alert.

Now: your buy alert arrives, nothing is open, the long side opens. Your sell alert arrives — the long side is closed and the short side opens, from that one call. The next buy alert closes the short and opens the long again.

Three things to know before you rely on it:

• "No exit URL" is not "no exit". Exit Time, Max Loss, Max Profit and every per-leg SL still apply exactly as they do on any other strategy. The reversal is an additional way out, not the only one.
• The close is placed before the open. TradeBridge does not wait for it to fill. If the account is tight on margin, the new side can be rejected while the old one is still closing. Keep headroom, or use two separate strategies where you control the timing yourself.
• Turning it off gives your exit URLs back unchanged. They are hidden, not discarded — the same addresses reappear, so anything you had already pasted into an alert keeps working.

If you had generated exit URLs before ticking the box, TradeBridge says so and keeps them.

The ORDER SETTING tab controls how an order reaches the broker — separately for entry, exit and stop-loss orders, because they do not want the same treatment.

• Limit Price Ref — price the order off LTP, best bid/ask, immediate-fill or average bid/ask.
• Limit Buffer — how far through that price to sit, in percent or points.
• If Not Filled — revise the limit price or wait; set the interval and how many revisions before giving up.
• Order Rejection Retry — retry a rejected order N times at an interval you set.
• Place SL in Broker / Trail SL in Broker — push the stop-loss to the broker as a real resting order rather than holding it in the software.

The OTHER SETTING tab holds the finer execution rules — when exits are evaluated, how prices are rounded, and how strikes are selected.

Target and SL check frequency

How often the software evaluates whether a target or stop-loss has been reached.

Choose Live for tight intraday exits. Choose a timeframe when you want a candle to complete before acting, so an intra-candle spike does not take you out.

SL and Target reference price

Whether the level is calculated from the leg's real entry price, meaning the price actually filled, or from the LTP at the moment entry was triggered. They differ when there is slippage between the signal and the fill.

Wait for hedge to execute

When hedging is enabled, this makes the software place the hedge first and wait for it to execute before firing the main leg. Doing it in that order means the protective long is in place before the short goes on, which is what keeps the margin benefit. Without it the main leg can go first and the account is briefly exposed to full margin.

Ceiling for SL and Target

Rounds the calculated stop-loss or target price up to the next whole number.

Strike rounding

Rounds the selected strike to a multiple you set, separately for main and hedge legs — so the software only ever picks strikes that actually exist for that underlying.

Direction is configurable too: round Towards OTM, Towards ITM, or to the Closest strike.

Premium and delta match tolerance

When a strike is chosen by Closest Premium or Closest Delta, the nearest contract may not be an exact match. Set how close it must be, and what happens when nothing falls inside that tolerance: Avoid Entry, Keep waiting, or Wait for X seconds and then take the closest available.

The foot of the dialog counts your legs as you build. On a Long and short strategy it reads LONG LEGS: n | SHORT LEGS: n, with the buy/sell breakdown following for whichever side you are looking at. If a leg on the other side has a problem, its tab shows a red count. An error on a table you are not looking at cannot hide from you.

It also warns about things that are valid but rarely intended — a strategy with neither a max loss nor a max profit, for example, which will run uncapped. Fix what it flags, then ADD STRATEGY.

Your signal decides when to enter. The risk manager decides when to get out regardless.

*On a Long and short strategy these limits cover both sides together, not one each.* That is the reason to keep both directions in one strategy. You get a single Max Loss for the position as a whole.

Set here, these limits travel with the strategy — every account running it inherits them.

##### Trade limits, and why Equity has two of them

The Trade limits box changes with the segment, because an equity strategy and an index strategy are not counting the same thing.

An Indices or MCX strategy trades the one underlying you chose in the header. NIFTY is NIFTY all day. So there is a single control:

• Max No of Trade — stop taking new entries on this strategy after this many trades.

An Equity strategy has no underlying of its own. The symbols arrive in the alert, and one Chartink scan can return thirty stocks. Two different questions follow, so there are two controls:

• Max Trades per Stock — how many times this strategy will trade each individual stock. Set it to 1 and RELIANCE is entered once today no matter how many times the scan returns it; TCS still gets its own single entry.
• Max No of Stocks — how many different stocks the strategy will open in a day. Set it to 5 and the first five distinct symbols are traded; the sixth and everything after it is skipped, even though the alert arrived and was accepted.

Enlarge

A worked example. Your scan fires all day and returns 40 stocks between them. With Max Trades per Stock = 1 and Max No of Stocks = 5 you get five positions. They are the first five distinct symbols, with one entry in each. That is the configuration shown above.

Both are off until you tick them. Left unticked, an equity strategy keeps taking every stock the scan returns. That is right for a basket strategy and wrong for a small account.

A broker account usually carries several strategies at once. Account-level risk watches the account as a whole, whatever any individual strategy is doing.

Press RMS on any row of A/C Management.

Once set, the A/C Management grid shows the live state next to the settings: the account's running P&L, whether trading has been stopped, and the profit locked in. You can see a limit working, not just set.

Account limits and strategy limits are separate, and both apply. A strategy can be stopped by its own rule while the account keeps trading. An account limit can close everything on that account, whatever each strategy is doing.

Risk settings stay editable while trading is live, so you can always tighten one mid-session. Anything switched off reads Disabled rather than showing a stale number.

The widest of the three scopes. Global limits watch the combined position of every account together. A day that goes wrong across several accounts at once is still capped, even when no single account or strategy breached its own rule.

Open Settings ▸ RMS Settings.

Press Save RMS after any change — the screen tells you so.

A worked example. Set Max Profit to a figure and it is the total across all accounts that is measured. If three accounts are up and one is down, it is the net of all four that counts; when that net reaches your figure, all four are squared off together.

All three scopes run at once. Global, per account and per strategy limits are independent, and whichever triggers first acts. A strategy can be stopped by its own rule while everything else carries on, or the global limit can flatten the lot.

Unlike Index Settings and Telegram, RMS settings stay editable while trading is live, so you can tighten a limit mid-session.

Connecting a signal source needs three things in place. None of them is difficult, but missing one is the usual reason a first setup does not fire.

The signal listener lives inside TradeBridge. If the application is closed, nothing is listening and your signals are lost. The sender gets no warning. The same happens if the machine sleeps, restarts for updates, or loses power.

A cloud machine solves three problems at once. It stays on around the clock. It does not sleep or restart on its own. And its public address does not change, unlike a home broadband address, which changes and breaks the URLs you have already given to Chartink or TradingView. The address matters because Chartink and TradingView call in from their own servers — TradeBridge builds their URLs on your public address automatically.

Minimum specification: 1 vCPU · 4 GB RAM · 50 GB HA NVMe.

Bring your own, or use MyAlgoMate's cloud server, which comes ready for this.

2 · A paid plan on your signal source.

3 · An address your signal source can reach. Chartink and TradingView are cloud services, so they must reach your machine over the internet. On a cloud machine this is normally already the case — one more reason it is the supported setup. See Local IP or Public IP for what to check.

Everything after this assumes those three are done, plus a strategy built and the broker accounts connected.

Then read the chapter for your source, and only that one.

The three do not overlap. Setting up one does not require reading the other two. If a signal later arrives late, or does not arrive at all, When a signal is late or missing covers all three.

Your URLs live in the Webhook band of the Create Strategy screen, directly under the strategy details. How many you get depends on Entry sides, which you set above the legs table:

A new strategy starts on Long and short, so the four-row version is what you see first.

1. Give the strategy a Name first. The GENERATE buttons stay disabled until you do, because the name is built into the URL.
2. Pick your Integration — Chartink, Trading View or Custom. This tells TradeBridge how to read what arrives.
3. Press GENERATE on each row you need.
4. Press COPY and paste each URL into Chartink or TradingView, one at a time, checking the row label as you go.

Chartink and TradingView post from their own servers, so TradeBridge uses your public address for them automatically — there is nothing to choose. On Custom you also get a Public IP / Local IP switch, because your own code often runs on the same machine. See Local IP or Public IP.

A URL looks like this:

http://203.0.113.10:80/CI_S1_Long_Entry/a1b2c3d4-e5f6-4a7b-8c9d-000000000001/

Reading it left to right: CI_ marks it as Chartink (TI_ is TradingView, and Custom has no prefix). S1 is your strategy name. Long_Entry is the side and the signal type. The long code at the end is a token unique to that one URL. The direction is written into the address on purpose: with four URLs open in front of you, the path is the check that you are pasting the right one.

That token is also the only thing protecting the URL. Treat it like a password: do not post it in a screenshot, a forum, or a shared document.

The Public IP / Local IP switch decides which address goes into the URL. It is a real trade-off, not a formality.

You will only see the switch on Custom. Chartink and TradingView send from their own servers on the internet, and those servers can never reach a local address. So for those two TradeBridge uses the public URL and does not offer a choice that has only one right answer. Pick Custom and the switch appears.

Chartink and TradingView are cloud services, so they get the Public IP URL automatically. Your own code running on the same machine or network can use the Local IP one.

Three things worth knowing:

• TradeBridge adds the Windows Firewall rule for its port by itself. The router port-forward is the part you have to do.
• If your broadband address changes, the public URL you pasted stops matching and signals are dropped. A static IP or a dynamic-DNS setup avoids re-issuing URLs every time.
• You can publish the URL on a different port. TradeBridge listens on port 80. The port in the URL you hand out is yours to choose. That helps when a network blocks port 80 outbound. Forward the outside port to 80 on the TradeBridge machine. Then edit the port in the ENTRY and EXIT boxes to match what the outside world will call. For example, forward external 8080 → 80 and publish:

  http://203.0.113.10:8080/TI_NIFTY_LONG_Entry/a1b2c3d4-e5f6-4a7b-8c9d-000000000003/

The URL in the strategy must match what the caller uses, port included. TradeBridge matches an incoming call against the URL it has stored, so a strategy holding :8080 will not answer a call made to :80, and the reverse is also true. And remember that pressing GENERATE writes a fresh :80 URL — re-apply your port after any regeneration.

Plan this before you start creating things, because the number grows faster than people expect.

Neither Chartink nor TradingView sends a direction — their alerts say what and when, never which way. Direction comes from which URL you send the alert to.

One strategy holds both leg sets. Each set has its own LONG ENTRY and SHORT ENTRY URL, so you still send one signal per direction. See One strategy, both directions. The difference is that both sides now sit in one strategy, under one Max Profit and Max Loss.

Count signals, not strategies. Each direction you trade needs an entry signal, and normally an exit signal too. Stop and reverse removes the exit signals, because the opposite entry does the closing.

signals = directions × 2, per underlying — or signals = directions with Stop and reverse

An index or a commodity counts as one underlying. A whole basket of stocks also counts as one, because a single Equity strategy handles every symbol its scan returns.

The first two rows are the bargain: one pair of signals covers a basket of any size. The rest grow one strategy at a time. An index or commodity strategy trades only the underlying it was built with. You choose that in the Index dropdown, and the incoming signal cannot change it.

If your system reverses, so a buy closes the short and opens the long, you can halve these numbers. The simple way is Stop and reverse on a Long and short strategy: two entry URLs, no exits, no wiring. Sharing one URL between two separate strategies does the same thing and is still worth it when the directions need different settings, schedules or portfolios — see Reversal systems, next.

Name everything so the pairing is obvious. NIFTY Long Entry, NIFTY Long Exit, NIFTY Short Entry, NIFTY Short Exit takes a moment longer and saves you pasting the wrong URL later.

If you want a single signal to decide direction for itself, that is what the Custom JSON integration is for — it takes an explicit order side per leg. Chartink and TradingView cannot express it.

Many systems are always in the market: a buy closes the short and opens a long, a sell does the reverse. Two signals is all you need, and no exit signal at all.

Set Entry sides to Long and short, tick Stop and reverse, and configure just the two entry URLs:

That is the whole setup. No exit URLs to generate, none to paste, and nothing to keep in step — the opposite entry does the closing. If nothing is open when a signal arrives, it simply enters.

Two things to know before you rely on it:

• "No exit signal" is not "no exit". Exit Time, Max Loss, Max Profit and every per-leg SL still apply. The reversal is an extra way out, not the only one.
• The close is placed before the open. TradeBridge does not wait for it to fill. On an account tight for margin, the new side can be rejected while the old one is still closing. Keep headroom.

---

The older way: sharing one URL between two strategies. You do not need this for a plain reversal any more — use Stop and reverse above. It is still the answer when the two directions need genuinely different settings, schedules or portfolios, because then they have to be separate strategies.

A URL is not owned by one strategy. When a call arrives, TradeBridge checks it against every strategy's entry URL and every strategy's exit URL. Everything that matches acts on it. So the same URL can be one strategy's exit and another's entry.

Wire it like this, with a Long strategy and a Short strategy:

To do it, generate the URL on one strategy, press COPY, then open the other strategy and paste it into the opposite box instead of pressing GENERATE there. The URL boxes accept pasted text — that is what makes this possible.

Now one buy alert flattens the short and opens the long in a single call, and you maintain two alerts instead of four.

Three things to know about this technique:

• The exit is triggered first, then the entry. That ordering is on purpose, so a reversal closes before it opens. As with Stop and reverse, TradeBridge does not wait for the exit to fill before placing the entry.
• The URL keeps the name of the strategy it was generated on. A URL reading …/CI_MULTI_STOCK_LONG_Entry/… sitting in the Short strategy's EXIT box looks wrong and is not. Only the token identifies it.
• Regenerating breaks both ends. Press GENERATE on that URL and every strategy using it stops responding, not just the one you were looking at. Repaste it everywhere it appears.

Chartink drives Equity strategies. The Chartink option is available when the segment is Equity; for indices and commodities use TradingView or the Custom API.

Three details worth knowing. On an Indices or MCX strategy the Chartink button is still visible but disabled, with a tooltip saying why — it has not gone missing. If you switch a new strategy to Indices or MCX while Chartink is selected, TradeBridge moves it to Trading View for you. And a strategy already saved on Chartink keeps working and stays editable, whatever its segment.

Build the strategy with Segment: Equity and leave the symbol alone — there is no symbol to set, because it arrives with the alert.

Your scan returns a list, and TradeBridge enters every symbol in it from that one call. You do not need a scanner per stock, and you do not need to name the stocks anywhere in TradeBridge.

Enlarge

The Symbol column in those results is exactly what arrives, so the scan that returns twelve rows opens twelve positions.

Two consequences to plan for:

• There is no cap. If your scan returns forty symbols, TradeBridge attempts forty entries. Keep the scan tight, and size each leg on the assumption that several may fire together.
• A symbol already in the position is skipped, not doubled. If the same stock appears in a later alert while its leg is still open, TradeBridge logs that it was skipped and moves on.

Chartink does not send an exchange, so TradeBridge looks the symbol up on NSE and falls back to BSE. Symbols that are not listed on either are reported as not found.

Direction is set on the strategy, not in the scan. A scan names the symbols; the leg set decides the direction. One strategy can now hold both a long and a short leg set, each with its own scanner pair.

Each scanner needs its own alert, and each alert carries one TradeBridge URL.

1. Open your entry scan and press Create Alert.
2. Give it an Alert Name you will recognise later.
3. Paste the strategy's ENTRY URL into the Webhook box — the field that reads "Enter url/link for which a POST callback will be triggered on a alert". It is marked OPTIONAL; for TradeBridge it is the only part that matters.
4. Press Save alert, then repeat with your exit scan and the strategy's EXIT URL.

On a Long and short strategy there are four URLs, so paste by label. The long entry scan gets LONG ENTRY, its exit scan LONG EXIT, and the same for the short pair. With Stop and reverse on there are no exit URLs: two scans, two alerts, and the opposite entry closes.

The Schedule settings decide how often your signal can fire:

You do not need to tick anything under Delivery. Email, SMS and the rest are for you; the webhook is what reaches TradeBridge.

Enlarge

Name alerts after the signal, not after the strategy. Multi Stock ST Buy and Multi Stock ST Sell are better names than Entry and Exit. The same alert can be an entry for one strategy and an exit for another — see Reversal systems. If you only ever trade one direction, … Entry and … Exit are perfectly clear.

Leave Payload Columns alone. TradeBridge reads the standard fields Chartink sends — the list of stocks and their trigger_prices. If you have changed them, press View JSON and check both are still there before you save.

Chartink is always told the signal was received, even when TradeBridge rejects it. A green result in Chartink means "delivered", not "traded" — the app's own messages are the place to check whether anything happened.

Which is what Test webhook is for. Press it and the call goes to TradeBridge exactly as a real alert would, so you can watch it land in the execution log before market hours.

A TradingView alert needs three things from you: a condition, a Message, and a Webhook URL.

Open the Create alert on … dialog and set the top half as you normally would.

Enlarge

The four Trigger options

This one setting decides how often you trade and how quickly. Open the dropdown and you get:

Enlarge

Which one for which job

Once only — for testing, not for trading. You have just pasted your ENTRY URL and want to check it reaches TradeBridge. Set Once only, let it fire, look at the Execution Logs, then delete the alert. Do not leave it on a live strategy. It works on the first signal of the first day and never again, and TradingView gives you no warning. This is the usual answer when someone says "my alert worked once and then stopped".

Once per bar — when being early matters more than being sure. Your rule is "5-minute candle crosses above the opening range high". You want to be in as the break happens, not up to five minutes later. The catch: the candle is not finished. Price can cross at 09:47:10, fire your entry, and close back below at 09:50. You entered on a break that did not hold.

Once per bar close — the default, and the right one for most rules. Your rule is "the 5-minute candle closed above yesterday's high". The word closed is doing the work: until the candle finishes, the rule has no answer. Waiting is not a delay here, it is the rule. Use it for anything built on candle closes, moving-average crossovers, or indicator values.

Once per minute — a different signal, not an earlier one. This is the loosest of the four. It does not wait for the candle to finish, and it can fire again and again while your condition stays true. It is tempting to reach for this when your alerts feel slow. Be careful. It does not give you your candle-close signal sooner. It gives you a different signal. If your rule is "the candle closed above yesterday's high", this setting never checks that rule at a close. It checks your condition on a candle that is still forming. Three things to know before you switch:

• It keeps firing while your condition stays true, up to once a minute. One long move can send ten alerts, and each one is an entry.
• It reads an unfinished candle, same as Once per bar. Price can turn back before that candle closes.
• It is not the fix for a slow alert on a thin contract. See When your signal actually arrives for what actually causes that wait.

Still unsure? Use Once per bar close. It is the safest of the four, and the few seconds it costs on a quiet contract are explained in When your signal actually arrives.

The bottom two rows are the ones that matter, and both open their own panel:

1. Message › — replace the text with TradeBridge's JSON. See the next section; this step is not optional and TradingView's default text will not work.
2. Notifications › — tick Webhook URL and paste the strategy's ENTRY URL into the box beneath it. Its own description says it plainly: "Sends a POST request to your specified URL when your alert triggers."

Then press Create, and build a second alert the same way carrying the EXIT URL.

A TradingView alert carries no direction, so each direction needs its own alert pointed at its own URL. Running NIFTY both ways means four alerts: entry and exit for each side. All four sit on one strategy with Entry sides set to Long and short. Tick Stop and reverse and it drops to two, because the opposite entry does the closing.

Webhook alerts are a paid TradingView feature. If Webhook URL is missing from your Notifications panel, that is why.

TradingView pre-fills the Message box with a description of your condition — something like MA Cross (50, 200) Crossing Up MA Cross (50, 200) on {{ticker}}, 1W.

Delete all of it. That text means nothing to TradeBridge. Replace it with this, and nothing else:

{
  "symbol": "{{ticker}}",
  "exchange": "{{exchange}}",
  "time": "{{time}}",
  "timenow": "{{timenow}}"
}

The pieces in double braces are TradingView's own placeholders — it fills them in when the alert fires. You do not edit them, and you do not need the Add placeholder button; the four you need are already in the text above.

You can copy this text straight out of TradeBridge: set the integration to Trading View and press SAMPLE PAYLOADS.

Enlarge

Alerts on an index work exactly like the one above — the dialog is the same, you just open it on the index rather than on a stock. What changes is what TradeBridge does with it.

For an Indices or MCX strategy, the symbol in the alert is ignored. The strategy trades the index or commodity you chose when you built it, and the alert is a pure trigger.

So each index or commodity needs its own strategy — the underlying is fixed when you build it and no alert can change it. Within that strategy you need one alert per direction, plus an exit alert for each unless you use Stop and reverse. An alert placed on a BANKNIFTY chart pointed at a NIFTY strategy will enter NIFTY, and nothing will warn you, so keep each alert on the chart it belongs to.

Set the message to the standard JSON even for index alerts. It costs nothing and keeps every alert in your account identical.

For stocks you do not need an alert per symbol. Build a watchlist, then create the alert with the watchlist as its subject instead of a single chart — the dialog title reads Create alert on <your watchlist>.

Everything else is identical to a single-symbol alert, with one extra row: Session, which decides whether the condition is evaluated in regular hours only or extended hours too. Regular is what you want for Indian equities.

This works because of the message. {{ticker}} and {{exchange}} are filled in per symbol, so TradingView sends TradeBridge one call for each stock that triggers, each naming itself. Add a stock to the watchlist and it is covered; remove it and it is not.

The strategy behind it is an ordinary Equity strategy with no symbol set — the same one described in the Chartink stocks section. A symbol that already has an open leg is skipped rather than entered twice.

If you trade the same watchlist both ways, use two watchlists or two alert sets. Point one at the strategy's LONG ENTRY URL and the other at its SHORT ENTRY. The alert itself cannot say which direction it means.

Choose Custom as the integration when you have written your own strategy. Instead of TradeBridge inferring what to trade, you state it outright in JSON and POST it to the strategy's URL.

Press SAMPLE PAYLOADS in the Webhook band for a working example of every action, ready to copy.

Each leg in `STRATEGY_ENTRY` carries:

The ids are yours to choose, and yours to reuse

This is the part that catches people out. TradeBridge does not invent identifiers for you — your code supplies them, and every later call refers back to the same ones.

Both must be unique. Pick an id per strategy and an id per leg, store them on your side, and use the same values for the rest of that strategy's life. Send a new strategy id and you have started a new strategy; send an existing one and you are acting on the strategy that already exists.

Because OrderSide is stated per leg, one Custom URL can drive both directions — the only integration where that is true.

Sometimes your order goes in a few seconds later than you expected. Most of that wait happens before TradeBridge is involved at all. Here is where it goes.

TradingView only checks your alert when a trade happens

TradingView does not watch the clock. It checks your condition each time a new trade comes in for that contract.

• On a busy contract like NIFTY, trades arrive constantly. Your alert fires straight away.
• On a quiet contract, nothing is checked until the next trade. If nobody trades for 15 seconds, your alert waits 15 seconds.

That is why the same setup feels fast on one contract and slow on another. Your strategy has not changed. The number of trades has.

What it looks like in real numbers

Eleven alerts in a row on SILVERMIC, a 1-minute chart. SILVERMIC does not trade every second, so the wait changes from candle to candle:

Most arrived within a few seconds. The 16-second one is simply how long SILVERMIC went without a single trade.

!TradingView's alert log. The `time` inside each message is when the candle opened; the clock next to the alert name is when it was sent

Your Trigger setting decides when the alert fires

TradingView gives you four choices. They behave very differently. The full table is in TradingView — creating the entry alert; for timing, this is what matters:

Once per minute is not the fix for a slow alert. It does not wait for the candle to finish, so it can fire sooner. But it is answering a different question. It tests your condition on a candle that is still open, and it can fire again every minute. Read TradingView — creating the entry alert before you switch to it.

TradeBridge starts working when the alert lands

TradeBridge cannot see when your candle closed. The alert does carry a timestamp, but it is not used. All TradeBridge knows is when the message arrived, and it acts on it then. Your Start Time and Stop Entry Time are also checked against arrival time.

What can add a little more time

Usually milliseconds. Worth knowing when one particular entry looks slow:

Check it on your own account

1. Execution Logs — the Time column on the line that says the signal was received.
2. Order Book — the Place Time column for the order that followed.

The gap between those two is TradeBridge's share. Everything before the first one belongs to TradingView and the internet in between.

What you can do

• Trade the liquid contract. The near month, the near strike. Most of the wait is how often your contract trades, not software.
• Match the timeframe to the contract. A 1-minute candle on something that trades every twenty seconds will always feel slow. A 5-minute candle on the same contract will not.
• Expect the entry price to differ from the candle's close. The market keeps moving between the close that triggered your alert and the moment your order reaches the exchange.

TradeBridge writes what it did with every signal. Open the logs at the bottom of the window and switch to EXECUTION LOGS.

Two more, specific to a strategy that takes both directions:

• The right side traded, the wrong way round. Nothing looks broken. Entries arrive, orders go in and the log is clean. But the long alert is opening the short legs. The LONG ENTRY and SHORT ENTRY URLs got crossed when they were pasted. Compare the address in your alert against the one on screen: the direction is written into the path (…_Long_Entry… against …_Short_Entry…). This is the reason it is spelled out there.
• "Short Entry Webhook URL can't be Empty" when saving. A Long and short strategy needs a URL for each direction. Press GENERATE on the short entry row.

If nothing appears in the log at all, the call never reached the application. Work through this in order:

1. Is TradeBridge running and started? The listener only exists while the app is open and trading has been started.
2. Is the URL current? Renaming a strategy, or pressing GENERATE again, invalidates what you pasted earlier.
3. Public URL from a cloud service? Port 80 must be forwarded on your router, and your broadband address must not have changed.
4. Is it inside the trading window? Signals arriving before Start Time are ignored, and nothing new opens after Stop Entry Time.
5. Is the underlying ticked? An index or commodity that is not active in Settings ▸ Index Settings is skipped. The call arrives and the log says NAME is not enabled in Index Settings, but nothing trades.

Enlarge

START begins the trading session. Before it will do anything useful:

1. Instruments downloaded — the footer stops saying Downloading instruments….
2. Accounts logged in — use Accounts ▸ Login All Accounts. Logging in is not possible after START.
3. Indices enabled — tick what you trade in Settings ▸ Index Settings.
4. A portfolio active, with strategies inside it.
5. Mode checked — Paper or live, shown on the command bar.

The Setup Guide tracks all of this and links each step to the screen that fixes it.

After START, your webhook URLs begin listening and your strategies wait for their signal.

Each tab answers one question.

Portfolio — what is scheduled and what is running, with a per-portfolio execution tally.

Strategies — every live strategy, its status, P&L and risk state.

Enlarge

Legs Detail — one row per leg: symbol, side, quantity, entry and exit price, target, SL, trail.

Enlarge

Order Book — every order placed, with status and any rejection message.

Enlarge

Position — net positions by symbol, with LTP, bid, ask and delta.

Enlarge

A/C Management — the accounts themselves: login state, funds, margin, risk caps.

Index Summary — the underlyings you trade, with spot, futures and synthetic-future prices, the ATM strike, and your net position in each.

Enlarge

Every grid carries the same tools, and every change is remembered for next time.

• COLUMNS — show or hide any column and drag them into the order you want. The counter shows how many of the total are visible.
• Filter — a spreadsheet-style panel on each column header: search, tick the values you want, select all results, or clear.
• Freeze — keep the identifying columns in place while the rest scrolls.
• Pin actions — promote the row buttons you use most out of the … menu.
• Reset puts a grid back to its defaults.

There is an exit at every level, and each is one click.

Part Book on a strategy row books part of a position rather than all of it.

Part Book closes a portion of an open position and leaves the rest running under its original rules. There are three ways to reach it.

1 · The whole strategy. Open Part Book from the row actions on a live strategy in the Strategies tab. Every leg is booked proportionally — it works the same whether the strategy has one leg or a full set on both sides.

2 · A single leg. Do the same from a row in Legs Detail to book part of that leg only. The other legs are untouched and carry on under their own rules.

3 · From your own code. Send LEG_PARTIAL_EXIT to the strategy's webhook URL, naming the leg and how much to book. Useful when your strategy decides to scale out on its own.

Choosing the amount — the same two units everywhere:

• By Lots — the number of lots to close.
• By Percentage — a share of the open quantity, between 0 and 100.

In the JSON API these are LOTS and PERCENT, set as partbookType.

Whatever is left keeps its target, stop-loss and trailing rules, and the strategy stays live — so the remainder still manages itself and can still be exited normally later.

Open View ▸ MTM Chart… for the MTM Visualizer — mark-to-market plotted across the session rather than only the current number.

It opens as a window, not a dialog. Clicking elsewhere does not close it, so you can leave it running beside the workspace while you edit a strategy or watch the order book. Drag the title bar to move it, drag any edge or corner to resize it, and it reopens where and how you left it.

Reading the chart

• The filled area shows which side of zero the day is on — green above, red below.
• Move the pointer across it for a crosshair and a tooltip listing every visible line at that moment.
• The last leg is dashed with a pulsing head. That is the minute still forming: it tracks the live figure continuously and settles into a normal point when the minute closes. Hovering it labels it forming.
• Drag across the chart to zoom into a time range. Reset Zoom clears it.

Choosing what to plot

• Level — Global, Account, Portfolio or Strategy, as four buttons rather than a dropdown.
• Below Global, a second picker names what it is choosing: Account, Portfolio or Strategy. It also shows how many there are. It remembers your choice per level.
• The legend along the bottom is also the control: click a chip to show or hide that line. At least one always stays on.

Global MTM, High and Low run along the top with the time each extreme was set. Figures update every half second and the curve every couple of seconds — there is no refresh button because nothing waits for one. If the connection drops, the badge turns amber and the last curve stays on screen rather than blanking.

The live tracking on the last leg applies to the Global view. Account, portfolio and strategy curves move as each minute is recorded.

Open Settings ▸ Index Settings. This is where you choose which underlyings the software tracks.

The left panel lists NSE / equity indices — NIFTY, BANKNIFTY, FINNIFTY, MIDCPNIFTY, SENSEX and BANKEX. The right lists MCX / commodity indices — GOLD, GOLD M, SILVER, SILVER M, Natural Gas and Crude Oil.

For each row:

• Active Index — the tick that switches it on. Untick anything you do not trade to keep the feed and the grids focused.
• Expiry Date — the expiry this underlying uses, as a date, with DTE (days to expiry) beside it.

Every change saves as you make it — there is no Save button on this screen.

The screen becomes read-only once trading is live, and in that state each panel also shows a count of how many underlyings are active.

Set this before you press START. There is no way to unlock Index Settings during a live session — you would have to close and reopen TradeBridge. So if you have a strategy on, say, SILVER, tick SILVER now. TradeBridge checks for exactly this when you press START and warns you by name if an active strategy is set on an underlying that is not ticked.

Open Settings ▸ Telegram Alerts to receive updates away from the machine.

1. Send Telegram Alerts — the master switch.
2. Bot Token — from BotFather in Telegram, when you create the bot.
3. Channel Id — the channel or chat the bot posts to.
4. Live MTM Alerts — optional periodic updates rather than event alerts only.
5. Telegram Time Frame — how often those periodic updates are sent.

The settings are shared by every account, so this is configured once. Like Index Settings, they are read-only once trading is live, and reopening TradeBridge is the only way back in.

Open Settings ▸ General.

Settings ▸ Reset & Data clears stored state if you want to start clean. It is read-only once trading is live, so reopen TradeBridge if you need it. There is a separate reset per area rather than one blunt button.

Session ▸ Export All Grids… writes every grid to Excel in one step.

Individual grids export from their own controls, and Portfolios ▸ Export All Portfolios… saves your portfolio definitions — useful as a backup, or to move a setup to another machine. Account set-ups travel the same way through Accounts ▸ Save / Load Account Template….

The export follows the API's own column order and includes every column, not only the visible ones.

The panel at the bottom of the window shows one of two logs, chosen with the pair of buttons on the right of its toolbar.

• Execution Logs — what your strategies did: signals received, contracts chosen, orders placed, exits, and every skip reason. This is the one you land on, and the one to read when a strategy has not done what you expected.
• Application Logs — the application's own activity: logins, downloads, connection state.

Both are searchable and filterable by column, OPEN LOG shows the file on disk, and CLEAR empties the view. Settings ▸ General controls how many days of logs are kept.