Hyperliquid TradingView Guide: How to Automate Trades from TradingView to Hyperliquid (Plus Charts, Metrics and Alerts)

1. What TradingView can and cannot do with Hyperliquid

People who search “hyperliquid tradingview” mean five different things. Four exist today; one does not, and knowing which is which saves an afternoon of looking for a “Connect broker” button that is not there.

So automation always has the same shape: TradingView alert → webhook POST → relay → Hyperliquid exchange endpoint. TradingView decides when; the relay decides what order and signs it. Everything below is about making that chain reliable and cheap. For native, code-free automation inside Hyperliquid (TWAP, scale orders, trailing stops) see the Hyperliquid trading bot guide.

2. Step 1: account, referral code and deposit

Set up the account before any relay, for one reason most relay guides skip: Hyperliquid takes one referral code per account, only while your cumulative volume is at most $10,000, and a code cannot be changed once set. Several relays push their own during onboarding: TV-Hub (TVHUB), Gainium (a GAINIUM join link), WunderTrading (its “Sign up now” link carries WUNDERTRADING) and AstraBit (ASTRABIT, required for its Freemium tier). Decide which code you want first.

• What the code does: 4% off your trading fees on the first $25M of volume, so a base-tier taker fee of 0.045% becomes 0.0432%. It does not apply to sub-accounts. It does apply to orders that carry a builder code (the fee some relays add, section 12): the discount comes off Hyperliquid’s part of the fee and the relay’s builder fee is added on top (checked on mainnet fills on October 1, 2026).
• Deposit: USDC on Arbitrum is the standard route (every other way to deposit USDC is in our deposit guide); deposits under 5 USDC can be lost. Walkthrough with screenshots: how to use Hyperliquid.
• Check it worked: app.hyperliquid.xyz/referrals shows “You are using the code: …” once a code is set.

Our code is HOLYGRAIL (join link); the referral code guide explains the rules in full.

3. Step 2: create and manage the API wallet

1. Connect to Hyperliquid and open app.hyperliquid.xyz/API (More → API).
2. Type a name (for example tv-relay) and generate the API wallet. Set its validity; the maximum is 180 days.
3. Copy the private key when it is generated, before you authorise, and store it only in the relay or your server.
4. Authorise with a signature from your main wallet.
5. Note your master account address (the wallet you connected). Relays need it to read balances and positions; the API wallet address returns an empty account.

Managing expiry. An API wallet stops signing on its expiry date whether you use it or not, and a strategy that silently stops trading is worse than one that never started. Name every wallet after the relay that uses it, put the expiry date in your calendar a week early, and when it comes, generate a new wallet under the same name and paste the new key into the relay. An account can hold 1 unnamed and 3 named API wallets, plus 2 more per sub-account, so one wallet per relay is realistic. Do not reuse an old API wallet address; the docs warn its nonce state may be pruned. More: agent wallet setup and API key security.

4. Step 3: TradingView-to-Hyperliquid relays compared

A relay receives the webhook, turns it into a Hyperliquid order and signs it with your API wallet. We read each service’s own Hyperliquid and pricing pages on September 27, 2026. All of them connect with an API wallet (trade-only) rather than your main key. We have no relationship with any of them.

“None listed” = the pricing page names no builder fee. “Not stated” = not on the pages we read. TradersPost shows Hyperliquid as “Coming Soon”; goodcryptoX and TradingView To Anywhere did not load for us on September 27, 2026 (the latter’s forum guide describes Hyperliquid spot commands only), so they are not in the table.

How to choose. Builder-fee relays cost nothing until you trade and then charge on every fill; subscriptions cost the same whether you trade $1,000 or $1M. Section 12 has the arithmetic. Beyond price, ask three questions before you paste a key: does it accept an API wallet (walk away if it wants withdrawal rights or your seed phrase), what happens to an alert that arrives while it is down, and can you see the exact order each alert produced? Autoview’s page, for example, accepts “your HyperLiquid wallet secret key” with an optional API wallet address; give it the API wallet key, never the main one.

Builder-fee approval. A relay that charges a builder fee asks you to sign an ApproveBuilderFee with your main wallet (an API wallet cannot sign it). That caps what it may charge; Hyperliquid limits builder fees to 0.1% on perps and 1% on spot (not on the buy side of spot), and you can hold 10 approvals at once and remove them at app.hyperliquid.xyz/builderCodes. Background: builder codes explained.

5. Steps 4–5: the TradingView alert, message and JSON fields

Open a chart, ideally the Hyperliquid market itself (HYPERLIQUID:BTCUSDC.P), and create the alert from a price level, an indicator or a Pine strategy. Webhook notifications need Essential or higher (from $12.95/month billed annually; the free Basic plan has a cross in that row of the pricing table) and two-factor authentication on your TradingView account. On the free plan, TV-Hub documents one workaround: tick Send Email instead of Webhook and it processes the email the same way; Basic only has 3 price alerts (no indicator or strategy alerts), so this suits simple price-level entries.

1. Condition: the strategy (“Order fills only”), or the indicator with “Once per bar close” so a wick does not fire it.
2. Expiration: Basic alerts last 1 month, Essential and Plus 2 months; only Premium and Ultimate have alerts that do not expire. Put the expiry in the same calendar as your API wallet.
3. Notifications: tick Webhook URL and paste the relay’s URL there. Pasting it into the Message box is the most common first-day mistake.
4. Message: the JSON or command format your relay documents. A valid JSON message is sent as application/json; anything else as text/plain.

Fields a strategy alert should carry

Field names depend on the relay; the table shows what the message needs to say, not a standard. A minimal strategy message (braces escaped here; type real ones): { "secret": "your-token", "ticker": "{{ticker}}", "action": "{{strategy.order.action}}", "contracts": "{{strategy.order.contracts}}", "price": "{{close}}", "time": "{{timenow}}" }.

Strategy alerts vs indicator alerts

The strategy.order.* placeholders only exist on Pine strategies, which is why strategy alerts are the easiest to automate: one alert carries every entry and exit. With an indicator (or a drawn line), create one alert per action and type the side and size into each message yourself, for example "action": "buy", "contracts": "0.002" on the long alert and a reduce-only sell on the exit alert. TradingView’s webhook rules: requests come from four IP addresses (52.89.214.238, 34.212.75.30, 54.218.53.128, 52.32.178.7), only ports 80 and 443 are accepted, the receiving server must answer within 3 seconds, IPv6 is not supported, and TradingView warns against putting credentials in the body.

6. Alerts without automation: price, liquidation and Telegram

Not every alert needs to place an order. If you trade by hand, these alerts tell you when to look, with no API wallet, relay or paid plan (features read September 25, 2026 on TradingView’s help center, Hyperliquid’s app and docs and Hyperdash’s docs):

• Price alert on Hyperliquid’s own price. On tradingview.com, open HYPERLIQUID:BTCUSDC.P (or your market), press Alt + A (Option + A on macOS) or click the plus button on the price scale, pick reaches, exceeds or falls below, and choose app notification or email. Name it after the action you plan (“BTC 80k: add to long”). The free Basic plan allows 3 active price alerts, Essential 20, Plus 100, Premium 400 and Ultimate 1,000.
• Liquidation warning, level 1 (no code). Read the liquidation price in Hyperliquid’s Positions tab and set a TradingView price alert a few percent before it; update it whenever you add margin or size. Check the distance first with the liquidation price calculator. On cross margin the liquidation price moves with the whole account, so a fixed alert drifts.
• Liquidation warning, level 2 (a script, no keys). Hyperliquid’s public info endpoint returns liquidationPx for every open position of any address (clearinghouseState). A small script can alert on distance instead of a fixed level: warn under 15% from liquidation, act under 5%, tighter on volatile alts.
• Level 3: an order that acts for you. A reduce-only stop-loss or trailing stop closes the position while you sleep; keep it well inside the liquidation price so it fires first (trailing stop tutorial).
• Telegram. Hyperdash’s public channel (t.me/hyperdashflows) posts every Hyperliquid liquidation of $50,000 or more, large TWAPs and open-interest surges: useful context for checking your own margin. For alerts on your own account, create a bot with @BotFather and have your script call the Bot API’s sendMessage; the bot only sends messages and never needs a wallet. Any “alert bot” that asks for a seed phrase or private key is not an alert bot. Wallet-level alerts for addresses you follow are in the whale tracker guide.
• Fill notifications. The Hyperliquid web app shows fills of resting orders while the tab is open; the official Android app adds push notifications for order fills on the master account and its sub-accounts. We found no price or liquidation alerts in either.

When one of these alerts keeps telling you to place the same order, that is the point to automate it with the webhook steps above.

7. Self-hosted bridge with the Python SDK

If you can run a small web service, the official hyperliquid-python-sdk (0.24.0 in September 2026) does the EIP-712 signing for you. No builder fee, no third party holding your key, and your referral discount applies to every order.

1. Configure: pip install hyperliquid-python-sdk; the API wallet key signs, and account_address is your master address.
2. Expose one HTTPS endpoint on port 443 (FastAPI, Flask, a serverless function). Reply 200 at once and place the order after replying, so you stay inside the 3-second limit.
3. Verify the sender: reject requests without your secret token; optionally allow only TradingView’s four IPs.
4. Map the ticker: TradingView sends BTCUSDC.P; Hyperliquid wants the coin BTC. Strip the quote and suffix, read side and size, then send a market or limit order worth at least $10.
5. Make it idempotent: derive a client order ID (cloid, a 128-bit hex string) from the alert time so a re-delivered webhook cannot double-fill, and log every request.
6. Exit reduce-only and cap notional per alert in code.

Rate limits rarely bind alert-driven trading: REST requests share 1,200 weight per minute per IP, and an unbatched order weighs 1. The address limit (one action per 1 USDC traded, plus a 10,000-action starting buffer) matters only for high-frequency bots. Details: Hyperliquid API guide.

8. Step 6: test, then go live

• Testnet first: Autoview and TV-Hub route to the Hyperliquid testnet, WunderTrading and Gainium have paper trading, and a self-hosted bridge just points at the testnet URL. See the testnet guide. Label testnet windows; confusing them with mainnet is an expensive mistake.
• Then one small live order: $10 of notional is the minimum on perps (10 of the quote token on spot).
• Watch fills, not alerts. A delivered webhook is not a filled order. Check Trade History in the app, or subscribe to userFills over WebSocket and alert yourself on rejections.
• Spot automation: use the pair without .P (HYPERLIQUID:HYPEUSDC), confirm your relay supports spot (table above), and remember that a builder fee on spot can be up to 1% (charged on the sell side).

9. Troubleshooting: symptom, cause, fix

10. Hyperliquid charts and derivative metrics on TradingView

Hyperliquid perps are margined in USDC and carry TradingView’s .P perpetual suffix: HYPERLIQUID:BTCUSDC.P, HYPERLIQUID:ETHUSDC.P, HYPERLIQUID:HYPEUSDC.P. Spot pairs drop the suffix (HYPERLIQUID:HYPEUSDC), Trade[XYZ] stock, index and commodity perps use HIP3XYZ: (Trade[XYZ] guide) and Paragon uses HIP3PARA:. Candles and volume are Hyperliquid’s own; the HYPE pages Google shows first (HYPEUSD, HYPEUSDT) aggregate or use other exchanges.

New in September 2026: on September 21 TradingView added nine derivative metrics for more than 170 Hyperliquid contracts plus HIP-3 markets from Trade[XYZ] and Paragon (over 300 contracts): open interest, funding rate, liquidations, long/short ratio (accounts), long/short accounts %, mark price, index price, premium and basis. Hyperliquid is the first decentralized exchange in TradingView’s derivatives data set. Add them from Indicators → Fundamentals on a HYPERLIQUID: perp. On September 23 TradingView also folded Hyperliquid into its aggregated open interest, funding and liquidation metrics (Aggregated toggle; also in the crypto screener and heatmap).

Two reading notes. Hyperliquid pays funding every hour, so its funding line is not comparable one-to-one with Binance’s 8-hour prints; BTC funding sat at the 0.00125%/hour baseline in 72% of the 720 hours to September 25, 2026 and summed to 0.7664% over those 30 days, about $77 on a $10,000 long. And TP/SL and liquidations trigger on the mark price, so plotting mark beside last price explains “why did my stop fire”. More: funding explained, open interest guide, custom TradingView indicators.

11. The in-app chart and multi-chart workspaces

The chart in the official Hyperliquid app on app.hyperliquid.xyz says “Chart by TradingView” and loads TradingView’s Charting Library (version 28.5 on September 25, 2026): favourite intervals, the Indicators dialog, drawing tools (trend lines, Fibonacci, patterns, measurement), a Funding tab and fullscreen. It is not linked to your tradingview.com account, so layouts, Pine scripts and server-side alerts do not appear there; pick one place to draw your levels.

The app shows one market per chart; we found no layout switcher. For several charts, open the app in more than one window (/trade/BTC, /trade/ETH) or build a TradingView layout: 2 charts per tab on Essential, 4 on Plus, 8 on Premium, 16 on Ultimate, 1 on the free plan. A four-chart layout covers most traders: BTC on 1h–4h for context, your market on the execution timeframe, ETH or SOL with funding, and your market again with open interest and liquidations. From August 26 to September 25, 2026, 38.6% of Hyperliquid BTC perp volume traded between 12:00 and 17:00 UTC (trading sessions guide). As of Tue, 20 Oct 2026 03:53 UTC, Hyperliquid listed 178 perp markets with $4.03B of 24-hour perp volume; new listings can take time to appear on TradingView.

12. What automation costs: builder fees vs subscriptions

Worked example: one $10,000 market order, and a month of automation

A market order pays the taker fee. Monthly figures assume a strategy that trades $50,000 of notional a day for 30 days ($1.5M), all as taker, at the base fee tier.

Every row includes the 4% referral discount on Hyperliquid’s part of the fee (0.0432% instead of 0.045%): Hyperliquid applies it to builder-coded orders too, while the builder fee itself is charged in full (checked on mainnet fills on October 1, 2026). At this volume a builder fee costs more than any subscription in the table, while at a few hundred dollars a day it costs less. Sending limit orders where the strategy allows it helps more than either: the maker fee is 0.015% against 0.045% taker, and above $5M of 14-day volume the tier drops to 0.04% / 0.012%. Full schedule: Hyperliquid fees.

13. Security checklist

• API wallet only. Never give a relay, bot or person your main wallet key or seed phrase. The only main-wallet signature a relay may ask for is the one-time builder-fee approval.
• One named API wallet per relay, with its expiry in your calendar; revoke builder approvals you no longer use at app.hyperliquid.xyz/builderCodes.
• Secret in the message, key on the server. The alert carries a token; the private key never leaves the relay.
• Cap size, exit reduce-only, so a misfiring strategy cannot flip you into a max-leverage position.
• Separate sub-account. Sub-accounts unlock after $100,000 of volume and share your fee tier; fund the bot’s sub-account with only what the strategy may lose (the referral discount does not apply to sub-accounts).

14. Limitations and which setup fits you

• No broker link. A Pine strategy’s backtest does not include Hyperliquid fees, builder fees or hourly funding unless you model them (how to backtest a Hyperliquid strategy with both).
• Charting the spot pair, trading the perp. HYPEUSDC and HYPEUSDC.P differ by the perp premium; alerts on the wrong one fire at the wrong price.
• Latency. Alert → webhook → relay → order adds seconds; this setup suits strategies on 1-minute bars and slower, not scalping the order book.

Our honest recommendation: run alerts manually for a month and log what they would have done. If the manual version does not make money, a relay only automates the losses around the clock.

FAQ

Disclosure: HOLYGRAIL is our Hyperliquid referral code; we earn a share of referred accounts’ fees, and it never raises yours. We have no affiliation with TradingView or any relay named here. Plan limits, webhook rules and each relay’s pricing were read on their own sites on September 27, 2026; Hyperliquid fees and limits come from Hyperliquid’s documentation; market counts and volume refresh at build time from the public API.