Skip to main content

Changelog

Last updated: 2026-06-29

This page records confirmed Deepcoin API changes, including new endpoints, behavior changes, deprecations, rate limit updates, and documentation corrections that may affect API integration.

Upcoming Changes​

There are no confirmed upcoming API changes at this time.

Released Changes​

2026-06-29​

Added: WebSocket batch cancel and batch amend order​

  • Type: Added
  • Scope: WebSocket
  • Change: Private WebSocket now supports batch cancel order via the batch-cancel-order action (up to 50 items per request) and batch amend order via the batch-replace-order action (up to 20 items per request), with per-item result codes and messages in the response.
  • User impact: Existing WebSocket trade and single-order cancel/amend endpoints are unchanged. Users can cancel or amend multiple orders in a single WebSocket request, reducing network round trips.
  • Related docs: WS Trade

2026-06-25​

Updated: Position copy-trading tags​

  • Type: Updated
  • Scope: Account
  • Change: GET /deepcoin/account/positions now returns isLeading and isFollow in each position item to identify leading copy-trade positions and copied positions.
  • User impact: Existing position fields are unchanged. Users can use the new boolean fields to distinguish normal, leading, and copied positions without deriving the status from internal copy-trading identifiers.
  • Related docs: Get Positions

2026-06-19​

Added: WebSocket batch order placement​

  • Type: Added
  • Scope: WebSocket
  • Change: Private WebSocket now supports batch order placement via the batch-orders action. Send {"action":"batch-orders","param":{"id":"...","args":[...]}} to submit up to 5 orders in a single request. Each order supports the same fields as REST batch orders (instId, tdMode, side, ordType, sz, px, etc.), with optional take-profit and stop-loss trigger prices.
  • User impact: Existing WebSocket trade and REST order endpoints are unchanged. Users can reduce network round trips when submitting multiple orders simultaneously.
  • Related docs: WS Trade

2026-06-12​

Added: Trading data market endpoints​

  • Type: Added
  • Scope: Market
  • Change: Added GET /deepcoin/market/open-interest-volume, GET /deepcoin/market/long-short-ratio, and GET /deepcoin/market/taker-volume for querying contract trading data by product ID, granularity, optional time range, and limit.
  • User impact: Existing market APIs are unchanged. Users can query contract open interest and volume, long/short account ratio, and taker buy/sell volume without integrating the underlying chart configuration API directly.
  • Related docs: Get Open Interest and Volume, Get Long/Short Ratio, Get Taker Buy/Sell Volume, Rate Limit Rules

2026-06-11​

Added: Private WebSocket channel subscription​

  • Type: Added
  • Scope: WebSocket
  • Change: Private WebSocket now supports subscribing to specific channels via the tables parameter. Send {"action":"subscribe","tables":["Account","AccountDetail","Order","Position","Trade","TriggerOrder"]} to subscribe to only the channels you need. If tables is not specified, all channels are subscribed by default. To unsubscribe from specific channels, re-subscribe with a tables array that only includes the channels you want to keep.
  • User impact: Existing private WebSocket connections are unchanged. Users who only need specific push channels can reduce data transfer by subscribing to a subset.
  • Related docs: Private WebSocket Subscribe

Added: Mark price query​

  • Type: Added
  • Scope: Market
  • Change: Added GET /deepcoin/market/mark-price for querying perpetual contract mark prices. instType=SWAP is required. Users may query by instId, by uly, or omit both to return all supported contract mark prices. If both instId and uly are provided, instId takes priority.
  • User impact: Existing market ticker and mark-price K-line APIs are unchanged. Users who only need the current mark price can use this endpoint instead of deriving it from ticker or K-line data.
  • Related docs: Get Mark Price

2026-06-10​

Added: Cancel and amend order client order ID support​

  • Type: Added
  • Scope: Trade
  • Change: POST /deepcoin/trade/cancel-order and POST /deepcoin/trade/replace-order now support locating active orders by clOrdId. The client order ID must match ^[A-Za-z0-9]{1,20}$.
  • User impact: Existing cancel and amend requests by ordId or OrderSysID are unchanged. Users can now cancel or amend active orders by clOrdId; if both system order ID and clOrdId are provided, the system order ID takes priority. If one clOrdId matches multiple active orders, use the system order ID.
  • Related docs: Cancel Order, Amend Order

2026-06-04​

Added: Place order and get order client order ID support​

  • Type: Added
  • Scope: Trade
  • Change: POST /deepcoin/trade/order now accepts clOrdId as a client-assigned order ID and returns it in order responses. GET /deepcoin/trade/order now supports querying a single order by clOrdId.
  • User impact: Existing order placement and order query by ordId are unchanged. Users can assign clOrdId when placing orders and later query by it; if both ordId and clOrdId are provided, ordId takes priority.
  • Related docs: Place Order and Get Order Info

2026-06-03​

Added: Unified account balances query​

  • Type: Added
  • Scope: Account
  • Change: Added GET /deepcoin/account/all-balances for querying balances across Funding, Spot, USDT Swap, Coin-margined Swap, Bonus, Rebate, Event Contract, Copy Trading, and Robot accounts. The response includes account-level balance details, available balance, frozen balance, unrealized profit, equity, USD equity valuation, and summary fields.
  • User impact: Existing GET /deepcoin/account/balances is unchanged. Users who need the same account structure shown in Deepcoin products can use the new endpoint instead of querying only by trading product type.
  • Related docs: Get Unified Account Balances, Rate Limit Rules

2026-06-02​

Added: Get order query​

  • Type: Added
  • Scope: Trade
  • Change: Added GET /deepcoin/trade/order for querying a single order by order ID. The endpoint checks historical orders first and then current pending orders when no historical match is found.
  • User impact: Existing order query endpoints are unchanged. Users who need one endpoint for single-order status lookup can use this API.
  • Related docs: Get Order Info

2026-05-28​

Added: Account trade fee query​

  • Type: Added
  • Scope: Account
  • Change: Added GET /deepcoin/account/trade-fee for querying the current account's trading fee rates by product type, product ID, or instrument family.
  • User impact: Existing account and trading APIs are unchanged. Users who need fee-rate display, reconciliation, or routing logic can integrate the new endpoint.
  • Related docs: Get Fee Rates

2026-05-20​

Added: Account leverage and position history APIs​

  • Type: Added
  • Scope: Account
  • Change: Added GET /deepcoin/account/leverage-info for querying leverage settings and GET /deepcoin/account/positions-history for querying historical contract positions.
  • User impact: Existing position and leverage APIs are unchanged. Users who need to verify leverage configuration or backfill closed-position data can integrate these endpoints.
  • Related docs: Get Leverage, Get Positions History

Added: Split-position increase and merge APIs​

  • Type: Added
  • Scope: Trade
  • Change: Added split-position management endpoints: POST /deepcoin/trade/increase-position for increasing an existing split position, and POST /deepcoin/trade/merge-positions for merging eligible split positions of the same product and direction.
  • User impact: Existing order and position APIs are unchanged. These endpoints only apply to contract split positions; users should pass a valid posId returned by the positions API.
  • Related docs: Increase Position, Merge Positions

Added: REST API rate limit rules page​

  • Type: Documentation update
  • Scope: REST API
  • Change: Added a rate limit reference page covering default request limits for account, market, trade, copy trading, internal transfer, sub-account, affiliate, and asset APIs.
  • User impact: API behavior is unchanged. Users can use this page to plan request pacing and avoid frequency-limit errors.
  • Related docs: Rate Limit Rules