How to Connect Bybit to TradingView (Webhooks)
Bybit doesn't have a native TradingView integration. You connect the two with a webhook: a TradingView alert posts a JSON message to TradingView Hub, which holds your Bybit API key and places the order for you. This guide walks the whole setup, from the API key to your first demo trade, in under 10 minutes.
Quick summary
- Bybit connects to TradingView through webhook alerts, not a native integration. TradingView posts a JSON message to TradingView Hub, which routes the order to Bybit.
- You need a paid TradingView plan. TradingView's free plan doesn't include webhook notifications, so it can't fire automated orders; webhook delivery starts on the Essential tier.
- TV-Hub itself is free when you open your Bybit account through the referral link. Already have a Bybit account? Subscriptions start at $23/month.
- Setup is three steps: create a Bybit read-write API key (third-party bind to tv-hub.org, no IP whitelist), add it to TradingView Hub, then paste the webhook URL and JSON into a TradingView alert.
- Test on Bybit Demo first (one checkbox, free) before you go live.
Bybit ranks as the third-largest crypto derivatives exchange by open interest (CoinGecko, accessed July 2026), so it's a common target for automated TradingView strategies. Here's how the connection actually works, and how to wire it up without the usual mistakes.
How does connecting Bybit to TradingView actually work?
Bybit and TradingView have no native integration. You bridge them with a webhook: TradingView posts a JSON alert to TradingView Hub, which holds your Bybit API key and places the order. The webhook path delivers in seconds, against the roughly 60-second email fallback (TradingView Hub docs, 2026).
So there are always three parts in the chain, and it helps to picture them before you start.
TradingView never touches your funds; it only sends a message. Sizing, leverage, and order type all live in that JSON, and TradingView Hub turns it into a real Bybit order. The webhook anatomy post breaks down what each value means.
What do you need before you connect?
Three things: a Unified Trading Account on Bybit, a paid TradingView plan, and a TradingView Hub account. TradingView's free plan doesn't include webhook notifications, so it can't send orders to Bybit; webhook delivery starts on the Essential tier (TradingView pricing, accessed July 2026).
The TradingView Hub account is the one you can get for free. If you don't have a Bybit account yet, create it through our referral link and the bot stays free for as long as you use it. Bybit pays us a commission on that signup, and that commission is what funds the free access. Already trading on Bybit? Paid subscriptions start at $23/month, with discounts on longer terms.
New Bybit accounts default to "Classic" mode. TradingView Hub expects the Unified Trading Account (UTA), which keeps Spot, Futures, and Options under one balance. Activate UTA from your Bybit account settings before you create the API key, or the key won't have the right trading scope.
Which TradingView plan do you need for webhooks?
TradingView's free plan doesn't include webhook notifications, which is the mechanism this whole setup relies on. As of July 2026, the free plan includes 3 active price alerts, so you can watch a strategy by hand, but you can't fire an automated order from it. Webhook delivery starts on the Essential tier. There's no way around it: no webhook, no automated Bybit order.
How to create a Bybit API key for TradingView
Creating the key takes about two minutes. Log in to Bybit, open API, create a system-generated key, and bind it to tv-hub.org as a third-party app with Read-Write permission. Because it's third-party bound, no IP whitelist is needed, and Bybit expires the key after 90 days (Bybit API docs, accessed July 2026).
Most competitor how-tos still show the old IP-whitelist flow. Bybit's third-party binding replaced that for supported apps, so the current steps look like this.
- Log in at bybit.com, click your account icon in the top right, and open API.
- Click Create New Key, then choose System-generated API Keys.
- On the key form, select Connect to Third-Party Applications, type tv-hub.org in the application name field and pick it from the list, set permissions to Read-Write (Unified Trading, Contract and Spot trade), leave withdrawals off, then submit.
Bybit's own note on that page confirms the timing: keys not bound to an IP address stay valid for three months. That 90-day TTL matters later, because TradingView Hub doesn't auto-rotate the key and your alerts start failing the day it lapses (the rejections show up in the Activity Log). Copy the key and secret (Bybit shows the secret once) for the next step.
How do you send your first Bybit webhook from TradingView?
A working Bybit webhook needs only two TradingView fields: the Webhook URL (https://alerts.tv-hub.org) and a one-line JSON Message carrying your token, exchange, pair, and the order. In our own testing, the alert reaches TradingView Hub within seconds of the trigger. First, hand the key to TradingView Hub.
Open Account, Settings, API Keys in TradingView Hub, pick Bybit, and paste the key and secret you just copied.
Now build the alert. In TradingView, create an alert, paste https://alerts.tv-hub.org into the Webhook URL box (need the exact endpoint? see which webhook URL to use), and drop the JSON into the Message box.
The minimal Bybit webhook payload (annotated)
This is the smallest market-order payload that does something real on Bybit. It's the exact schema from our Bybit API key setup and payload reference, not a legacy example.
{
"token": "your-tvh-token",
"exchange": "bybit",
"pair": "BTCUSDT",
"isMarket": true,
"isBuy": true,
"units": 50,
"unitsType": "percentBalance",
"leverage": 5,
"marginType": "cross"
}
| Field | What it does |
|---|---|
token | Your personal TradingView Hub token, which authenticates the alert |
exchange | Routing target, bybit for the UTA futures identifier |
pair | Exchange-native symbol, BTCUSDT and not BTC/USDT |
isMarket | true sends a market order; false needs a price |
isBuy | true opens a long; use isSell: true for a short |
units | The size number, read together with unitsType |
unitsType | percentBalance means units is a percent of your balance |
leverage | Leverage applied to the futures position |
marginType | cross or isolated margin |
One field isn't in the payload above: apiKey. If you've stored a single Bybit key in TradingView Hub, it's selected automatically. Once you keep more than one Bybit key, add apiKey with the name you gave the key in the dashboard so the order routes to the account you mean.
TradingView strips newlines from the Message field, so compact JSON on one line is fine. For how the JSON message field works, the alert message format docs go deeper. Bybit has a few quirks of its own too, like the separate take-profit-attach flags for market versus limit entries and UTA-wide sizing, all covered in the Bybit exchange reference.
Ready to send your first live Bybit order?
Wire up a TradingView alert to your Bybit account and let the webhook do the rest.
Start Free TrialRead the Bybit docsHow do you test safely on Bybit Demo first?
Test on Bybit's Demo Account before you risk real money. It mirrors live prices behind a single checkbox, with no separate site or login, so you can validate the full alert-to-order path on paper. TradingView Hub demo trading is always free, including the prop-firm demo, with no referral required (TradingView Hub docs, 2026).
On bybit.com, open the Tools menu and switch on Demo Trading. Generate a demo API key the same way you made the live one, add it to TradingView Hub, and fire the same alert. The round trip is identical, just on paper.
Run your alert on demo and watch the orders land. Only swap in the live key once you've seen the full path work. If you want the difference between demo and the separate testnet spelled out, that's covered in a companion post on Bybit testnet vs demo.
How do you run a free Bybit trading bot?
You run a free Bybit trading bot by opening your Bybit account through TradingView Hub's referral link. Do that, and the full bot stays free for as long as you keep trading, with no separate subscription needed for the live connection.
Free here means the complete product: live webhook trading on Bybit, every exchange feature, and no time limit or trial clock. Bybit pays TradingView Hub a commission on that referred signup, and that commission is what covers your access, so the cost lands on the exchange, not on you. Already have a Bybit account you don't want to replace? You can run the same bot on a paid plan instead, starting at $23/month with discounts on longer terms. And demo trading stays free for everyone regardless, referral or not, so you can validate a strategy on paper before any of this matters.
Why isn't my Bybit webhook firing?
The most common Bybit webhook failure is an expired or wrong-permission API key that Bybit rejects. Bybit keys lapse after 90 days and TradingView Hub doesn't auto-rotate them (Bybit API docs, accessed July 2026). Check the Activity Log first: it records every inbound alert and the exchange's response, so it usually tells you exactly what broke. The Debug a Failed Trade Alert guide maps the common log entries to their fixes.
When we tested this on Bybit Demo, the first order that failed was almost always a Read-only key or an un-activated UTA. The table below is ordered by how often each one actually bit us, not alphabetically.
| Symptom | Likely cause | Fix |
|---|---|---|
| Alert fires, no order appears | API key expired (90-day TTL) or Read-only, rejected by Bybit | Recreate a Read-Write key; check the rejection in the Activity Log |
| Order rejected on a permission error | UTA not activated, or key lacks trade scope | Activate UTA in Bybit settings; recreate the key as Read-Write |
| 429 rate-limit response | Too many alerts firing too fast | Space alerts out; the retry backs off automatically |
| Nothing routes, "invalid symbol" | Wrong pair or exchange value | Use BTCUSDT (no slash) and bybit, lowercase |
| Nothing happens at all | Wrong webhook URL, or you're on the Free plan | Use https://alerts.tv-hub.org; upgrade to a paid TradingView plan |
| A limit order sits unfilled | Bybit's post-only default on limit entries | Expect maker-only behavior; adjust the price or use a market entry |
Work top to bottom. Nine times out of ten it's the key.
From a first trade to a full strategy
Once your first Bybit order lands from a TradingView alert, the hard part is done. From here you can layer on stops, take-profits, and multiple alerts, all through the same webhook. When you're ready to move past a single manual setup, the landing page on how to automate Bybit trades with TradingView covers the strategy side and the trade-command builder.
Keep testing on demo whenever you change the payload. The full referral walkthrough, with the fee schedule and signup screenshots, lives in a dedicated post.
Frequently asked questions
Do I need a paid TradingView plan to connect Bybit?
Yes. Webhook alerts require a paid TradingView plan. The free plan doesn't include webhook notifications, so it can't send orders to Bybit; webhook delivery starts on the Essential tier. As of July 2026, the free plan includes 3 active price alerts, which is enough to watch a strategy by hand but not to automate it.
Is TradingView Hub free to use with Bybit?
It can be. Open your Bybit account through our referral link and the bot is free for as long as you trade, because Bybit pays us a commission that covers your access. If you already have a Bybit account, paid plans start at $23/month. Either way, demo and paper trading stay free.
Does Bybit have a native TradingView integration?
No. You connect them with a webhook. TradingView posts a JSON alert to TradingView Hub, which holds your Bybit API key and places the order. TradingView itself never touches your funds or your key.
Is it safe to give TradingView Hub my Bybit API key?
You create a Read-Write key bound to tv-hub.org with withdrawals disabled, so it can trade but never move funds off Bybit. Because it uses third-party binding, no IP whitelist is required.
Can I test before risking real money?
Yes. Use Bybit's free Demo Account, which is one checkbox with real market prices. TradingView Hub demo and paper trading are always free too, including the prop-firm demo, with no referral needed.
Why isn't my Bybit webhook firing?
Most often it's an expired or Read-only API key that Bybit rejects, an un-activated UTA, or being on the TradingView Free plan. Open the Activity Log first; it logs every alert and the exchange response.
How long does a Bybit API key last?
Bybit keys expire after 90 days unless re-confirmed. TradingView Hub doesn't auto-rotate them, so re-create the key before it lapses; otherwise every alert fails on the rejected key until you swap it.
That's the full path: a webhook, a read-write key bound to tv-hub.org, one JSON message, and a demo run first. Get it working once, and every future Bybit strategy is just a change to the payload.