Upcoming Changes

Delist initial snapshot and checksum field in order book channels

Last update: February 12, 2026

To improve the user experience and the stability of the market data push，the following order book channels will delist the initial snapshot and checksum push field.
After the delisting, the initial snapshot and checksum push field will not be returned, please use the GET / Order book endpoint to get the snapshot data, and use seqId/prevSeqId to verify the data accuracy before the delisting.

Note: The WebSocket connection now fully enforces TLS (wss://), providing protection against eavesdropping, tampering, and ensuring data integrity. Together with rigorous validation of seqId and prevSeqId, it effectively prevents out-of-order messages, partial data loss, or malicious injection, achieving integrity protection equivalent to, or even stronger than, the original checksum mechanism.

The delisting date of demo trading environment: early May 2026
The delisting date of production environment: early August 2026

• Delist the initial snapshot and checksum push field.

  • WS / Order book channel
    • books/books-elp/books-l2-tbt/books50-l2-tbt
      
      

• How to manage a local order book correctly

  1. Open a JSON WebSocket connection and subscribe to the incremental order book channel.
  2. Buffer the events received from the stream. Ignore the first event received (action is snapshot), and record the prevSeqId of the second event.
  3. Get a depth snapshot from GET / Order book, e.g. https://www.okx.com/api/v5/market/books?instId=BTC-USDT-SWAP&source=0
  4. If the seqId from the snapshot is strictly less than the prevSeqId from step 2, go back to step 3.
  5. In the buffered events, discard any event where stream seqId is <= snapshot seqId of the snapshot.
  6. The first buffered event should satisfy the condition: stream prevSeqId <= snapshot seqId < stream seqId.
  7. Set your local order book to the snapshot. Its sequence ID is snapshot seqId.
  8. Apply the update procedure below to all buffered events, and then to all subsequent events received.
     • For each price level in bids and asks, set the new quantity in the order book:
       • If the price level does not exist in the order book, insert it with new quantity.
       • If the quantity is zero, remove the price level from the order book.
     • Set the order book sequence ID to the latest sequence ID (seqId) in the processed event.
       Note: Not all snapshot seqId will appear in the books-l2-tbt channels.
       
       

• To support using the GET / Order book endpoint to manage the local order book, the endpoint already added the seqId response parameter, to support getting the snapshot data of the ELP order book, source request parameter will be added on March 5, 2026.

Delist instId request parameter in WS order operation channels

Last update: January 29, 2025

To reduce latency of WebSocket order operations, the following order operation channels have introduced a new request parameter, instIdCode. In the demo trading environment, the instId request parameter has been delisted. In the production environment, instId will be delisted in phases. After the delisting, any instId value provided will be ignored.

• Phase 1 delisting date: March 5, 2026. The affected channels include:
  
  • WS / Place order
  • WS / Place multiple orders
• Phase 2 delisting date: March 10, 2026. The affected channels include:
  
  • WS / Amend order
  • WS / Amend multiple orders
  • WS / Cancel order
  • WS / Cancel multiple orders

Note: Users can use the Get instruments interface to map instIdCode to instId.

OKX trading fee scheme update

Last updated: 2025/11/3

OKX will update the trading fee scheme for improved fee differentiation across tiers. Please refer to the announcement for more details.

Instruments endpoint/channel

• Add a new response parameter groupId to indicate which group a specific symbol belongs to.
  • Get instruments (private)
  • Get instruments (public)
  • Instruments channel

Response Parameters

Response Example

{
    "code":"0",
    "msg":"",
    "data":[
      {
            "alias": "",
            "auctionEndTime": "",
            "baseCcy": "BTC",
            "category": "1",
            "ctMult": "",
            "ctType": "",
            "ctVal": "",
            "ctValCcy": "",
            "contTdSwTime": "1704876947000",
            "expTime": "",
            "futureSettlement": false,
            "groupId": "13"
            "instFamily": "",
            "instId": "BTC-USDT",
            "instType": "SPOT",
            "lever": "10",
            "listTime": "1606468572000",
            "lotSz": "0.00000001",
            "maxIcebergSz": "9999999999.0000000000000000",
            "maxLmtAmt": "1000000",
            "maxLmtSz": "9999999999",
            "maxMktAmt": "1000000",
            "maxMktSz": "",
            "maxStopSz": "",
            "maxTriggerSz": "9999999999.0000000000000000",
            "maxTwapSz": "9999999999.0000000000000000",
            "minSz": "0.00001",
            "optType": "",
            "openType": "call_auction",
            "preMktSwTime": "",
            "quoteCcy": "USDT",
            "tradeQuoteCcyList": [
                "USDT"
            ],
            "settleCcy": "",
            "state": "live",
            "ruleType": "normal",
            "stk": "",
            "tickSz": "0.1",
            "uly": "",
            "instIdCode": 1000000000
        }
    ]
}

Get fee rates endpoint

• Add new response parameter feeGroup. Fields that will be deprecated: maker, makerU, makerUSDC, taker, takerU, takerUSDC.
  • Get fee rates

Response Parameters

Response Example

{
  "code": "0",
  "msg": "",
  "data": [{
    "category": "1", //Deprecated
    "delivery": "",
    "exercise": "",
    "feeGroup": [
        {
            "taker": "0.001",
            "maker": "0.0001",
            "groupId": "1"
        },
        {
            "taker": "0.01",
            "maker": "0.001",
            "groupId": "2"
        },
        {
            "taker": "0.1",
            "maker": "0.01",
            "groupId": "3"
        },
        ......
    ],
    "instType": "SPOT",
    "level": "lv1",
    "maker": "-0.0008", //Deprecated
    "makerU": "", //Deprecated
    "makerUSDC": "", //Deprecated
    "taker": "-0.001", //Deprecated
    "takerU": "", //Deprecated
    "takerUSDC": "", //Deprecated
    "ruleType": "normal",
    "ts": "1608623351857",
    "fiat": []
  }
  ]
}

Delist old attached stop profit and stop loss parameters

Last update: November 20, 2025

In order to streamline the placement parameters and order information parameters, Open API will delist the old stop-loss and take-profit parameters.

• Related request parameters will be delisted in mid-October or later (the parameters in the array attachAlgoOrds aren’t affected), no specific time will be further notified.
  • Order channel
    
  • Get order details
    
  • Get order list
    
  • Get order history (last 7 days)
    
  • Get order history (last 30 days)
    

2026-02-12

• Added new parameters
  • Get instruments (private)
  • Get instruments (public)
  • Instruments channel

2026-01-15

Rename XAUT Perpetual Contract

To enhance your trading experience, OKX renamed XAUTUSDT perpetual to XAUUSDT perpetual and the trading of XAUTUSDT perpetual will be suspended from 8:05 am to 8:25 am on Jan 15, 2026 (UTC), more details can be found in announcement details.

• When renaming:

  • Instruments channel will first push the update data of instId: XAUT-USDT-SWAP, state: expired, then push the update data of instId: XAU-USDT-SWAP, state: live.
    

• After renaming:

  • The instId, instFamily, uly in the pushed data will use the new parameter values.
  • OKX will no longer support subscribing to the WebSocket channels for this perpetual using instId: XAUT-USDT-SWAP or instFamily: XAUT-USDT, nor will it support sending HTTP requests via OpenAPI with these parameters. Please use instId: XAU-USDT-SWAP or instFamily: XAU-USDT for related trading operations after the contract is renamed.
    
  • For the trades and regular snapshot push of positions channels, the old subscriptions will still push data, please resubscribe using the new parameter values after the renaming.
    
  • For order book channels, old subscriptions will continue to receive data. After the renaming, please first cancel the subscription using the new parameter values, then resubscribe using the new values.
    
  • For other channels, they will no longer push any data, please resubscribe using the new parameter values after the renaming.
    
  • instIdCode will remain unchanged.

The parameters to be renamed are as follows:

2025-11-20

• Added new request parameter instIdCode
  • WS / Place order
  • WS / Place multiple orders
  • WS / Amend order
  • WS / Amend multiple orders
  • WS / Cancel order
  • WS / Cancel multiple orders

Note: You can use the Get instruments interface to map instIdCode to instId.

2025-09-03

• Fiat deposits and withdrawals are supported.

2025-08-20

Unified USD orderbook revamp

To revamp unified USD orderbook, more details for the first type users, more details for the second type users. OKX delisted the Crypto-USDC trading pairs and upgrade the Crypto-USD trading pairs for accessibility to all users.

Users are categorized into two types based on their country or region, with varying solutions for each. If you get valid data from GET /api/v5/account/instruments?instType=SPOT&instId=BTC-USD, you belong to the first type users, if you get an empty array [] data from that URL, you belong to the second type.

• If you are going to trade Crypto-USDC pairs after the revamp:
  • The instId should be set to Crypto-USD, such as BTC-USD.
  • The tradeQuoteCcy is used to determine the settlement quote currency and must be set as USDC.
  • The value for tradeQuoteCcy should be one of the enumerated values from tradeQuoteCcyList, which can be obtained from the endpoint Get instruments (private).
• What you need to do:
  • For the first type users:
    • Regarding Trade, Algo Trading and and in Block Trading, you currently have two options to trade Crypto-USDC. The first option is to trade directly with "instId": "Crypto-USDC" without specifying tradeQuoteCcy. The second option is to trade using "instId": "BTC-USD" with "tradeQuoteCcy": "USDC". The first option will not be available after the revamp. For more details, please refer to the Example 1 below.
  • For the second type of users, you are allowed to trade only with "instId": "Crypto-USDC" before the revamp. Afterward, you must use "instId": "Crypto-USD" with "tradeQuoteCcy": "USDC".
  • When trading Crypto-USDC after the revamp, Get maximum available balance/equity and Get maximum order quantity will also need to use "instId": "BTC-USD" with "tradeQuoteCcy": "USDC".
  • For market data related Crypto-USDC and Crypto-USD trading, after the revamp, they will share the same order book, both using "instId": "Crypto-USD", such as BTC-USD. The tradeQuoteCcy is not supported.

Example 1: Placing an order with BTC-USDC:

2025-08-14

• MARGIN and OPTION trading are permitted in specific countries and regions.

2025-07-08

Open API supports Unified USD Orderbook

For more details, please refer to Unified USD Orderbook FAQ

• Added new request parameter
  
  • Place order
    
  • Place multiple orders
    
  • Place order channel
    
  • Place multiple orders channel
    
  • Place algo order
    
  • Get maximum available balance/equity
    
  • Get maximum order quantity

• Added new response parameter
  • Get instruments (private)
  • Get instruments (public)

• Added new response parameter
  • Order details
  • Order List
  • Order history (last 7 days)
  • Order history (last 3 months)
  • Order channel
  • Algo order details
  • Algo order list
  • Algo order history
  • Algo orders channel
  • Advance algo orders channel

Trades channel adds seqId field

• WS / Trades channel

Note: The seqId may be the same for different trade updates that occur at the same time.

2025-07-02

• Added new endpoint

  • Get asset bills history

• Added new response parameter

  • Get asset bills details

2025-06-26

• Futures and swap trading are permitted in specific countries and regions.

2025-06-24

• Added new endpoint
  • Withdrawal

2025-05-28

• Added endpoints. Bills details (since 2021) endpoints below have been released in production
  • Apply bills details (since 2021)
  • Get bills details (since 2021)

2025-04-17

• Added endpoints

  • Create sub-account
    
  • Create an API Key for a sub-account
    
  • Query the API Key of a sub-account
    
  • Delete the API Key of sub-accounts
    
    

• Added new error codes

2024-09-18

• Added new endpoints:
  • GET / Announcements
  • GET / Announcement types