Hyperliquid Market Order
Place a market order on Hyperliquid perpetual DEX. Executes immediately at current market price with configurable slippage protection (default 1%). Ideal for: instant trade execution, momentum entries, and time-sensitive strategies.
Catalog action Hyperliquid wallet
Place a market order on Hyperliquid perpetual DEX. Executes immediately at current market price with configurable slippage protection (default 1%). Ideal for: instant trade execution, momentum entries, and time-sensitive strategies.
This action can require a wallet connector, gas, token movement, or an external side effect. Test with simulation or a controlled amount before using it in a live workflow.
At a Glance
| Field | Value |
|---|---|
| Action ID | hyperliquid-market-order |
| Category | Hyperliquid |
| Connector | wallet |
| Requires gas | No |
| Funds movement | None declared |
| Tags | hyperliquid, perps, order, trade, market, defi |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
dex | string | No | HIP-3 DEX name for TradFi markets. Omit for standard crypto perps. xyz = trade.xyz (stocks, indices, commodities), flx = flx.finance, vntl = vntl.exchange |
coin | string | Yes | Asset symbol (e.g., BTC, ETH for crypto; TSLA, SP500 for HIP-3 DEX markets) |
side | string | Yes | Order direction |
size | string | Yes | Order size in asset units (e.g., '0.1' for 0.1 BTC). Total order value (size × market price) must be at least $10. |
slippageBps | number | No | Maximum acceptable slippage in basis points (default: 100 = 1%). For buys, the limit price is set above mid; for sells, below mid. |
reduceOnly | boolean | No | If true, order can only reduce an existing position |
cloid | string | No | Optional client order ID for tracking (hex string, max 16 bytes) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Order outcome: filled (fully matched), partially_filled (IOC remainder cancelled) |
oid | number | No | Hyperliquid order ID |
filledSize | string | No | Total filled size |
avgPrice | string | No | Average fill price |
coin | string | No | Asset symbol |
side | string | No | Order side (buy/sell) |
requestedSize | string | No | Originally requested size |
midPrice | string | No | Mid price at time of order |
limitPrice | string | No | Effective limit price after slippage |
Examples
json{ "type": "hyperliquid-market-order", "payload": { "coin": "example-coin", "side": "buy", "size": "example-size" }, "children": [], "connector": { "type": "wallet", "id": "conn_wallet" }}
bashcurl -X POST "https://api.b3os.org/v1/actions/hyperliquid-market-order/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "coin": "example-coin", "side": "buy", "size": "example-size" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.