Exchange API calls do not consume Quicknode API credits. Transactions through this endpoint are appended with a builder fee. See hyperliquidapi.com for a full breakdown. To white-label with your own builder code, contact us.
This endpoint is not a drop-in replacement for Hyperliquid's native /exchange endpoint. See the Exchange API Overview for key differences.
Body Parameters
- actionobjectREQUIRED
Order action object in wire format (from build-order or build-market-order response)
- typestring
Action type ("order")
- ordersarray
Array of order objects in wire format
- ainteger
Asset index (0 for BTC, 1 for ETH, etc.)
- bboolean
Buy side (true for buy, false for sell)
- pstring
Price as a stringified number
- sstring
Size/quantity as a stringified number
- rboolean
Reduce-only flag
- tobject
Order type specification
- limitobject
Limit order type
- tifstring
Time in force ("Ioc", "Gtc", "Alo")
- groupingstring or object
Order grouping strategy ("na", "normalTpsl", "positionTpsl"). When a priority fee is requested, the build response returns grouping as an object of the form { "p": 12345 }. Send the action exactly as returned by the build step. HIP-4 signed actions use grouping "na".
- nonceintegerREQUIRED
Nonce from build-order response (timestamp in milliseconds)
- signatureobjectREQUIRED
ECDSA signature of the hash
- rstring
Signature r value (0x-prefixed hex string)
- sstring
Signature s value (0x-prefixed hex string)
- vinteger
Signature v value (27 or 28)
- vaultAddressstring
Optional vault address
- expiresAfterinteger
Optional expiration timestamp (ms)
- slippagenumber
Optional slippage tolerance
- priorityFeeinteger or string
Optional priority fee rate. The value is interpreted as p / 100000000 of filled notional, so 10000 equals 1 basis point and the maximum is 80000 (8 basis points). Applies only to IOC orders; every order in the action must be IOC or a market-style IOC order. Charged from the undelegated staking HYPE balance (use Build Priority Funding Deposit to fund it). Not supported for HIP-4 orders. When the build response already includes grouping as an object { p }, any priorityFee sent must equal action.grouping.p.
Returns
- successboolean
Whether the order was successfully submitted
- userstring
User address (0x-prefixed hex string)
- exchangeResponseobject
Response from Hyperliquid exchange with order details
- ordersarray
Optional. Summary of each submitted order, including asset information, side, price, size, status, oid, and fill details when present.