API reference · Price-level maps

Forced flow stream

The GET /api/hypercore/forced-flow map, pushed whole on subscribe and every 5 s when it changes.

  • Elysium: not served
  • HyperCore
  • HyperEVM: not served
  • Not on Elysium or HyperEVM: a channel of HyperCore only

WebSocket channel hc.forced_flow.map on wss://api.femtos.xyz/v1/ws

Parameters

ParamInExample or valuesMeaning
coinfilterBTCHyperCore market
bucketsfilter40Buckets (1..400)
stepfilter(optional)Bucket width, in price (instead of buckets)
range_pctfilter10Grid: mark ± range_pct % (default 10)

Subscribe

{"op":"subscribe","channel":"hc.forced_flow.map","filter":{"coin":"BTC","buckets":"40","range_pct":"10"}}

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

Response fields

FieldTypeMeaning
snapshot: trueobjectevery frame: the full GET /api/hypercore/forced-flow answer

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 /api/hypercore/liquidation-map map, pushed whole on subscribe and every 5 s when it changes.
  • 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.
  • Stop map stream WS hc.stops.map HyperCore
    The GET /api/hypercore/stops map, pushed whole on subscribe and every 5 s when it changes.

More

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