Getting Started with HyperLiquid

Autoview

By the end of this guide you'll have a HyperLiquid wallet connected to Autoview, a webhook ready to receive alerts, and one real order placed from a test signal. We'll do a dry run before anything touches the order book, so you can confirm your syntax without risking a fill.

HyperLiquid is a live on-chain venue. Trades execute against your real wallet. That's worth saying twice, because the connection here works differently from a normal API key. A couple of HyperLiquid quirks will trip you up if you skip ahead.

What you'll need

  • A funded HyperLiquid account at app.hyperliquid.xyz.
  • An Autoview account with a HyperLiquid connection. See the pricing page for current rates per live exchange.
  • An alert source that can POST to a URL. TradingView is the common one, but the webhook accepts a POST from anything: a custom script, your own backend, another charting platform.

1. Generate an API wallet on HyperLiquid

HyperLiquid doesn't hand you a key-and-secret pair. It signs trades with an Ethereum private key. You can use your main wallet's key directly, but don't. Generate a dedicated API wallet instead.

Open the HyperLiquid API page, connect your wallet, and click Generate. The API wallet gets its own private key but trades against the balance sitting in your main wallet. If that key leaks, an attacker can trade. They can't withdraw your funds. That separation is the whole point.

Two values come out of this step:

  • Secret Key: the API wallet's private key. HyperLiquid shows it once. Copy it somewhere safe immediately.
  • Public Address: the 0x address of your main wallet, the one holding the balance you want to trade. Not the API wallet's address.

HyperLiquid also supports IP whitelisting on API wallets. If you turn it on, you'll restrict signing to specific addresses, which means coordinating with the execution zone Autoview routes through. Get the connection working first, then tighten. The full setup is in HyperLiquid's own docs.

2. Save your credentials in Autoview

In Autoview, open the HyperLiquid setup and paste the Secret Key into the Secret Key field and the main wallet's address into Public Address. Pick an execution zone from the dropdown. That's where your commands run. Save.

Storing the credentials doesn't place any orders. It just hands Autoview the key it needs to sign on your behalf when a real alert arrives.

3. Create a webhook and link it

A webhook is a URL that catches your alert messages. Create one and give it a name you'll recognize later, like HyperLiquid Perps. If you want a little extra security, set a Webhook Key. Then every POST has to carry ?key=yourkey in the URL.

One more wiring step: link the webhook to your HyperLiquid credentials. The link tells Autoview which wallet to trade when an alert lands on that URL. Skip it and every alert comes back with No API Keys linked to this Webhook.

4. Know the symbol format before you send anything

This is where most HyperLiquid setups go wrong. HyperLiquid uses two different instrument formats depending on the market:

  • Perpetual futures use the bare asset name, uppercase. Bitcoin perp is BTC. Ether is ETH. Solana is SOL.
  • Spot pairs use BASE/QUOTE with a slash. The PURR spot market is PURR/USDC.

Do not pipe TradingView's {{ticker}} through unmodified. {{ticker}} is a TradingView placeholder: TradingView substitutes it when the alert fires, and it hands you strings like BTCUSDT or BTCUSD.P that HyperLiquid won't recognize. The point is that the alert sender supplies the symbol value, and a script or another platform does it its own way. Hardcode the bare asset for perps, or the BASE/QUOTE pair for spot. The full instrument list lives in the HyperLiquid info-endpoint docs.

Two more rules that matter:

  • Direction is required. Every alert needs b=buy, b=sell, b=long, or b=short. Leave it out and Autoview errors before it ever contacts HyperLiquid.
  • Quantity is in the base asset. For the BTC perp, q=0.001 means 0.001 BTC. Sizes have to fit the asset's precision step and clear HyperLiquid's minimum, or the exchange rejects the order.

5. Dry-run, then go live

Now the part everyone wants. Sending a trade. Start with a dry run: add d=1 to your alert message and Autoview parses the command, shows you exactly what it would do, and stops short of placing anything:

s=BTC b=buy q=0.001 t=market d=1

Fire that through your webhook. The result lands on your events page looking just like a live trade. A blue row means the syntax is good. Red or orange flags an error to fix before you risk real size.

When the dry run reads clean, drop d=1 and send it for real:

s=BTC b=buy q=0.001 t=market

Use a small quantity that still clears HyperLiquid's minimum order value, or the exchange rejects it. Check the events page and your HyperLiquid account to confirm the order went through. That round trip, dry run clean then live order filled, is the proof your connection works end to end.

If something doesn't fire

  • No API Keys linked to this Webhook: you skipped step 3. Link the credential to the webhook.
  • Unknown market symbol: you sent something like BTCUSDT or BTC/USD for a perp. Use the bare asset (BTC) or the correct spot pair.
  • Invalid Order Book (b=) parameter: the direction is missing. Add b=buy or b=sell.
  • Size or notional rejection: bump the quantity to clear HyperLiquid's minimum and match the asset's precision step.

For the full command vocabulary, including limit prices and take-profit or stop-loss triggers, see the command syntax reference. If a connection still won't behave, email support@autoview.com.

Compare the extension and webhook platform