RULE CHANGE
Trading with the API
Stop_market and stop_limit orders now support attached take-profit/stop-loss; attached-exits endpoint extended to stop_market and stop_limit entries.
What this means
stop_market now allows attached TP/SL in addition to reduce-only protection, whereas previously only reduce-only protection was listed. stop_limit now allows attached TP/SL for opening conditional orders. The PUT endpoint for setting or removing attached exits now applies to resting limit, stop_market, or stop_limit entries, expanded from resting limit entries only.
▸ View exact changes
The change in place, line by line
Before Oct 15, 2026
that account's position. Long and short notional
add together. An opening fill that would exceed the cap is rejected with
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
−
| type | Required price fields | Important options |
|---|---|---|
| stop_market | trigger_price | optional reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order |
| take_market | trigger_price | opening conditional order |
| take_limit | trigger_price, limit_price | opening conditional order |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
FX markets trade on veranta. Use their current market_id values from
GET /v1/markets. The previous hyperliquid EUR/USD and USD/JPY markets are
retiring: they accept only orders that reduce or close existing positions
there. The historical fpx and lighter providers are retired and have no
markets available for new trades.
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
− a resting limit entry. Send null to remove a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.
After Oct 18, 2026
that account's position. Long and short notional
add together. An opening fill that would exceed the cap is rejected with
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
+
| type | Required price fields | Important options |
|---|---|---|
| stop_market | trigger_price | attached TP/SL, or reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
| take_market | trigger_price | opening conditional order |
| take_limit | trigger_price, limit_price | opening conditional order |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
FX markets trade on veranta. Use their current market_id values from
GET /v1/markets. The previous hyperliquid EUR/USD and USD/JPY markets are
retiring: they accept only orders that reduce or close existing positions
there. The historical fpx and lighter providers are retired and have no
markets available for new trades.
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
+ a resting limit, stop_market, or stop_limit entry. Send null to remove
+ a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.
that account's position. Long and short notional
add together. An opening fill that would exceed the cap is rejected with
exposure_cap, without resizing. Reductions and closes remain allowed, and
freed capacity becomes available at the next refresh, approximately 10 seconds
later. See Asset Exposure Limits.
Standard and advanced orders
Send orders to POST /v1/orders. If type is omitted, the request is treated
as a market order for compatibility with existing clients.
| type | Required price fields | Important options |
|---|---|---|
| market | expected_price | slippage_tolerance_bps, attached TP/SL |
| limit | limit_price | attached TP/SL, IOC, FOK, or GTD time in force |
| chase | chase_offset | optional chase_cap_price |
−
| type | Required price fields | Important options |
|---|---|---|
| stop_market | trigger_price | optional reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order |
+
| type | Required price fields | Important options |
|---|---|---|
| stop_market | trigger_price | attached TP/SL, or reduce-only protection |
| stop_limit | trigger_price, limit_price | opening conditional order, attached TP/SL |
| take_market | trigger_price | opening conditional order |
| take_limit | trigger_price, limit_price | opening conditional order |
| take_profit | trigger_price, reduce_only: true | position protection |
| conditional | trigger_price, trigger_market_id, trigger_direction | observe one market and execute on another |
The server resolves provider, symbol, and venue coin from market_id. Do not
send those fields. expected_price records what your client observed, but it
never controls the execution price, margin calculation, or slippage reference.
FX markets trade on veranta. Use their current market_id values from
GET /v1/markets. The previous hyperliquid EUR/USD and USD/JPY markets are
retiring: they accept only orders that reduce or close existing positions
there. The historical fpx and lighter providers are retired and have no
markets available for new trades.
copy uses the leverage you send, lowered to the follower's own maximum for
that market when needed, and keeps the margin mode of any position the
follower already holds in that market. See
Copy Trading.
Use GET /v1/orders?client_order_id=... to resolve your caller-assigned order
identity when the placement response or server id is unavailable. This lookup
survives API key rotation and returns the normal order-page shape with zero or
one result.
If the server cannot prove the snapshot is complete inside the active-order
bound, it returns 503 with Retry-After instead of returning truncated data.
- PATCH /v1/orders/{order_id} changes price and optionally size.
- PUT /v1/orders/{order_id}/attached-exits sets or removes TP/SL attached to
− a resting limit entry. Send null to remove a leg.
+ a resting limit, stop_market, or stop_limit entry. Send null to remove
+ a leg.
- DELETE /v1/orders/{order_id} cancels a working order or queues cancellation
when execution already owns the row.
To cancel the complete ordinary-order snapshot for an account, send
POST /v1/accounts/{account_id}/cancel-all-orders with an Idempotency-Key.
It includes resting orders and armed trigger orders. An in-flight market order
can still settle, and active TWAP, VWAP, or scaled parents must be canceled
through their own endpoints. Each request advances at most five source orders,
with every source cancellation isolated in its own transaction. A 202
response includes progress and Retry-After; repeat the same request until the
operation reports completed.
Chase orders cannot be modified. Cancel the chase and place a replacement with
new offset or cap settings.