API reference · Stops & take-profits

Stops stream

Every trigger order event: placed, triggered, canceled, and the order a trigger placed.

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

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

Parameters

ParamInExample or valuesMeaning
coinfilterBTCHyperCore market (BTC, @107, xyz:TSLA)
userfilter(optional)Account: 0x address or a named wallet's handle
statusfilter(empty), open, triggered, filled, canceledStatus: open, triggered, canceled, filled…
kindfilter(empty), stop, take_profitstop | take_profit

Subscribe

{"op":"subscribe","channel":"hc.stops","filter":{"coin":"BTC"}}

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

Response fields

FieldTypeMeaning
snapshot: trueHcStopEvent[]last 50 trigger-order events
dataHcStopEventevery status of a stop-loss / take-profit order (placed, triggered, canceled, rejected) and of the order its trigger places (filled, canceled: triggered true): the hc.orders fields + is_position_tpsl, kind, exec (market | limit), triggered: {coin, side, px, sz, orig_sz, status, order_type, tif, oid, user, block, time, …}
data.kindstop | take_profitStop-loss or take-profit (from the order type)
data.execmarket | limitWhat the trigger places: a market or a limit order
data.triggeredbooleantrue: the order a trigger placed (filled, canceled)

Related: Stops & take-profits

  • Stop map GET /v1/hypercore/stops HyperCore
    Open stop-loss and take-profit orders of one coin, bucketed by trigger price around the mark.
  • Triggered stops GET /v1/hypercore/stops/triggered HyperCore
    Stop-loss and take-profit orders that fired, newest first, with the fill they got.
  • Wallet stops GET /v1/hypercore/wallet/{address}/stops HyperCore
    One wallet's open trigger orders, or with history=1 every status event of them.

More

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