Which Exchanges Accept TradingView Webhook Signals?
The Honest 2026 List

Short answer: of the 15 exchanges people ask about most, only 6 have a real, exchange-hosted webhook or signal-bot product — Binance, OKX, Bybit, Bitget, Gate.io, and Phemex. Five of them — Binance, OKX, Bybit, Bitget and Phemex — say in their own docs that the feature is futures/perpetual only. Gate.io never spells out the market scope either way, but everything in its setup guide points at perpetuals too. Either way, none of the 6 documents spot as a supported market.

The other 9 get listed as “supported” constantly, in blog posts and SEO listicles alike. Almost always, what's actually being described is TradingView's own chart-trading “broker” feature — a different product entirely. This article checked every exchange's own help center and announcements directly (not search-result summaries) as of July 2026, so you can find out where your exchange actually stands before you build anything on top of it.

Three things keep getting called the same name

Before the list, the confusion needs untangling, because it's the whole reason this article exists. “TradingView + [exchange] integration” can mean three completely different products:

• (a) Native webhook / signal bot — the exchange itself generates a webhook URL, receives your TradingView alert, and places the order. No third party involved.
• (b) TradingView Broker integration — you log into your exchange account inside TradingView's Trading Panel and click buy/sell manually from the chart. There is no alert, no webhook URL, and no automation — it's a fancier order ticket.
• (c) Third-party bridge — a separate service hosts the webhook, receives the alert, and calls the exchange's API on your behalf using your own API key.

The 15 exchanges, checked one by one

Verified directly against each exchange's own help center, documentation, or official announcement, as of July 2026. Exchange features change without much notice — treat this as a snapshot, not a permanent guarantee, and re-check the exchange's own docs before you commit.

The mix-up that keeps happening

This is the part worth slowing down for, because it's where most published “supported exchange” lists get it wrong — not out of bad faith, usually just from skimming an announcement headline. Seven exchanges in particular get miscast as having native webhooks when their own official material describes something else:

• BitMEX — its own /tradingview page is about logging in and trading manually from the chart, plus Pine Script backtesting. A line in its FAQ mentioning “webhooks” is describing TradingView's generic alert feature, not something BitMEX hosts.
• HTX — HTX's own announcement calls this a “Broker” partnership. That's chart-trading, not a signal-receiving endpoint.
• Kraken — Kraken's own support article names third-party bot partners explicitly. There's no Kraken-hosted webhook to point at.
• Coinbase Advanced — Coinbase does have a feature literally named “Webhooks,” which causes a lot of the confusion. It pushes onchain notifications outward; it doesn't receive TradingView alerts to trigger trades.
• WOO X — WOO X's own blog names a specific partner, WunderTrading, for webhook automation. The WOO X-branded integration itself is the Trading Panel.
• MEXC — MEXC's own promotional post is easy to misread. Read closely, it describes a user building their own webhook receiver against MEXC's API — not MEXC shipping a signal bot.
• Hyperliquid — TradingView added Hyperliquid in July 2026 as a market-data feed only (charting), not a broker connection. There is no TradingView-side automation hook at all, native or otherwise.

For KuCoin, the honest answer is a little different from all of the above: no official KuCoin documentation describing a native webhook feature could be found at all — not a positive statement of what it offers instead. That's a meaningfully weaker basis than the exchanges above, where each has its own material describing what it does offer. Treat “KuCoin has no native webhook” as the best available reading of an absence of documentation, not a confirmed denial from KuCoin itself.

No native webhook on your exchange? Here's what actually closes the gap

For the nine exchanges above, TradingView-alert-to-order automation only happens through a third-party bridge: a separate service receives the webhook and calls the exchange's own trading API using your API key. That's not a downgrade by itself — a well-built bridge can be just as reliable as a native feature — but it does add a service in between you and your funds, so it's worth being deliberate about which one.

Two things matter most when picking a bridge:

• Non-custodial or custodial. A non-custodial bridge only ever holds your API key and calls the exchange's API with it — your funds never leave your own exchange account. A custodial one pools user funds into its own wallets, which is a fundamentally different risk profile (see the 2022 incident where a pooled-key platform leaked 100,000 API keys).
• What API permission it actually needs. A bridge that only ever needs to place and cancel orders should only ever ask for trade permission — never withdrawal.

TVSBot is one option in category (c): it currently connects seven exchanges — Binance, OKX, Bybit, Bitget, Gate.io, BingX, and Hyperliquid (Hyperliquid perpetuals only — Hyperliquid has no spot market on TVSBot). It's non-custodial: you paste in your own API key, and every order is placed directly against the exchange's API with that key — TVSBot never takes custody of funds. Of the 15 exchanges in the table it doesn't cover BitMEX, HTX, Kraken, Coinbase, Crypto.com, Phemex, WOO X, KuCoin or MEXC, so if your exchange is one of those, you'll want a bridge built specifically for it.

Checklist before you connect any API key to a bridge

• Trade permission only, withdrawal permission off. A signal bridge never needs to move funds out of your account — only to place orders. See our deeper walkthrough on scoping a Binance API key safely.
• IP whitelist enabled, if the exchange supports it. Several exchanges (Binance, KuCoin) make this mandatory the moment withdrawal permission is on, and recommend it even for trade-only keys.
• Confirmed the bridge is non-custodial — it relays your signal and calls the exchange API with your key, it never pools or holds your funds itself.
• Checked the exchange's own help center directly, not just a third-party listicle — as this article shows, broker-integration and native-webhook features get conflated constantly.
• Understood which market the webhook covers — no native example on this list documents spot support (five say futures/perp outright, Gate.io leaves it unstated), so don't assume spot is included.
• Know how long an unused API key stays valid before the exchange auto-expires it (commonly 14–90 days without an IP whitelist, varies by exchange) so a dormant strategy doesn't silently stop working.

Frequently asked questions