New Strategy

(no watch instruments yet — conditions can only reference what you add here)

(both times blank — no overnight hold; the strategy enters and exits the same day)

(overnight protection off — short legs carry the overnight gap unhedged)

(no legs yet — add one row per order)

(rules disabled — the position is never auto-adjusted)

(no combined wait — legs place as soon as the entry fires)

(set Combined SL above — preview rebuilds as you type)

(set Combined Target above — preview rebuilds as you type)

(enable trailing and fill Trigger / Step / Lock to arm it)

(set "when P&L reaches ₹" above to arm the profit lock)

(default execution — parallel legs, market entries)

Signal Configuration

Build your trigger

Sample bodies — copy & fill

{
  "signal": {
    "signal_type": "LONG ENTRY",   // the one field to always send
    "symbol": "TCS",                 // tradable root
    "fut_opt": "FUT",                // FUT (front month, auto-rolls) | CASH
    "qty": 2,                        // LOTS — the engine converts
    "sl": 30, "tgt": 50              // in the unit your strategy uses
  }
}

{
  "signal": {
    "signal_type": "ENTRY",
    "legs": [
      { "underlying":"NIFTY", "expiry":"current",
        "option_type":"PE", "strike_offset":0,
        "side":"SELL", "qty":1 },
      { "underlying":"NIFTY", "expiry":"current",
        "option_type":"CE", "strike_offset":0,
        "side":"SELL", "qty":1 }
    ]
  }
}
// strike_offset = ATM ± N strikes (needs strike_selection "relative"
// on the saved strategy). Replaces the saved legs — and their SL/TGT.

{ "signal": { "signal_type": "LONG EXIT" } }

// Closes the whole position. Add a qty to book only part
// of it and leave the rest running:
{ "signal": { "signal_type": "LONG EXIT", "qty": 1 } }

Every parameter you can send

One URL — the alert names its type

Quantity

• Send lots — the same unit you configured the strategy in. "qty": 2 means two lots; the engine multiplies by that contract's size before the order goes to the broker, so you never have to know it.
• On an entry, qty sets the size of every leg. On an exit it is optional: omit it to close the position, or send lots to release just that much and leave the rest running.
• Raw contract units — qty_units — for senders that would rather compute the size themselves. It skips the lot conversion entirely.
• Per-route multiplier. Each strategy row on the Signals page has a multiplier that scales the final quantity — the way to run one alert at 1× on one broker and 3× on another.

Repeat alerts

Placeholders — {{signal.*}}

What a webhook can and cannot change mid-trade

Scenarios — exactly what to pass

1 · Go long

{ "signal": { "signal_type": "LONG ENTRY" } }

// …or let the alert decide the instrument, size and risk:
{ "signal": { "signal_type": "LONG ENTRY",
              "symbol": "NIFTY", "fut_opt": "FUT",
              "qty": 1, "sl": 30, "tgt": 50 } }

2 · Go short

{ "signal": { "signal_type": "SHORT ENTRY", "symbol": "NIFTY",
              "fut_opt": "FUT", "qty": 1 } }

3 · Close the position

{ "signal": { "signal_type": "LONG EXIT" } }

4 · Book part of the position

{ "signal": { "signal_type": "LONG EXIT", "qty": 1 } }

// …or as a share of what is still open
{ "signal": { "signal_type": "LONG EXIT", "qty_pct": 50 } }

5 · Add to a winner (pyramid)

{ "signal": { "signal_type": "LONG ENTRY", "qty": 1 } }   // first add
{ "signal": { "signal_type": "LONG ENTRY", "qty": 1 } }   // second add

6 · Reverse

{ "signal": { "signal_type": "SHORT ENTRY", "qty": 1 } }

7 · Multi-leg — enter

{ "signal": { "signal_type": "ENTRY" } }

{ "signal": { "signal_type": "ENTRY", "legs": [
    { "underlying":"NIFTY", "expiry":"current", "option_type":"PE",
      "strike_offset":0, "side":"SELL", "qty":1 },
    { "underlying":"NIFTY", "expiry":"current", "option_type":"CE",
      "strike_offset":0, "side":"SELL", "qty":1 } ] } }

8 · Multi-leg — exit, whole or part

{ "signal": { "signal_type": "EXIT" } }             // close it
{ "signal": { "signal_type": "EXIT", "qty": 1 } }   // halve a 150-lot basket

9 · One alert, several brokers at different sizes

{ "signal": { "signal_type": "LONG ENTRY", "qty": 1 } }

// row 1 · Broker A ×1  →  1 lot
// row 2 · Broker B ×3  →  3 lots

10 · Change the stop or target on an open position

{ "signal": { "signal_type": "UPDATE", "sl_inr": 8000 } }        // basket ₹
{ "signal": { "signal_type": "UPDATE", "sl_inr": 0 } }           // breakeven
{ "signal": { "signal_type": "UPDATE", "leg": 0, "sl_price": 142.5 } }
{ "signal": { "signal_type": "UPDATE", "trailing": {
    "enabled": true, "trigger_inr": 25000,
    "step_inr": 5000, "lock_inr": 5000 } } }

11 · Wiring it in TradingView

// TradingView substitutes its own {{…}} placeholders before sending,
// so they can fill our fields. Numbers may arrive as strings; fine.
{ "signal": { "signal_type": "LONG ENTRY",
              "qty": "{{strategy.order.contracts}}" } }

Test it from a terminal

curl -X POST 'https://algo.fnotrader.com/api/webhook/sig/<signal-token>' \
  -H 'Content-Type: application/json' \
  -d '{"signal":{"signal_type":"LONG ENTRY","symbol":"NIFTY","fut_opt":"FUT","qty":1}}'

# → {"signal":"NIFTY breakout","started":1,"squared_off":0,"updated":0}
# The counts tell you what the alert actually did.
# Point it at a paper broker account first.

Equity Curve & Drawdown

Performance Metrics

Monte Carlo & Sequence Risk

Monthly PnL Calendar

Yearly Summary

Build & backtest by asking your AI

Connect Claude, ChatGPT or any AI assistant to FNOTrader MCP and describe strategies in plain English — the AI creates them and runs backtests on the same engine, data and credits as this app.

Your usage

Strategy level

Limits

Today's State