Can I practice on HyperLiquid Testnet before trading live?

Yes. Autoview supports a HyperLiquid Testnet connection, so you can automate it with the exact same commands you'd use live. Testnet runs on its own separate network rather than a paper account on the main chain, so you trade with test funds there, never your real wallet balance.

What credentials does HyperLiquid need, and is my main wallet ever exposed?

HyperLiquid connects with a Secret Key, the private key of a separate API wallet you generate, plus your main wallet's Public Address. Trades execute against the balance in your main wallet, but only the dedicated API wallet key ever leaves HyperLiquid's site, so a leaked key lets someone trade, not withdraw.

Does Autoview run HyperLiquid in the cloud, or do I need the Chrome extension?

Both work for HyperLiquid. The cloud webhook platform runs your automation on its own, so nothing needs to stay open on your computer. If you'd rather execute on your own device, the Chrome extension can run HyperLiquid too, reading TradingView alerts directly from your browser.

Does Autoview support stop-loss, take-profit, or trailing stops on HyperLiquid?

Stop-loss and take-profit, yes, each as its own trigger order rather than attached to your entry in one command. Trailing stops are not currently available for HyperLiquid through Autoview; use a fixed stop trigger instead. The full command syntax for triggers lives on Autoview's syntax reference page.

Getting Started with HyperLiquid

Autoview · Guide · Updated August 14, 2026

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, and the mechanism behind that is called agent-wallet delegation: you approve a separate wallet (the "agent," what this guide and Autoview both call the API wallet) to sign trade actions on behalf of your main wallet, via a HyperLiquid action called approveAgent. The agent wallet can place and cancel orders against your main wallet's balance. It cannot withdraw, transfer, or touch anything outside trading. That's the entire scope of the delegation, by design.

Never generate a key from, or paste the private key of, your main wallet into this connection. Use a dedicated agent wallet only. HyperLiquid lets you use your main wallet's raw private key directly, but doing that hands Autoview (and anything that ever reads that key from storage, a leak, a bug, a compromised machine) full control of your funds, not just trading. The whole point of the agent-wallet model is that a leaked agent key costs you nothing but the trades someone could place; a leaked main-wallet key costs you everything in it.

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. HyperLiquid allows one unnamed agent wallet per account plus up to three named ones, so you can run more than one Autoview connection, or more than one bot, off separate agent wallets tied to the same main wallet.

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.

One thing HyperLiquid doesn't put front and center: this wallet expires. HyperLiquid caps every API wallet's validity at 180 days out from when you generate it, and shows the exact date on the API page next to the wallet, labeled Valid Until. Check it. When that date arrives, regenerate the wallet and paste the new Secret Key into Autoview the same way you did the first time (step 2 below). There's no warning when it lapses. The wallet just stops signing.

Revoking or rotating a key. There's no separate "revoke" button; the way you retire an agent wallet is to approve a new one in its place. Approving a new agent under the same name replaces the old one, so if you ever suspect a key leaked, generate a fresh named agent wallet, update the Secret Key in Autoview, and the old agent stops being able to sign anything the moment the new approval lands. An unnamed agent works the same way, one at a time; generating a new unnamed agent supersedes the previous unnamed one.

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, which also documents the asset ID mapping underneath the human-readable name: a perpetual's asset ID is its index position in the universe array of the meta response, while a spot asset's ID is 10000 plus its index in spotMeta.universe. Autoview resolves the name you send to that ID for you, but if you're ever debugging against the raw API, that's the mapping. Testnet has its own separate universe and its own info endpoint at https://api.hyperliquid-testnet.xyz, distinct from live's https://api.hyperliquid.xyz -- an asset ID on testnet doesn't necessarily point to the same asset on mainnet.

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.
Orders stop landing and nothing else changed: check the Valid Until date on the HyperLiquid API page first. An expired API wallet stops taking orders, and nothing on the Autoview side looks broken when it happens. Regenerate the wallet and update the Secret Key in Autoview.
Signature or chain-mismatch rejection: HyperLiquid signs every action against a specific network, mainnet or testnet, and a signature built for the wrong one gets rejected outright. This almost always means an agent wallet approved on mainnet got pointed at a testnet connection, or the reverse. Confirm the HyperLiquid connection in Autoview (live vs. Testnet) matches the network you generated and approved the agent wallet on, and regenerate the agent wallet on the correct network if it doesn't.

For the full command vocabulary, including limit prices and take-profit or stop-loss triggers, see the command syntax reference. Want to run through all of the above without risking a live wallet first? See HyperLiquid Testnet. If a connection still won't behave, email support@autoview.com.

Compare the extension and webhook platform