Valid values for Exchange and Symbol
Exchange and Symbol (aka Market) must be specified in most webhook signals.
Valid values are set out below.
Accepted values for Exchange
Spot Exchanges:
- Binance or BINA
- Binance US or BIUS
- BNGX (BingX)
- Bitvavo or BVVO
- ByBit or BYBI
- Coinbase or GDAX
- Crypto.com or CRO
- Gate.io or GATE
- HitBTC or HITB
- Huobi or HUBI
- Hyperliquid or HYPERLIQUID
- Kucoin or KUCN
- Kraken or KRKN
- Mexc or MEXC
- OKEx or OKEX
- Poloniex or PLNX
- Woo or WOO
Futures exchanges:
- Binance Futures or BIFU
- BingX futures or BNGXF
- Bitmart Futures BITMF
- Bybit Futures or BYBIF
- Kucoin Futures or KUCNF
- Hyperliquid Futures or HYPERLIQUIDF
- Okex Futures or OKEXF
- Toobit or TBITF
e.g."exchange": "BIFU""exchange": "Gate.io""exchange": "Kucoin Futures"
Accepted values for Symbol
There are two ways to specify the symbol, and we recommend using the first method, unless there is a good reason for using the second.
- We recommend formatting the symbol as **
Note. The Exchange codes are listed above.
e.g."symbol": "BINA_USDT_BTC""symbol": "KUCNF_USDT_ADA""symbol": "GATE_BTC_SOL"
This format will work for all exchanges.
- If you are a coder, or familiar with using API calls, you can use the symbol format as used by the exchange API (e.g. BTCUSDT, BTC-USDT. This must be the format used by the specific exchange in their API calls, and it varies by exchange.
- You can also use the Trading View values
{{exchange}and{{ticker}}which will resolve correctly but must be used with the alternative variable names:"tv_exchange"and"tv_ticker"
in this way:
"tv_exchange": "{{exchange}}",
"tv_ticker": "{{ticker}}",
Related Articles
- Altrady's Webhook: Overview
- Webhook: Setting up the Signal Bot
- Webhook Signals: start or stop a Signal Bot
- Webhook Signals: Open, Increase, Reduce, Close or Reverse a Position
- Webhook Signals: Trading View Setup
- Webhook Signals: Testing and Errors
Updated on: 26/06/2026
Thank you!