# October 2026

## [October 13, 2026] Notice: API Adjustments for the RToken Matching Engine Upgrade

To provide deeper liquidity and a better trading experience, we will soon upgrade the matching engine for rToken (tokenized stock) trading pairs. During the upgrade, the order placement, order book, and fills endpoints will be adjusted accordingly. Please review the changes below and prepare your strategies and systems in advance.

rToken trading pairs will be migrated to the new matching engine in batches from October 14 to October 20. For the detailed migration schedule, please refer to [this article](https://www.bitget.com/support/articles/12560603897457).

### 1. Order placement

**Place Order**

- **HTTP REST:** `POST /api/v3/trade/place-order`; `POST /api/v3/trade/place-reality-order`<br/>
- **WebSocket Topic:** `place-order`<br/>

During and after the upgrade, the existing order placement endpoint URLs and parameter logic remain **fully compatible**. You can continue to use `place-order` and `place-reality-order` to place rToken orders. Note that modifying an rToken order is not supported — cancel the resting order and place a new one instead.

Once the matching engine upgrade is complete, the system will officially support smart liquidity routing via the `venue` parameter, covering two channels: internal (onshore) matching only, and the public market. In addition to the existing `gtd` time-in-force, a new `gtc` execution strategy will be supported. For rToken, `gtc` orders are valid for 90 days.

**Order Info**

- **HTTP REST:** `GET /api/v3/trade/order-info`
- **WebSocket Topic:** `order`

After placing an order, you can query the values of `venue` and `rTokenTimeInForce` via the REST order info endpoint or the WebSocket order channel.

### 2. Standard depth (order book) changes

If you use the standard depth endpoints/channels to retrieve rToken depth data, the adjustments after the matching engine upgrade are as follows.

After upgrading to the new matching system, the order book may briefly show crossed prices — this is expected behavior.

REST API

- **HTTP REST:** `GET /api/v3/market/orderbook`
- **Weekdays (market hours):** only returns level-1 (BBO) best bid/ask data.
- **Weekends (off-hours):** returns the requested number of levels based on the `limit` parameter.

WebSocket channels

- **`books1`**: pushed **at all times**, both during and outside market hours.
- **`books5` / `books50` / `books`**: pushed **only outside market hours**.

### 3. RToken depth changes

#### RToken merged depth (`reality-orderbook`)

- **HTTP REST:** `GET /api/v3/account/reality-orderbook`
- **WebSocket Topic:** `reality-orderbook`
- **Depth levels:** up to 85 levels.
- **Push frequency:** every 500ms when the depth copy has changed, or every 10s when unchanged.
- **Note:** after upgrading to the new matching system, the order book may briefly show crossed prices — this is expected behavior.

#### RToken segmented depth (`reality-orderbook-segmented`)

This upgrade introduces rToken segmented depth, to support trading use cases that need to distinguish onshore and offshore liquidity precisely.

This depth is only available for trading pairs that have completed the matching engine upgrade; pairs that have not completed the upgrade will not push data.

Note: segmented depth is scheduled to go live on October 20, 2026.

- **HTTP REST:** `GET /api/v3/account/reality-orderbook-segmented`
- **WebSocket Topic:** `reality-orderbook-segmented`
- **Depth levels:** up to 85 levels.
- **Push frequency:** every 500ms when the depth copy has changed, or every 10s when unchanged.
- **Note:** after upgrading to the new matching system, the order book may briefly show crossed prices — this is expected behavior.
- **Data structure:** in the pushed data, the `a` (Asks) and `b` (Bids) arrays are structured as follows:

  - `a[0]` / `b[0]`: price (String)
  - `a[1]` / `b[1]`: **onshore** quantity (String)
  - `a[2]` / `b[2]`: **offshore** quantity (String)

::::tip{title="Risk Notice and Recommendations"}

1. Please note the difference in depth-level push behavior between weekdays and weekends, to avoid issues caused by `books5` / `books50` not pushing during market hours.<br/>
2. To use the rToken segmented depth (`reality-orderbook-segmented`) endpoint, please contact your account manager to request whitelist access.<br/>

If you have any questions, please contact the API technical support team at any time.

::::

## [October 13, 2026] Added STP Group APIs

**New APIs:**

- `/api/v3/account/create-stp-groups` Create a custom Self-Trade Prevention (STP) group
- `/api/v3/account/stp-groups` Get the STP Group list and member sub-accounts
- `/api/v3/account/add-groups-members` Add sub-accounts to an STP Group
- `/api/v3/account/remove-groups-members` Remove sub-accounts from an STP Group


## [October 5, 2026] Reality Trading Guide: Added rToken Limit Order Trading Rules

- Reality Trading Guide

Changes:
- Added rToken limit order trading rules: if a single UID's terminal orders on a single trading pair exceed 2,000 within a statistical cycle with a fill rate below 10%, the limit order function for that trading pair will be restricted (error code `41121`). The restriction is automatically lifted if the conditions are not triggered again in the next statistical cycle (re-evaluated daily at 04:00 UTC+8).