Get take profits & stop losses
- Hyperliquid
- HIP-3
- HIP-4
/v1/hyperliquid/orders/{symbol}/tpsl. Plain perp symbols such as BTC.Request parameters
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
symbol | path | string | Yes | Trading pair symbol, e.g. BTC |
start | query | string | No | Start time, ISO 8601 (e.g. 2026-01-01T00:00:00Z) |
end | query | string | No | End time, ISO 8601 |
user_address | query | string | No | Filter by wallet address |
limit | query | integer | No | Max results. Default 1000, max 10000 |
cursor | query | string | No | Pagination cursor from meta.next_cursor |
When to use it
A take-profit or stop-loss sits as a trigger until its price condition fires. When it fires, it becomes an ordinary fill, so a complete picture pairs this route with Trades for the resulting executions and Order history for the order lifecycle. Use theuser_address filter to study one wallet’s risk management, or pull the whole symbol to see where triggers cluster around price. Store the trigger price, side, and status with each record: a trigger that never fired and one that fired are different events, and the status field is what separates them.
Stream it live
There is no dedicated take-profit or stop-loss channel. Trigger orders surface in the L4 order-event stream (l4_orders, plus the venue-prefixed variants), where you can filter for trigger order types as they are placed, fired, or canceled.
Export in bulk
Take-profit and stop-loss records ship in thel4_orders (Order Events / TP/SL) export schema ($8/GB, $25 minimum), delivered as Parquet with ZSTD compression. Build a selection in the Data Catalog; columns and coverage keys are on Export Schemas.