Skip to content

2026-5-20

2026-05-20

Futures V3 & Testnet — Chase Order & BBO-Pegged Order Support

  • Added 3 new optional parameters to the POST /fapi/v3/order — Place Order endpoint in Futures V3 and Futures Testnet (EN & ZH):
  • pegPriceType (ENUM) — BBO peg mode: COUNTERPARTY_1 or QUEUE_1. When set on a LIMIT order, the engine resolves the actual price from the order book at trigger time using the BBO + pegOffset. Defaults to no peg.
  • pegOffset (DECIMAL) — Signed offset from BBO when pegPriceType is set. BUY: non-positive (e.g. -0.5); SELL: non-negative. Must be a tickSize multiple.

  • priceLimit (DECIMAL) — Absolute price cap for BBO-pegged orders. BUY: ceiling; SELL: floor. Must be > 0 and a multiple of tickSize. Defaults to no cap.

  • Added a new endpoint POST /fapi/v3/chase — Place Chase Order (TRADE) in Futures V3 and Futures Testnet (EN & ZH), placed between Modify Order and Place Multiple Orders:

  • Places a BBO-pegged GTX limit order with automatic price tracking — the strategy service polls each tick and re-pegs the order to bid1 − chaseOffset (BUY) or ask1 + chaseOffset (SELL).
  • Supports quantityUnit (BASE / QUOTE), chaseOffset / chaseOffsetType, maxChaseOffset / maxChaseOffsetType (ABSOLUTE / PERCENTAGE), and priceLimit.
  • The chase auto-cancels with reason OFFSET_CANCELLED when the market moves beyond maxChaseOffset from the original BBO; clamps at priceLimit if the new peg would breach it.
  • timeInForce defaults to GTX (post-only); NO_FILL is not allowed.

  • clientStrategyId length must be ≤ 28 characters and match ^[\.A-Z\:/a-z0-9_-]{1,28}$.

  • Updated Modify Order notes in Futures V3 and Futures Testnet (EN & ZH):

  • Added a note that BBO-pegged orders (placed with pegPriceType = COUNTERPARTY_1 / QUEUE_1) cannot have their price re-resolved via plain modify — to continuously track the BBO use a Chase order (POST /fapi/v3/chase).