/levels family computes these estimates from clearinghouse positions and margin state, then groups them into price buckets around the snapshot mark price.
This is a separate data grain from completed liquidation events, liquidation-volume buckets, and voluntary trigger orders. The projected-level routes currently cover Hyperliquid core and HIP-3. There is no Lighter projected-level route in the OpenAPI contract.
For completed liquidation events and volume, use Liquidations. For the exact request and response contracts, use the generated operation pages below.
Routes
Read a snapshot
Omitat to receive the latest retained snapshot for a symbol. Pass at as epoch milliseconds to receive the newest snapshot at or before that instant. The response’s snapshot_ts identifies the UTC snapshot that the levels reflect.
Snapshots are computed roughly every 45 minutes. That cadence describes the retained snapshot source, not a real-time liquidation-price calculation for one account or position.
- Hyperliquid
- HIP-3
BTC.Read retained history
Use the/history variant to enumerate snapshots in ascending snapshot_ts order. The route accepts start, end, limit, and cursor. Pass meta.next_cursor from one response as cursor for the next page.
summary=true when you only need the snapshot timestamp, mark price, and total notional. Summary items omit the levels histogram, so this is the lower-payload way to discover snapshots before fetching selected histograms.
When summary is false or omitted, each history item includes its bucketed levels array. Use range_pct, buckets, and side to control the returned view. The generated history pages document the complete parameter and response contracts:
Interpret the response
The snapshot response contains the following fields:
These projected forced-liquidation levels are aggregate bucketed estimates of forced-liquidation exposure. They are not completed liquidation events and they are not an account, wallet, or position liquidation-price endpoint.
Shape the bucket view
The snapshot and history routes accept the same bucket controls:
Use the generated snapshot operation page or HIP-3 snapshot operation page for the schema, examples, and validation details.
Keep liquidation data grains separate
Trigger levels are voluntary orders, not projected forced liquidations. Their history uses a separate route family and cadence. See Order flow for the surrounding order-event routes, or open the generated Hyperliquid trigger-level history and HIP-3 trigger-level history pages.