HyperLiquid Testnet: testing Autoview before you trade live

Autoview · Guide · Updated September 2, 2026

HyperLiquid Testnet is a separate blockchain network, not a simulated balance on top of the real one. Getting started with HyperLiquid connects your live wallet; this page walks through Testnet specifically, including the one step that catches people who haven't done this before: getting funded there in the first place.

The network this runs on

HyperLiquid isn't an app on top of someone else's chain. It's its own Layer 1, built from two parts under one consensus: HyperCore, which runs the order books and matching, and HyperEVM, its smart-contract layer, both secured by the same HyperBFT consensus (HyperLiquid docs, HyperEVM, accessed 2026-09-11). Testnet is a separate network from mainnet, not a mode switch on the same one: it runs on its own API host, api.hyperliquid-testnet.xyz, distinct from live HyperLiquid's api.hyperliquid.xyz, and its own asset numbering, covered next.

HyperLiquid's raw API addresses every asset by a numeric index, not by symbol, and testnet and mainnet don't share the same numbers for the same asset. HyperLiquid's own docs give HYPE as the example: spot index 107 on mainnet, 1035 on testnet (HyperLiquid docs, Asset IDs, accessed 2026-09-11). Autoview's HyperLiquid integration applies this same indexing underneath the symbol names you type: a perp resolves to its position in the exchange's asset list, and a spot pair resolves to 10000 + that position (Autoview treats PURR/USDC as asset 10000, matching HyperLiquid's own worked example). You never write the index yourself, Autoview does the lookup, but it's why a testnet symbol and a live symbol with the same name are not interchangeable behind the scenes, and why this page's commands should stay on testnet rather than getting copied verbatim into a live script that assumes the same index.

Use a wallet you treat as disposable

Fund a wallet for testnet specifically and treat it as disposable: it should hold nothing but mock USDC, exist for testing, and never be the wallet you use for real funds. Testnet balances have no real-world value and can be reset or drained by the faucet's own rate limits without warning, so there's no reason to reuse a wallet you'd mind losing access to.

1. Get testnet funds from the faucet

Open the HyperLiquid Testnet faucet and connect the wallet you want to trade with. It grants 1,000 mock USDC per claim.

One requirement trips people up: the faucet only pays out to a wallet address that has previously made a deposit on HyperLiquid's live mainnet. If you've never funded a live HyperLiquid account with that address, connect the same wallet to the live app and make a deposit first, then come back to the faucet.

If you log into HyperLiquid with email instead of a wallet extension, this step needs one extra move: HyperLiquid's login provider generates a different address for testnet than it does for mainnet, so the mainnet-deposit requirement can't be satisfied automatically. Export your mainnet wallet's key and import it into a browser-extension wallet like Rabby or MetaMask, then connect that same wallet on both networks. A wallet connected through a browser extension keeps one address across mainnet and testnet, so this only matters for email-based logins.

2. Generate a Testnet API wallet

HyperLiquid signs trades with a wallet private key, not a key-and-secret pair, and that's true on Testnet too. Open the Testnet API page (note the -testnet in the URL, distinct from the live API page), connect your funded testnet wallet, and generate a dedicated API wallet rather than using your main key directly. You'll get two values, the same shape as the live connection:

• Secret Key: the API wallet's private key. Shown once. Copy it immediately.
• Public Address: your main testnet wallet's 0x address, the one holding the faucet funds. Not the API wallet's own address.

The same 180-day expiry applies here as on live HyperLiquid: check the Valid Until date next to the wallet on the API page, and regenerate it when that date arrives.

3. Connect HyperLiquid Testnet in Autoview

HyperLiquid Testnet isn't a promoted card in Autoview's setup picker today. Connect it directly at /account/credentials/hyperliquid_testnet/create/, paste the Secret Key and Public Address from step 2, and pick an execution zone. It costs nothing to run.

Create a webhook the same way you would for any exchange, and link it to your HyperLiquid Testnet credentials specifically. An alert that lands on a webhook linked to a different exchange's credentials won't reach this connection.

4. Send a test command

Because HYPERLIQUIDTESTNET runs the identical order-placement code live HyperLiquid uses, every command you'd write for live works here unchanged: the same e=, s=, b=, t=, and q= tokens, the same bare-asset perp symbols (BTC, ETH, SOL) and BASE/QUOTE spot pairs (PURR/USDC), and the same stop-loss/take-profit trigger orders. See the getting-started guide for the full symbol-format rules and the syntax reference for every parameter.

e=HYPERLIQUIDTESTNET s=BTC b=buy q=0.01 t=market d=1

d=1 dry-runs the command: Autoview resolves it and reports what it would have done without sending it. Drop d=1 once the side, symbol, and size look right, and confirm the fill lands in your testnet account, not your live one.

This guide doesn't include a live order-and-cancel transcript for HyperLiquid Testnet. Confirm the fill (and, separately, a cancel or close) directly in HyperLiquid's own testnet interface at app.hyperliquid-testnet.xyz after you send a command, rather than assuming success from the dry-run alone.

A note on what Autoview is. Autoview is an execution tool, not a trading or investment advisor. It places the orders your script and alerts tell it to; it doesn't generate signals or make any claim about results. See our disclosures.

Back to getting started with HyperLiquid