A test mode that records nothing
Every Strategy gets a validation mode that parses and checks an alert completely without storing a Signal. You can fire your Strategy at it as many times as you like while you get the alert configuration right.
Algo Providers
Your Strategy already generates the Signals. Triggon distributes them.
An Algo Provider runs a Strategy that produces its own entries and exits, and connects it to Triggon with a webhook. Commonly that is a Pine Script Strategy on TradingView, which is the most common way to send one. Triggon reads the request, not the sender: your own server, a Python or Node.js bot, or another platform that can send the same authenticated request works the same way. Each webhook becomes a Signal for your subscribers, recorded permanently. The route is the same in every market; what differs is the account you trade at, the symbols you can declare and the backtest evidence you export, and each market has its own guide below.
Connection · test modeRecords nothing
✓BTCUSDT09:14 alert parsed · entry, stop, 2 targets · validated
✓ETHUSDT09:16 alert parsed · entry, stop, 1 target · validated
✗SOLUSDT09:18 refused: stop on the wrong side of the price for a long
✓SOLUSDT09:21 alert parsed · stop below entry · validated
Go-live gateReady to publish
Declared markets passed3 / 3
✓Connection confirmedeach market
✓Application approvedreason on record
✓Hub validPending to Live
✓Connection details privaterotatable any time
Sample. A Strategy cannot go live until every market it declared has produced a successful validation.
Five markets, five guides
Each guide is the whole route for one market: what to set up outside Triggon, which symbols you can register now, how the alerts reach Triggon, what evidence to export, what it costs, what the application asks, and what happens after approval. Open the one that matches your Strategy.
Algo · Crypto
Crypto Algo Provider guide
Exchange account, spot or futures symbols, your webhook, a TradingView backtest export. Enabled now: every symbol on Triggon's crypto list.
Open the guide → Algo · ForexForex Algo Provider guide
Where MetaTrader 5 fits, your broker, the pairs you can declare, your webhook, a TradingView or MetaTrader 5 report as evidence. Enabled now: 72 symbols (AUDCAD, AUDCHF, AUDJPY, AUDNZD and 68 more).
Open the guide → Algo · StocksStocks Algo Provider guide
US-listed symbols, the Reg-T leverage ceiling, market hours, alerts and evidence. Enabled now: shown in the application.
Open the guide → Algo · CommoditiesCommodities Algo Provider guide
Spot gold and metals as broker CFDs, the instruments you can declare, alerts and evidence. Enabled now: every symbol on Triggon's commodities list.
Open the guide → Algo · IndicesIndices Algo Provider guide
Stock indices as broker CFDs on the index level, the indices you can declare, alerts and evidence. Enabled now: every symbol on Triggon's indices list.
Open the guide →Not sure which market or whether Algo is your route at all? Answer two questions on the Become a Provider page → and Triggon shows you the roadmap for your exact combination.
The route, end to end
Step 01
Your Strategy
Whatever you already run, wherever you run it: a Pine Script Strategy on TradingView, your own server, a bot, another platform. You do not rebuild it.
Step 02
A webhook
Sent on the events your Strategy produces: entries, exits and the management in between. A TradingView alert is one way to send it; an HTTPS request from your own code is another.
Step 03
Triggon
Validates each alert, records it, and turns it into a Signal.
Step 04
Subscribers
Receive the Signal in Telegram, with your Strategy's record attached.
Step 05
Auto-Trade
Places it on the accounts of subscribers who enabled it, inside their own limits.
The same route in every market. Whether the chart is BTCUSDT, EURUSD, AAPL or
XAUUSD, the Signal reaches Triggon the same way: one authenticated webhook. Triggon does not
connect to your exchange, your broker or MetaTrader 5, and never asks a Provider for API keys
or a terminal login.
What Triggon accepts from an Algo Strategy
A full position lifecycle, not just entries. Everything your Strategy does to manage a trade can be expressed.
EntryOpens a position with its direction, price, stop loss and take-profit levels.
Add to positionA further leg under the open position, for a Strategy that scales in.
UpdateRewrites the stop loss and/or the targets on an open position.
Partial closeReduces the position by a share you specify, leaving the rest open.
Target hitRecords a take-profit level being reached and the share it closed.
Stop hitCloses the position at the stop, recorded like any other close.
CloseEnds the position and every leg under it.
One-way or hedgeOne direction at a time per market, or long and short simultaneously where the instrument allows it.
Sizing and leverage can travel with a Signal too. Both are treated as ceilings on the subscriber's side: a Signal can ask for less than a subscriber allows, never for more.
Connect the Strategy you already have
Triggon does not ask you to rebuild your Strategy inside Triggon, and it does not care which software runs it. It authenticates the request and reads the JSON. Anything that can send that request can be an Algo Provider.
Example
TradingView
Pine Script Strategy → TradingView alert → Triggon webhook → Signal. The most common route, and the one with the most worked examples. See TradingView & Pine Script.
Example
Your own code
Your server, a Python or Node.js bot, your own strategy engine → HTTPS POST → Triggon webhook → Signal. No TradingView account involved.
Example
Another platform
Any alerting or trading platform that can POST JSON to a URL you configure, with the fields below.
Compatible, not automatic. Triggon does not integrate with platforms; it
accepts requests. A system works if it can send an HTTPS POST with a JSON body carrying your
Strategy's secret and the required fields, at the moment your Strategy acts. A system that cannot do
that, or can only send fixed, unconfigurable text, cannot connect, whatever its name.
Test yours against your Hub's sandbox before you go live: it answers with the exact reason
anything is refused.
What the request has to be
| Part | What Triggon requires |
|---|---|
| Method | POST |
| URL | The webhook URL issued to your Strategy in your Provider Hub after approval, over HTTPS. It is private to your Strategy: it is not shown here and should not be shared. A per-symbol form is also issued, so one Strategy can send each declared symbol to its own URL. |
| Authentication | Your Strategy's secret, sent as a field in
the JSON body. Triggon compares it in constant time and refuses anything else with
unauthorized. |
| Body | A single JSON object. |
The fields every Signal carries
| Field | Required | What it is |
|---|---|---|
secret |
Always | Your Strategy's secret. Keep it out of public repositories and out of anything that runs in a browser. |
type |
Always | What happened. One of entry, update,
pyramid, reduce, close, tp_hit,
sl_hit, cancel. |
symbol |
Always | The market. Can come from the URL instead, on a per-symbol webhook; if both are present they must agree. It must be one of the symbols your application declared. |
ts |
Always | The time the Signal fired, as epoch milliseconds. Requests outside a few minutes of Triggon's clock are refused as a replay guard. |
price, sl, tp, size,
leverage, order type and the rest |
Depends on type |
An entry needs a price; a stop move needs the new stop. Your Hub's Connection tab documents the full set for your route and validates a real payload against it before you go live. |
Refusals are explicit. Triggon answers a bad request with a machine-readable
reason:
unauthorized, bad_type, bad_symbol,
bad_ts, asset_not_declared and so on, rather than failing quietly.
Your Hub keeps the log, so a Strategy that stops reaching Triggon tells you why.
Keep the secret secret. It is the only thing standing between your Strategy
and someone else publishing Signals under your name. Send it over HTTPS, keep it server-side,
never commit it to a repository and never put it in front-end code. If it is ever exposed,
rotate it in your Provider Hub.
Nothing goes live untested
Every declared market must pass
A Strategy cannot be published until it has produced a successful validation for each market it declares. An integration that works for one symbol and silently fails for another is caught here rather than by a subscriber.
Your connection is private and rotatable
Each Strategy has its own connection details and its own secret, both issued in the Connection tab of your Provider Hub and rotatable at any time. They are never shown on a public page.
Bad Signals are refused, not forwarded
A stop on the wrong side of the price, a target in the wrong direction, an unsupported order type, a stale timestamp: each is rejected at the door, before it can reach a subscriber's account.
Is the Algo route right for you?
Yes, if
You have a Strategy that already runs automatically, you can configure its alerts, and your problem is distribution rather than signal generation.
Consider Manual instead, if
You trade discretionarily, or your process involves judgement a script does not capture. The Manual route publishes to the same Marketplace and builds the same record.