Signal execution
Your signals,
executed under your limits
A signal is an instruction, not a trade. Between the two sits the risk engine: it takes the alert, sizes it against the limits on that account, and either sends the order or refuses it.
- 3
- sources — TradingView, Telegram, raw webhook
- Pre-trade
- every signal is checked before it reaches the venue
The path
What happens between the alert and the fill.
Four steps, and the third is the one most setups skip.
The alert arrives
TradingView webhook, Telegram message or a raw POST. Each carries a payload identifying the symbol, side and size.
It is matched to a strategy
The signal is bound to a strategy on a specific account, so the same alert can drive different accounts differently.
The engine checks it
Daily loss, drawdown and position limits are evaluated against that account right now — not against a snapshot from when the route started.
It sends, or it refuses
A passing order goes to the venue. A breaching one is refused and written to your event log with the rule that stopped it.
Duplicates and gaps
The failures that only appear with real money.
An alert delivered twice becomes two positions unless something upstream notices. A signal that fires while the market is closed has to wait or be dropped, and which one it does should be your decision rather than an accident.
Signals carry an identifier so a repeat is recognised as a repeat. If the venue state is unconfirmed after a disconnect, the route halts rather than guessing.
- Duplicate alerts are recognised, not executed twice
- Symbol names are mapped, so a correct signal cannot route to nothing
- An unconfirmed venue state halts the route instead of retrying blind
Sources
Where a signal can come from.
TradingView alerts
Point a webhook alert at your endpoint. Anything you can express in Pine can drive a route.
Webhook
Telegram channels
Parse a channel you already follow into structured orders, with the same limits applied.
Parsed
Raw webhooks
Post JSON from your own system. The payload shape is documented and stable.
Your own
Send a signal at a demo account first.
Fire your alert into a demo route and watch the engine size it, check it, and either send it or refuse it. Nothing real is at stake while you learn what it does.