Short answer: To connect TradingView to Bybit, OKX, Kraken or Coinbase, first choose between two different things. One is a broker link for placing orders by hand from the chart's Trading Panel; the other is webhook alerts that send a message to software that calls the exchange. TradingView's Help Center says automated strategy trading with a brokerage account is not available yet (read 4 November 2026), so automation needs the webhook route. The same Help Center says its alerts are not designed for automated trading. Neither route makes a strategy profitable, and automated orders can lose money.
People who ask how to connect TradingView to an exchange usually want either to click buy and sell on the chart, or to have their own alerts place orders while they are away. The two use different credentials, plans and failure modes.
This guide maps both for five platforms, from TradingView's broker pages and each platform's own documentation read on 4 November 2026. It does not rank or recommend platforms and has no referral links, and whether you may use any of them depends on where you live.
What does connecting TradingView to an exchange mean?
Connecting TradingView to an exchange means one of two things: a broker link for placing orders by hand from the chart, or webhook alerts that send a message to software that places the order, which can be the exchange's own or yours.
| Aspect | Broker link | Exchange's own webhook receiver | Your own bridge |
|---|---|---|---|
| Who sends the order | You, from the chart | The exchange's bot, on your alert | Your code, on your alert |
| What you set up | A sign-in on the exchange's page | A webhook URL and message template | A server, an API key and code |
| TradingView side | An account; Kraken accepts free or paid | Paid plan, two-factor authentication | Paid plan, two-factor authentication |
A broker link does not make alerts trade. TradingView's Help Center says automated strategy trading with a brokerage account is not available yet (read 4 November 2026), so a connected account and an alert remain separate things.
TradingView's Terms of Use (opens in a new tab), read on 5 November 2026, describe alerts and webhooks as licensed for display use and prohibit using them for automated trading, including through third-party products or services. Read those terms and take legal advice before relying on this route; it is your agreement with TradingView.
Which exchanges offer which route?
On 4 November 2026 Bybit and OKX documented all three routes, Kraken and Coinbase a broker link and an API, and Hyperliquid an API only, judging by the pages read for this guide.
| Platform | Broker link on TradingView | Exchange's own receiver | API for a bridge |
|---|---|---|---|
| Bybit | Spot, inverse, USDT and USDC perpetuals (Bybit help, 8 June 2026) | Webhook Signal Trading | V5 API |
| OKX | Spot and derivatives (OKX help, 30 September 2026) | Signal Bot | V5 API |
| Kraken | Spot and spot margin; futures listed as planned (Kraken support (opens in a new tab), 29 July 2026) | None found | Spot REST API |
| Coinbase | Coinbase Advanced: spot and derivatives as announced on 29 April 2025 (TradingView blog); Coinbase moved international derivatives (opens in a new tab) to a new gateway on 1 October 2026, so check what your panel offers | None found | Advanced Trade API |
| Hyperliquid | None found; TradingView's post of 2 July 2026 adds its market data to charts and does not mention orders | None found | HTTP API with wallet signatures |
None found means none in the pages read, not proof of absence. TradingView's Help Center refers to brokers displayed in the Trading Panel for your country (opens in a new tab), with a See all brokers button, so the first list you see can differ. Loaded from Turkey on 4 November 2026, its brokers directory showed 12 names, without Kraken or Coinbase Advanced, although both have profile pages. A directory entry is commercial information, not a statement that a platform may serve you.
How to connect TradingView to Bybit, OKX, Kraken or Coinbase for chart trading
On all four, you open the Trade button or Trading Panel on a chart, choose the broker and connect by signing in to your exchange account.
- Bybit. You authorize on Bybit's login page, and Bybit's help page (8 June 2026) says the connection lasts 24 hours, a limit it attributes to TradingView.
- OKX. OKX's help page (updated 30 September 2026) has you choose a live or demo environment before Connect. For derivatives it asks for Single currency margin account mode and says you can't trade in TradingView from Multi-currency margin or Margin free.
- Kraken. Kraken's support pages say the link uses OAuth, so no API key is created, and that you need a verified account in a region where the integration is supported (opens in a new tab).
- Coinbase. TradingView's 2025 post says to use Coinbase credentials in the Trading Panel. It names no regions.
Every order on this route is one you place yourself.
TradingView webhook to Bybit or OKX: the exchange's own receiver
Bybit and OKX each run a webhook receiver, so an alert can reach them with no server of yours, within limits they set.
| Item | Bybit Webhook Signal Trading | OKX Signal Bot |
|---|---|---|
| Page date | Updated 3 March 2026 | FAQ updated 14 October 2026 |
| Products | Perpetuals and inverse futures | Perpetual contracts; no spot |
| Alert source | Strategies only, not indicators | Strategies, indicators and chart alerts (setup guide (opens in a new tab)) |
| Authentication | A webhook URL per pair, which Bybit says not to share | A signalToken in the message, matched to your signal; OKX's FAQ lists the URL as one fixed address per environment |
| Other limits | One-way mode; 5 strategies per symbol, 30 per account; signals later than max_lag (default 20 seconds) are not placed | Separate URLs for live and demo |
Both products are derivatives, which carry leverage risk, and OKX's TradingView page limits signal trading to jurisdictions where perpetual trading is legally supported. A spot alert therefore needs a bridge. So does a Kraken TradingView webhook: Kraken's TradingView pages describe manual trading and mention no webhook (read 4 November 2026), and the pages read for Coinbase and Hyperliquid mention none either.
What does TradingView require for webhook alerts?
Every webhook route starts with the same rules, read in TradingView's Help Center and pricing page on 4 November 2026.
| Item | Documented value |
|---|---|
| Plan | Paid plans, not the free Basic plan |
| Account | Two-factor authentication on |
| Ports | 80 and 443 only; no IPv6 |
| Timeout | Canceled if the server takes over 3 seconds |
| Source IP addresses | 52.89.214.238, 34.212.75.30, 54.218.53.128, 52.32.178.7 |
TradingView's Help Center also says its alerts are not designed for automated trading (opens in a new tab) (read 4 November 2026): a webhook is a notification, and acting on it safely is the job of whatever receives it. A hosted receiver meets the network rules for you; your own bridge has to meet them itself. The webhook bot guide covers the architecture, and TradingView webhook in Python has a tested receiver.
What changes per exchange in your own bridge?
The alert side stays the same, while the host, signature, order fields, client order ID and test environment change per exchange.
| Platform | Order request | Signing | Client order ID | Test environment |
|---|---|---|---|---|
| Bybit | api.bybit.com /v5/order/create (opens in a new tab): category, symbol, side, orderType, qty | HMAC-SHA256 or RSA over timestamp, key, recv window, body | orderLinkId, up to 36 characters | api-testnet.bybit.com |
| OKX | openapi.okx.com /api/v5/trade/order: instId, tdMode, side, ordType, sz | Base64 HMAC-SHA256 over timestamp, method, path, body; passphrase header | clOrdId, up to 32 alphanumeric characters | Same host, header x-simulated-trading: 1 |
| Kraken | api.kraken.com /0/private/AddOrder (opens in a new tab): nonce, pair, type, ordertype, volume | HMAC-SHA512 (opens in a new tab) over path and SHA256(nonce + data); increasing nonce | cl_ord_id: UUID (32 hex, dashes optional) or up to 18 characters | validate flag; Spot UAT (opens in a new tab) by request |
| Coinbase | api.coinbase.com /api/v3/brokerage/orders (opens in a new tab): client_order_id, product_id, side, order_configuration | ES256 JWT (opens in a new tab) per request, expires in 2 minutes | client_order_id; a reused ID returns the existing order | Sandbox (opens in a new tab) with static mocked responses |
| Hyperliquid | api.hyperliquid.xyz /exchange: action, nonce, signature | Wallet signature; docs recommend an SDK (opens in a new tab) | c (cloid), 128-bit hex | api.hyperliquid-testnet.xyz |
Python notes for each platform: Bybit API in Python, OKX API in Python, Kraken API in Python, Coinbase Advanced Trade API in Python and Hyperliquid API in Python.
Hosts also depend on where the account is. Bybit's guide (opens in a new tab) lists other mainnet hosts for some regions, such as api.bybit.eu for the EEA, where it says the API supports only third-party app connections for API broker users, and it says IP addresses in the US or mainland China get 403 Forbidden. OKX sends US and Australian accounts to us.okx.com and EU accounts to eea.okx.com. Coinbase's host above covers spot and US derivatives; international derivatives now use its separate gateway. This snippet builds a limit order body for each platform from one alert, with hypothetical values; the symbol is an example, not a recommendation, and nothing is sent. Signing adds the nonce on Kraken, and the nonce and signature around Hyperliquid's action:
import hashlib
import json
alert = {"alert_id": "BTCUSDT-60-2026-11-04T14:00:00Z", "side": "buy", "qty": "0.01", "price": "67250"} # hypothetical
cid = hashlib.sha256(alert["alert_id"].encode()).hexdigest()[:32] # 32 hex characters
side, qty, px = alert["side"], alert["qty"], alert["price"]
hl_asset = 0 # index of BTC in Hyperliquid's meta universe: read it at runtime
bodies = {
"bybit": {"category": "spot", "symbol": "BTCUSDT", "side": side.capitalize(),
"orderType": "Limit", "qty": qty, "price": px, "orderLinkId": cid},
"okx": {"instId": "BTC-USDT", "tdMode": "cash", "side": side, "ordType": "limit",
"sz": qty, "px": px, "clOrdId": cid},
"kraken": {"pair": "XBTUSD", "type": side, "ordertype": "limit", "volume": qty,
"price": px, "cl_ord_id": cid},
"coinbase": {"client_order_id": cid, "product_id": "BTC-USD", "side": side.upper(),
"order_configuration": {"limit_limit_gtc": {"base_size": qty, "limit_price": px}}},
"hyperliquid": {"type": "order", "grouping": "na", "orders": [
{"a": hl_asset, "b": side == "buy", "p": px, "s": qty, "r": False,
"t": {"limit": {"tif": "Gtc"}}, "c": "0x" + cid}]},
}
print(cid)
for venue, body in bodies.items():
print(f"{venue}: {json.dumps(body)}")Hypothetical example. The alert ID above hashes to abea6b708ca3e3e0e53a6774ada3ace1. Those 32 hex characters fit all five ID rules (Hyperliquid adds 0x), so after a timeout the bridge can look up the same order instead of sending a new one.
Three details break a naive mapping, all checked on 4 November 2026:
- Symbols. Public endpoints returned BTCUSDT on Bybit's testnet, BTC-USDT on OKX, XBTUSD on Kraken and BTC-USD on Coinbase, so keep a server-side table.
- Hyperliquid assets. The asset is an index from its meta response: BTC was 0 on mainnet but 3 on testnet, so read it at runtime.
- Price rules. Hyperliquid's tick page (opens in a new tab) allows 5 significant figures unless the price is an integer, so 67250.5 fails there.
Test environments differ too. With placeholder keys on the same day, Bybit's testnet answered 10003 (API key is invalid) and OKX's demo mode 50111 (Invalid OK-ACCESS-KEY). Coinbase's sandbox took our BUY body and returned its fixed SELL response, so it cannot validate order logic. Our Kraken signing code reproduced the test vector in its documentation. No Hyperliquid order request was sent, because that needs a wallet signature.
Whose alerts may drive a bridge, and where is it allowed?
Use alerts from rules you wrote yourself, on your own account, and check your jurisdiction and the platform's terms first.
- Your own alerts. A paid third-party signal feed changes the legal picture. ESMA's briefing of 30 March 2023 (opens in a new tab) (paragraph 12) repeats that a firm's automatic execution of third-party trade signals, with no further client action, counts as portfolio management under MiFID. ESMA's Q&A 2463 (opens in a new tab) (answer of 7 April 2025) applies that guidance, case by case, to identifying copy trading services under MiCA. Local rules differ, and this is not legal advice.
- Platform terms. Section 9.3 of OKX's API Agreement (opens in a new tab) (read 4 November 2026) requires written authorization for a SaaS platform, signal service or managed trading, and for executing orders for third parties. Read the equivalent terms of any platform you use.
- Your jurisdiction. In Turkey, Article 99/A of Capital Markets Law No. 6362 treats activity by foreign-based crypto-asset platforms directed at Turkish residents as unauthorized service provision, and the Capital Markets Board says (opens in a new tab) appearing on its operating list does not mean a firm is authorized. Elsewhere, availability also differs by product and country.
A wrong quantity executes as fast as a right one, automated orders can lose money, and backtests do not guarantee future results. Fincode's TradingView automation service builds bridges from alerts in the customer's own account and does not connect paid signal feeds; rules and trading decisions stay with the customer. Naming a platform does not mean Fincode built for it.
Frequently asked questions
How do I connect TradingView to Bybit?
For chart trading, choose Bybit in the Trading Panel, click Connect and authorize on Bybit's login page. For alerts, Bybit documents Webhook Signal Trading for derivatives, or you can run a bridge to its V5 API.
How do I connect TradingView to OKX?
Select OKX on the Trading Panel, choose live or demo and click Connect. For an OKX TradingView webhook, its Signal Bot takes alerts for perpetual contracts only, so spot needs a bridge to the V5 API.
How do I connect TradingView to Kraken?
Click Trade on a chart, select Kraken, click Connect and approve the OAuth sign-in; no API key is created. Alerts would need your own bridge to its AddOrder endpoint.
How do I connect TradingView to Coinbase?
Use the Trading Panel with Coinbase credentials, where it appears as Coinbase Advanced. Alerts need your own bridge to the Advanced Trade API, signed with an ES256 JWT.
Can I connect TradingView to Hyperliquid?
No broker link was found on 4 November 2026; TradingView's July 2026 post adds Hyperliquid market data to charts. Alerts can reach it through a bridge that calls its API with a wallet signature.
Sources
- TradingView Help Center: How to configure webhook alerts (opens in a new tab)
- TradingView Help Center: How to autotrade using Pine Script strategies (opens in a new tab)
- TradingView: Brokers directory and broker profiles (opens in a new tab)
- TradingView: Plans and pricing (webhook notifications by plan) (opens in a new tab)
- TradingView Blog: Coinbase joins TradingView, 29 April 2025 (opens in a new tab)
- TradingView Blog: Trade[XYZ] and Hyperliquid data on TradingView, 2 July 2026 (opens in a new tab)
- OKX Help: How do I trade with OKX on TradingView? (opens in a new tab)
- Bybit Help Center: How to Get Started With Trading on Bybit From TradingView (opens in a new tab)
- Bybit Help Center: How to Use and Setup Webhook Signal Trading on Bybit (opens in a new tab)
- OKX Help: Trading Signal Bot FAQs (opens in a new tab)
- Kraken Support: How to connect your Kraken Pro account to TradingView (opens in a new tab)
- Bybit V5 API: Integration guidance (hosts, signing) (opens in a new tab)
- OKX API v5 documentation (hosts, demo trading, signing, place order) (opens in a new tab)
- Hyperliquid API docs: Exchange endpoint (opens in a new tab)
- Capital Markets Law No. 6362, Article 99/A (Turkish) (opens in a new tab)
This guide is general information about software and markets, not investment, legal or tax advice. Automated trading can lose money, past or backtested performance does not guarantee future results, and the rules that apply depend on your jurisdiction and your exchange's terms. Sources, checks and corrections: see the editorial policy.