Valid exchange and symbol values for webhook signals
New to webhooks? Start with How webhook signals work.
Most webhook signals must specify the exchange and the symbol (the market). These are the accepted values.
Exchange
Use either the exchange name or its Altrady code.
Spot exchanges:
| Exchange | Code |
|---|---|
| Binance | BINA |
| Binance US | BIUS |
| BingX | BNGX |
| Bitvavo | BVVO |
| Bybit | BYBI |
| Crypto.com | CRO |
| Gate.io | GATE |
| Coinbase | GDAX |
| HitBTC | HITB |
| HTX (Huobi) | HUBI |
| KuCoin | KUCN |
| Kraken | KRKN |
| MEXC | MEXC |
| OKX | OKEX |
| Poloniex | PLNX |
| WOO X | WOO |
Futures exchanges:
| Exchange | Code |
|---|---|
| Binance Futures | BIFU |
| BingX Futures | BNGXF |
| Bybit Futures | BYBIF |
| KuCoin Futures | KUCNF |
| Hyperliquid | HYPERLIQUIDF |
| Toobit | TBITF |
"exchange": "BIFU"
"exchange": "Gate.io"
"exchange": "KuCoin Futures"
Symbol
There are two ways to specify the symbol. Use the first unless you have a reason not to.
-
EXCHANGE_QUOTE_BASE(recommended) — Altrady’s own format, using the exchange code from the table above. It works on every exchange."symbol": "BINA_USDT_BTC" "symbol": "KUCNF_USDT_ADA" "symbol": "GATE_BTC_SOL" -
The exchange’s own API symbol (for example
BTCUSDTorBTC-USDT) — for coders familiar with API calls. It must match the exact format that exchange uses in its API, which varies by exchange.