What the connector does

The connector takes the strategy's alerts and places the orders on your own exchange keys. What it does, what it never does, and your plan's limits.

Applies to the Meanward Platform connectorOpen app
On this page

The connector (Meanward Platform) is the service between your TradingView alert and your exchange account. The strategy decides; the connector executes exactly what the alert says, on your own API keys, and reports every step to Telegram. I run my own account through it every day.

What happens to one alert

  1. TradingView sends the alert to the webhook URL of one of your exchange accounts. The connector acknowledges it at once and records it.
  2. It reads the command: open, average (an add), update (a new TP %) or close.
  3. The URL decides where it trades: that account, on its exchange. If the alert also names an exchange (?exchange=binance or an exchange field) and it's a different one, the signal is refused.
  4. It checks your plan and the account's position limits, then places a market order on that account.
  5. It reports the result to your Telegram chat and records it in the cabinet under Trades.

Per command:

CommandWhat the connector does
openChecks the per-side position limit, skips if a position on that pair and side is already open, opens at market, then places the TP order on the exchange at the TP % from the entry price.
averageAdds at market, then moves the exchange TP to the same % from the new average price.
updateReplaces the exchange TP with the new %, measured from the current average price.
closeCloses the whole position at market and cancels the TP order.

The TP lives on the exchange as a regular order right after the entry. If the connector goes down, the TP is still there.

What it never does

  • Never withdraws or transfers. The key you give it has no withdrawal or transfer rights, and the cabinet asks for exactly that.
  • Never trades on its own. No alert, no order. It doesn't open positions by itself, doesn't average by itself and doesn't place a stop loss on the exchange.
  • Never shows your keys. They're stored encrypted and aren't displayed again, to you or to me.
  • Never guesses an account. Each account has its own URL. An alert that names another exchange than its account's is refused with rejected_exchange_mismatch, closes included.

Your hard off switch is the API key: revoke it on the exchange and nothing can trade, whatever state the connector is in.

Exchanges

ExchangeStatusMarketKeysNotes
Binancelive, I run mine hereUSDT-M futuresAPI key + secretUses hedge mode for the whole futures account.
BybitcomingUSDT linear perpetualsAPI key + secretUses hedge mode, set per symbol.
HyperliquidcomingUSDC perpetualsWallet address + API wallet private keyNo hedge mode: one net position per symbol. USDC pairs only.

You can connect several accounts on one exchange, sub-accounts included: one key, one name and one webhook URL per account. Platform holds 5 accounts, Platform Expert 10. Coming means the connector supports the exchange, but it's switched off for everyone for now. It goes live with a release, and the changelog says when.

Hedge mode means a long and a short on the same symbol are two separate positions, which is how the strategy's long and short bots work. On Hyperliquid they can't coexist: an open against an existing opposite position is refused rather than silently netting it out. How to create each key: Exchange keys.

Plan limits

The plan you pay for decides what the connector executes. Closing is never blocked: a close or an update always goes through, so no position is left without its exit.

PlanopenaverageHedge
Clubrefusedrefusedrefused
Platformexecuted as sentexecuted as sentrefused
Platform Expertexecuted as sentexecuted as sentexecuted; the strategy sends hedge commands from v1.47, and hedging goes live with the next connector release
No subscription, or suspendedrefusedrefusedrefused

No plan changes order sizes: the connector sends what the alert says, so the cascade runs on the exchange as in your backtest. The plan only decides whether an order goes out at all.

Refused commands show up as statuses; see Execution statuses.

Position limits

Each account has a limit on how many long and how many short positions can be open at once: 5 and 5 by default. An open over the limit is refused with rejected_by_risk_limit; adds and closes aren't affected. Change the limits on the account's card under Accounts, or from Telegram with /set_long and /set_short (see Telegram bot).

Downgraded to a plan with fewer accounts than you have? The accounts added last, over the limit, stop opening new trades (rejected_account_over_limit). Their closes, adds and TP updates still go through.

Where to go next

  1. TradingView alert: one alert per chart, with your webhook URL.
  2. Exchange keys: what permissions to give, per exchange.
  3. Telegram bot: notifications and the emergency close.
  4. Execution statuses: what each result means.