API reference, Price-level maps

Price level

The orders and positions inside one bucket of the maps: each stop / take-profit with its wallet and position, each position liquidated there.

  • Elysium: not served
  • HyperCore
  • HyperEVM: not served
  • Not on Elysium or HyperEVM: served on HyperCore only

GET https://api.femtos.xyz/v1/hypercore/price-level

Parameters

ParamInExample or valuesMeaning
coinqueryBTCHyperCore perp coin: BTC, xyz:TSLA
px_loquery50000Band low edge (inclusive), price
px_hiquery150000Band high edge (exclusive), price, over px_lo
limitquery50Orders, and positions, listed (largest first)

Example

curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/hypercore/price-level?coin=BTC&px_lo=50000&px_hi=150000&limit=50"

Key: Authorization: Bearer $FEMTOS_KEY. Get a free key, or with no browser through agent onboarding.

Response fields

FieldTypeMeaning
ordersobject[]Open trigger orders in the band, largest executable notional first, then largest placed: {oid, user, coin, side, kind, exec, orderType, triggerPx, triggerCondition, limitPx, sz, origSz, …}
orders.executableSzdecimalSize it would execute when it fires: a reduce-only one at most what is left of its wallet's position then
orders.unbackedSzdecimalSize placed that would not execute (reduce-only past the position, or opening past the account's margin)
orders.positionobject | nullThe wallet's open position in the coin; null without one: {address, szi, side, entryPx, notional, upnl, leverage, marginMode, liqPx, liqDistancePct, label, entity}
ordersTotalintOpen trigger orders in the band
liquidationsobject[]Open positions whose liquidation price is in the band, largest liqNotional first: {address, szi, side, entryPx, notional, upnl, leverage, marginMode, liqPx, liqDistancePct, label, entity, …}
liquidationsTotalintOpen positions whose liquidation price is in the band
cutobjectWhere each source is cut: {stops, positions}
markPxdecimal | nullMark: last trade

Related: Price-level maps

  • Liquidation price map GET /v1/hypercore/liquidation-map HyperCore
    Liquidation prices of every open position, from Hyperliquid's formula on each account's state, bucketed like the stop map.
  • Liquidation map stream WS hc.liquidations.map HyperCore
    The GET /v1/hypercore/liquidation-map map, pushed on subscribe, then on each roll of the live positions (every 5 s) when it changes (whole, or as a JSON Patch).
  • Forced flow GET /v1/hypercore/forced-flow HyperCore
    Stop-loss / take-profit orders and liquidations on the same buckets: the cascade (stops + liquidations, with the move) and the take-profits (against it) at each price.
  • Forced flow stream WS hc.forced_flow.map HyperCore
    The GET /v1/hypercore/forced-flow map, pushed on subscribe, then on each roll of the live positions (every 5 s) when it changes (whole, or as a JSON Patch).
  • Stop map stream WS hc.stops.map HyperCore
    The GET /v1/hypercore/stops map, pushed on subscribe, then on each roll of the live positions (every 5 s) when it changes (whole, or as a JSON Patch).

More

Agent guide (agents.md)llms.txtOpenAPIMCP serverGet an API keyChangelog