Quicknode logoBuilt on Quicknode infrastructure

Hyperliquid API

Zero-custody builder API for Hyperliquid.Sign locally, we forward. Your keys never leave your machine.

Get StartedApprove via Wallet
Zero custody
Perps & Spot
HIP-3 Markets

How it works

Every trade follows the same three-step pattern. Use human-readable format (asset names, "buy"/"sell", "market" tif) or native wire format — no SDK needed. Use POST /openOrders and POST /orderStatus to discover orders and get pre-built cancel actions.

1

Build

POST /exchange

Send the action without signature. We inject the builder fee and compute the hash

2

Sign

Your key

Sign the hash locally. Your private key never leaves

3

Send

POST /exchange

Send the action with signature. We forward the signed transaction to Hyperliquid

Quickstart

Clone the repo. Set your key. Run.

Endpointhttps://send.hyperliquidapi.com

hyperliquid-api-examples

Clone and run. Full working examples in Python, TypeScript, and Rust.

bash
1git clone https://github.com/quiknode-labs/hyperliquid-api-examples.git
2cd hyperliquid-api-examples/python
3pip install -r requirements.txt
4export PRIVATE_KEY="0xYOUR_PRIVATE_KEY"
5 
6python3 approve.py          # one-time builder fee approval
7python3 check_status.py     # check approval status
8python3 list_markets.py     # list all available markets
9python3 open_orders.py      # view open orders + cancel actions
10python3 order_status.py     # check what happened to an order
11python3 place_order.py      # place a perp order
12python3 cancel_order.py     # place + cancel
13python3 modify_order.py     # place + modify
14python3 roundtrip.py        # buy then sell (full cycle)
15python3 hip3_order.py       # HIP-3 market order by name
16python3 revoke.py           # revoke approval

Try it now

bash
1curl -s -X POST https://send.hyperliquidapi.com/exchange \
2  -H "Content-Type: application/json" \
3  -d '{
4    "action": {
5      "type": "order",
6      "orders": [{"asset": "BTC", "side": "buy", "price": "100000", "size": "0.001", "tif": "ioc"}]
7    }
8  }'

API Reference

REST API. POST /exchange for all transactions (build without signature, send with signature). Click any endpoint to expand and try it live.

Examples

Exchange — Build (no signature)

Exchange — Send (with signature)

Enhanced Endpoints

Error Codes

Every error uses the appropriate HTTP status code and includes error, message, and guidance with exactly what to do next.

HTTPError Code
403NOT_APPROVED
422BUILDER_MISMATCH
422SIGNATURE_INVALID
422HL_EXCHANGE_*
400INVALID_JSON
422INVALID_PARAMS
500INTERNAL_ERROR

Fees

Two fees apply per trade: our builder fee (injected into your order) and Hyperliquid's exchange fee (maker/taker, charged by the protocol).

Builder Fee— charged by us, injected into each order
MarketFeeProtocol Max
Perpetuals0.04%0.1%
Spot0.05%1%
Exchange Fee— charged by Hyperliquid, based on your volume tier
MarketTakerMaker
Perpetuals0.045%0.015%
Spot0.070%0.040%

You approve a maxFeeRate ceiling (e.g. "1%") for the builder fee. The actual builder fee is always within your approved limit. You can revoke at any time.

FAQ

Common questions about Hyperliquid API.

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

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.

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.

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.

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.

You can trade perpetuals (perps), spot markets, and HIP-3 markets on Hyperliquid through the API. All order types supported by Hyperliquid are available.

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

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.

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, and HIP-3 markets.

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.

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.

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.

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.