NAV Navigation
English
HTTP

Upcoming Changes

Trailing Stop Order — Algo order enhancement

Last update: Aug 27, 2026

BloFin is adding trailing stop orders to the Open API, aligning API capabilities with the existing App/Web feature. A trailing stop order tracks favorable price movements using the last price and submits a market order when the price retraces by a preset callback amount from the extreme price reached after activation.

The feature is built on the existing algo order framework. No new endpoints or channels are introduced.

Place Algo Order POST /api/v1/trade/order-algo

  1. A new orderType enumeration value trailing_stop is added.
  2. New request parameters: callbackRatio (callback rate, 0.001–1, step 0.001), callbackSpread (callback price distance), and activePrice (activation price; if omitted, the order is activated immediately). Either callbackRatio or callbackSpread is required, but not both.
  3. size supports -1 for the entire position: the triggered market order is placed with the actual position size at the moment of triggering.
  4. positionId is required in Multi-Position mode (ignored otherwise), consistent with the Multi-Position conventions for TP/SL and algo orders.
  5. Activation and tracking both use the last price. For buy orders activePrice must be lower than the last price; for sell orders it must be higher; otherwise the order is rejected (order would immediately trigger).
  6. Trailing stop orders are executed at market price only; price must not be passed.

Get Algo Orders GET /api/v1/trade/orders-algo-pending / orders-algo-history

  1. orderType=trailing_stop is supported for filtering.
  2. New response fields: callbackRatio, callbackSpread, activePrice, moveTriggerPrice (current dynamic trigger price; empty = not yet activated, non-empty = activated and tracking) and positionId.
  3. The existing state enumeration is reused: live (placed; not activated, or activated and tracking) → effective (triggered, market order submitted) / canceled / order_failed. No new state values are introduced.
  4. The triggered market order may be split into multiple child orders; child order IDs are not returned in the algo order. Correlate child orders by instId and the triggering time window.

Amend Algo Order POST /api/v1/trade/amend-algo

  1. Trailing stop orders can be amended: newSize (positive values only; -1 is not supported), newCallbackRatio / newCallbackSpread (mutually exclusive per request; switching the callback form is supported) and newActivePrice (only before activation).
  2. Amending the callback of an activated order preserves the recorded extreme price; the dynamic trigger price is recalculated without resetting tracking.
  3. The existing requestId and ttl semantics apply.

Cancel Algo Order POST /api/v1/trade/cancel-algo

No changes. Trailing stop orders are canceled via the existing endpoint by algoId or clientOrderId. When the associated position is fully closed, liquidated, or ADLed, the reduce-side trailing stop order is automatically canceled with cancelType=system; it is recommended to check the position upon receiving a system cancellation and re-place the order if the position is non-zero.

WebSocket orders-algo channel

  1. Trailing stop order updates are pushed via the existing private channel with the new fields above.
  2. Messages are pushed on state changes and at the moment of activation (a live update carrying the first moveTriggerPrice); price movements during tracking are not pushed tick by tick.
  3. Amendment results are pushed via the amendResult field.

Limits & error codes

  1. Each trading account may have a maximum of 50 pending (untriggered) partial-position trailing stop orders, of which at most 10 per instrument. In addition, each position may have 1 full-position (size=-1) trailing stop order, which does not count toward the 50-order limit.
  2. New error codes for invalid callback parameters, invalid activation price, and the pending order limit will be published with the release. Multi-Position related errors reuse the unified Multi-Position error codes.

Effective date

To be announced.

2026-08-27

Spot API Launch

BloFin Spot API is now live and open to the public. It provides full REST and WebSocket support for spot trading. See the Spot API documentation for details.

Authentication, signature algorithm, and rate limits are consistent with the existing Futures API.

Delisted Instruments

Multi-Position Mode (Position-by-Order)

Multi-Position mode is now supported in the Open API. When enabled, each opening order creates an independent position with its own positionId, entry price, margin, leverage, and TP/SL, instead of being merged into a single position per instrument and direction. Available under Hedge Mode (long_short_mode) only; both cross and isolated are supported. Accounts that do not enable Multi-Position are not affected — new response fields return an empty string. See the Multi-Position Mode section for full details.

2026-08-19

Order Amendment

HTTP