What is Hyperliquid API?

Hyperliquid API is a zero-custody REST builder API for Hyperliquid, built by Quicknode. It lets you trade perpetuals, spot, HIP-3, and HIP-4 markets programmatically while your private keys never leave your machine.

How does the build-sign-send pattern work?

Every trade follows three steps: (1) Build — construct your order parameters locally, (2) Sign — sign the transaction with your private key on your machine, (3) Send — submit the signed payload to the Hyperliquid API endpoint. Your private key is never transmitted.

What are the trading fees?

Hyperliquid API charges a builder fee of 0.04% on perpetual trades and 0.05% on spot trades. These are on top of Hyperliquid's native exchange fees.

How do I fund order priority fees?

Order priority fees are paid from undelegated staking HYPE, not spot USDC. If you have spot HYPE, build a cDeposit action through POST /exchange, sign the returned hash, then send the returned action with the signature. For example, wei 100000 moves 0.001 HYPE into undelegated staking HYPE.

How do I add a priority fee to an order?

Set the top-level priorityFee field when building an IOC order. The API encodes it into action.grouping as { p: priorityFee } before hashing, so you must sign and send the returned action unchanged. A priorityFee of 10000 is 1 bp, and the max is 80000. Do not use priorityFee on HIP-4 prediction markets; Hyperliquid rejects priority grouping for # assets.

Is Hyperliquid API custodial?

No. Hyperliquid API is fully non-custodial. You sign every transaction locally with your own private key. The API only forwards your pre-signed transactions to Hyperliquid. Your keys never leave your machine.

What programming languages are supported?

Hyperliquid API provides examples and SDK support for Python, TypeScript, and Rust. The API uses a REST API over HTTPS, so any language with an HTTP client can integrate.

What markets can I trade on Hyperliquid API?

You can trade perpetuals (perps), spot markets, HIP-3 markets, and HIP-4 prediction markets on Hyperliquid through the API. HIP-4 markets use # aliases like #10 or native asset indices like 100000010.

How do I trade HIP-4 prediction markets?

Use the same POST /exchange build-sign-send flow and set the asset to a # alias such as #10, or the native asset index such as 100000010. HIP-4 markets require USDC balance, have a 10 USDC minimum order value, and should use grouping na because priorityFee is not supported for # markets.

Is there an API for Hyperliquid?

Yes. Hyperliquid API by Quicknode is a production-ready REST API for trading on Hyperliquid. It supports perpetuals, spot, HIP-3, and HIP-4 markets with a non-custodial build-sign-send pattern. You sign locally and the API forwards your pre-signed transactions to Hyperliquid.

How do I build a Hyperliquid trading bot?

Use the Hyperliquid API to build a trading bot in Python, TypeScript, or Rust. Call the order endpoint with your parameters, sign the payload with your private key locally, and submit via HTTPS. The API handles routing to Hyperliquid while you retain full custody of your keys.

How do I trade Hyperliquid programmatically?

Send REST API requests to the Hyperliquid API over HTTPS. Build your order parameters, sign the transaction locally with your private key, and call the send endpoint. The API supports market, limit, and trigger orders for perpetuals, spot, HIP-3, and HIP-4 markets.

What is a builder fee on Hyperliquid?

A builder fee is a small fee charged by Hyperliquid API infrastructure providers on top of Hyperliquid's native exchange fees. Hyperliquid API charges 0.04% on perpetual trades and 0.05% on spot trades. Builder fees are set by the API provider, not by Hyperliquid itself.

How do I cancel or modify an order via the API?

To cancel an order through Hyperliquid API, send a cancel request with the order ID, sign it locally with your private key, and submit. To modify, cancel the existing order and place a new one. Both operations follow the same build-sign-send pattern as placing orders.

What is HIP-3 on Hyperliquid?

HIP-3 is Hyperliquid's protocol for permissionless spot token deployment and liquidity. Through the Hyperliquid API, you can trade HIP-3 tokens programmatically alongside perpetuals and standard spot markets. HIP-3 markets use the same REST API endpoints as other order types.

What is HIP-4 on Hyperliquid?

HIP-4 is Hyperliquid's protocol for on-chain prediction markets, enabling programmatic trading on event-based outcomes. Through the Hyperliquid API, you can trade HIP-4 markets using # aliases like #10 or native asset indices like 100000010. HIP-4 markets use the same REST API endpoints as perpetuals, spot, and HIP-3.

Do I need to share my private key to use Hyperliquid API?

No. Hyperliquid API is fully non-custodial — your private key never leaves your machine. You sign every transaction locally and only send the signed payload to the API. The server cannot execute trades without your cryptographic signature.

hyperliquidapi / approvedocs changelognon-custodial

Approve & fund

A one-time setup before you trade through the API: approve the builder fee, and fund your Hyperliquid account. The API is free to use; the builder fee is its only cost, charged when an order fills. Non-custodial, so your keys never leave your machine.

Approve Builder Fee

One-time approval to trade through this builder. Your private key never leaves your wallet.

Perp fee0.04%

Spot fee0.05%

Approval ceiling1%

The approval ceiling is the maximum the builder could ever charge. Actual fees are 0.04% (perps) and 0.05% (spot). You can revoke at any time.

No wallet detected

Install MetaMask or Rabby to continue.

Check Approval Status

Your private key never leaves your wallet. We only receive the signature.

Prefer the command line?

Approve from a terminal: build, sign locally, send. No wallet UI required.

curl · approve builder fee

# 1 · build (no signature)
curl -s -X POST https://send.hyperliquidapi.com/exchange \
  -H "Content-Type: application/json" \
  -d '{"action":{"type":"approveBuilderFee","maxFeeRate":"1%"}}'
# → { hash, nonce, typedData }

# 2 · sign the hash locally, then send it back
curl -s -X POST https://send.hyperliquidapi.com/exchange \
  -H "Content-Type: application/json" \
  -d '{"action":{"type":"approveBuilderFee","maxFeeRate":"1%"},
       "nonce":…, "signature":{…}}'

# check status anytime
curl -s https://send.hyperliquidapi.com/approval?user=0xYOUR_ADDRESS

full flow in the docs →