Hyperliquid Setup

This page lists the key differences that are specific to Hyperliquid setup.

• In .env

HYPERLIQUID_PRIVATE_KEY=<REPLACE WITH YOUR KEY>

• Specify "hyperliquid" to "exchange" field in Tradingview alert message.

sample alert template

{
"exchange": "hyperliquid",
"strategy":"testStrategy",
"market":"ETH_USD",
"size":"0.01",
"reverse":false,
"order":"{{strategy.order.action}}",
"position":"{{strategy.market_position}}",
"price":"{{strategy.order.price}}"
}

HIP-3 Builder-Deployed Perps

Hyperliquid supports HIP-3 builder-deployed perpetuals — markets for equities, commodities, and forex deployed by third-party builders like trade.xyz.

To trade these assets, use the full dex:SYMBOL format in the market field:

{
  "exchange": "hyperliquid",
  "strategy": "SilverStrategy",
  "market": "xyz:SILVER",
  "size": 1.0,
  "order": "buy",
  "price": "{{strategy.order.price}}",
  "position": "long",
  "reverse": false
}

Examples: "xyz:SILVER", "xyz:GOLD", "xyz:TSLA", "xyz:NVDA", "km:US500", "flx:OIL".

Note

We have identified an issue where the Hyperliquid API returns a "429 Too Many Requests" error. This occurs because Render.com shares outbound IP addresses across multiple users, which can cause our requests to exceed the API's rate limits.

So, I would suggest to deploy the connector tool to Digital Ocean and here is the guide