Copy page

Changelog

November 2026

[November 5, 2026] Notice: Adjustment to rToken Order Routing Strategy (venue) Enum Values

• Effective date: November 5, 2026

The enum values of the venue (order routing strategy) parameter in the rToken order placement and order query APIs (REST and WebSocket) are adjusted as follows:

Before	After	Description
internalization	internal_market	Orders are matched within the exchange and are not submitted to the U.S. stock broker
-	lit_market	Orders are submitted to the U.S. stock broker and are not matched within the exchange
lit_market	Omitted / default	Orders are first matched internally within the exchange at the best price; any unfilled portion is submitted to the broker

Important Notes:

1. internalization is renamed to internal_market with no change in meaning: "orders are matched within the exchange and are not submitted to the U.S. stock broker." Please replace this enum value with internal_market.
2. Orders previously shown as lit_market in order details will be shown as default after the adjustment, meaning "orders are first matched internally within the exchange at the best price; any unfilled portion is submitted to the broker." Please update the parsing logic for order details on your side accordingly.
3. The new lit_market means "orders are submitted to the broker for execution and are not matched within the exchange." This differs from the meaning of lit_market shown in order details before the adjustment, so please distinguish between the two carefully.
4. Omitting venue when placing an order applies the default strategy. The accepted enum values for the order placement API are internal_market and lit_market.
5. The venue field returned in order details will consistently use the adjusted enum values.

Please adjust the venue parameter according to your trading strategy. For detailed routing and matching rules, please refer to the rToken Trading Guide.
If you encounter any parameter validation or enum parsing issues after November 5, please contact us promptly and we will be happy to assist.

[November 4, 2026] New Affiliate, Savings, SharkFin and Broker APIs for the Unified Account

New APIs:

Affiliate (/api/v3/affiliate/*):

• GET /api/v3/affiliate/customer-list — query the list of your direct customers
• GET /api/v3/affiliate/customer-asset — query the assets of your direct customers
• GET /api/v3/affiliate/customer-trade-volume — query the trading volume of your direct customers
• GET /api/v3/affiliate/customer-deposit — query the deposit records of your direct customers
• GET /api/v3/affiliate/customer-kyc-result — query the KYC result of your direct customers
• GET /api/v3/affiliate/customer-commission — query your direct commission records
• GET /api/v3/affiliate/sub-customer-list — query the list of your sub-customers
• GET /api/v3/affiliate/sub-affiliate-info — query the information of your sub-affiliates
• GET /api/v3/affiliate/sub-affiliate-commission — query the commissions of your sub-affiliates

Savings (/api/v3/earn/savings/*):

• GET /api/v3/earn/savings/product — query the savings product list
• GET /api/v3/earn/savings/account — query the savings account information
• GET /api/v3/earn/savings/assets — query savings assets
• GET /api/v3/earn/savings/records — query savings records
• GET /api/v3/earn/savings/subscribe-info — query the subscription details of a savings product
• POST /api/v3/earn/savings/subscribe — subscribe to a savings product
• GET /api/v3/earn/savings/subscribe-result — query the savings subscription result
• POST /api/v3/earn/savings/redeem — redeem a savings product
• GET /api/v3/earn/savings/redeem-result — query the savings redemption result

SharkFin (/api/v3/earn/sharkfin/*):

• GET /api/v3/earn/sharkfin/product — query the SharkFin product list
• GET /api/v3/earn/sharkfin/account — query the SharkFin account information
• GET /api/v3/earn/sharkfin/assets — query SharkFin assets
• GET /api/v3/earn/sharkfin/records — query SharkFin records
• GET /api/v3/earn/sharkfin/subscribe-info — query the subscription details of a SharkFin product
• POST /api/v3/earn/sharkfin/subscribe — subscribe to a SharkFin product
• GET /api/v3/earn/sharkfin/subscribe-result — query the SharkFin subscription result

Broker (/api/v3/broker/*):

• POST /api/v3/broker/modify-subaccount-email — bind or modify the email address of a sub-account
• GET /api/v3/broker/subaccount-email — query the email address bound to a sub-account
• GET /api/v3/broker/trade-volume — query the trading volume of broker sub-accounts
• GET /api/v3/broker/total-commission — query total broker commission data
• GET /api/v3/broker/order-commission — query broker order commission (rebate) data
• GET /api/v3/broker/rebate-info — query a user's broker rebate information

[November 3, 2026] API Parameter Updates

Interface:

• /api/v3/account/sub-transfer
• /api/v3/cfd/account/instruments
• WebSocket place-order channel
• WebSocket liquidation channel

Changes:

• /api/v3/account/sub-transfer: Changed clientOid request parameter max length from 64 to 50 characters.
• /api/v3/cfd/account/instruments: Added currentTimezone String response parameter: the instrument's trading timezone, as a UTC offset in hours (e.g. +2 means UTC+2).
• WebSocket place-order channel: Added bboLevel String request parameter (BBO level for limit orders: queue1/queue5/counterparty1/counterparty5; ignored for market orders), and slippageTolerance String request parameter (slippage percentage for market orders, default 2%, range [0.01, 0.05]).
• WebSocket liquidation channel: Added symbol String request parameter: when provided, only public liquidation data for the specified symbol will be pushed.

[November 2, 2026] FastAPI Signature Algorithm Upgrade

• Release date: November 3, 2026

The FastAPI request signature algorithm is being upgraded from MD5withRSA to SHA256withRSA. You only need to change the hash algorithm from MD5 to SHA-256 in both your request-signing code and your callback signature verification code. For example, in Java, replace Signature.getInstance("MD5withRSA") with Signature.getInstance("SHA256withRSA"); the same applies to other languages. The estimated effort is under one hour, plus sandbox testing.
For code examples of signing and RSA encryption/decryption, please refer to the FastAPI Integration Guide
For the detailed migration timeline, please refer to Bitget FastAPI Signature Algorithm Upgrade Notice