Skip to main content

Supported Exchanges

TradingView Hub supports 6 exchange families. Each family covers one or more markets (Spot, Futures USD-M, Futures Coin-M) and may include separate testnet identifiers. The total: 16 distinct exchange identifiers routed by the Functions backend.

TL;DR
  • 6 crypto families with 16 distinct exchange identifiers
  • Default webhook URL: alerts.tv-hub.orgboth Binance Spot and Binance Futures use binance.tv-hub.org (see Webhook routing for details)
  • Demo trading is supported via two mechanisms: the Demo Account checkbox (Binance Spot, Binance Futures USD-M, Bybit Futures, Bybit Spot, OKX — 5 exchanges total) and separate testnet identifiers (Binance Futures USD-M + Coin-M, BitMex, Bybit)
  • Every exchange family has an affiliate sign-up link

Comparison matrix

ExchangeIdentifiersSpotFuturesDemo / TestnetAffiliate
Binancebinance, binance-futures, binance-futures-coin (+ testnets)✅ USD-M, Coin-M✅ Demo (Spot + USD-M) · Testnet (separate ids)Open account
Bybitbybit, bybit-spot (+ testnets)✅ Unified (UTA)✅ Demo + TestnetOpen account
OKXokx✅ Spot/Margin✅ Swap + Futures + Options✅ DemoOpen account
KuCoinkucoin, kucoin-spot✅ PerpetualOpen account
Coinbasecoinbase, coinbase-spot✅ Perpetual + ExpiringOpen account
BitMexbitmex (+ testnet)✅ Perpetual + QuarterlyTestnet (separate id)Open account
Prefer a Demo Account over a testnet

We always recommend testing on a demo account rather than a testnet. Demo accounts are real paper-trading environments: they run on live market prices and real liquidity, so fills behave like production. Testnets usually have little or no liquidity, so prices and fills are unrealistic. See Demo Accounts for the per-exchange setup.

For the exact symbol format, demo behaviour and feature matrix per identifier, see the Exchange Quirks Reference.

How to choose

If you want…Pick
Simple crypto spot tradingBinance Spot or Bybit Spot
High leverage crypto futuresBinance Futures (up to 125×) or Bybit Futures
Hedge mode / long + short on the same pairBinance Futures (hedgeMode: true), OKX (positionSide: long/short), or Bybit (no extra param — set the account to hedge mode and TVH routes each side automatically)
Coin-margined futures (collateral in BTC, ETH, …)Binance Futures Coin-M (binance-futures-coin)
Risk-free testingBinance Spot, Binance Futures USD-M, Bybit, OKX (Demo via checkbox) · Binance Futures / BitMex (separate testnet identifier)
US-regulated exchangeCoinbase (Spot + Futures)

Webhook routing per exchange

All exchanges send their TradingView alerts to one of two subdomains:

Exchange identifier(s)Webhook URL
Everything except Binancehttps://alerts.tv-hub.org
binance (Spot) and binance-futures (USD-M) — the TVH UI routes both Binance identifiers herehttps://binance.tv-hub.org
binance-futures-coin, binance-futures-coin-testnet, binance-futures-testnethttps://binance.tv-hub.org (same routing as live Binance)

The Binance subdomain runs in a separate Azure region with its own IP whitelist. The Functions backend routes Binance Futures signals onto a dedicated queue. alerts.tv-hub.org will also accept Binance signals, but the canonical UI routing sends both Binance Spot and Binance Futures to binance.tv-hub.org. Both endpoints also have a /api/ExecuteTradeSignalClassic "Classic" variant for low-latency strategies — see Webhook URLs & IP Whitelist.

Feature support deep-dive

Want to know which exchange supports trailing stops, scaled orders, multiple TPs, hedge mode, or sub-accounts? Jump to the Exchange Quirks Reference — it has a single scrollable matrix covering symbol formats, demo support, and feature flags across all 16 identifiers.

Universal setup pattern

Regardless of which exchange you pick, the connection flow is identical:

  1. Create an API key on the exchange (with IP whitelist).
  2. Add it to TVH at the API Keys page.
  3. Set the webhook URL in your TradingView alert.
  4. Place a trade and verify in the Activity Log.

The per-exchange differences (permissions to grant, passphrase requirement, sub-account handling, symbol format) live on each family's page. See Common Setup for the universal walkthrough.

Next steps