Upcoming Changes

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.
  • 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",
    "makerU": "",
    "makerUSDC": "",
    "taker": "-0.001",
    "takerU": "",
    "takerUSDC": "",
    "ruleType": "normal",
    "ts": "1608623351857",
    "fiat": []
  }
  ]
}

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-07-02

• Added new endpoint

  • Get asset bills history

• Added new response parameter

  • Get asset bills details

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

2025-03-03

Withdrawal API adjustment for Turkey entity users

Due to compliance requirements, Bahamas entity users need to pass in the field rcvrInfo when making withdrawal.

Withdraw assets to the exchange wallet

If users withdraw assets to the exchange wallet, they need to provide exchange info & recipient information.

• Users can query supported exchanges through the endpoint of Get exchange list (public)
• Users need to pass in the following field information of the recipient (rcvrFirstName, rcvrLastName, rcvrCountry, rcvrCountrySubDivision, rcvrTownName, rcvrStreetName). For the exchange wallet belongs to business recipient, rcvrFirstName may input the company name, rcvrLastName may input "N/A", location info may input the registered address of the company. The examples are as follows:

Withdraw assets to the private wallet

If users withdraw assets to the private wallet, they need to provide recipient information.

• Users need to pass in the following field information of the recipient (rcvrFirstName, rcvrLastName, rcvrCountry, rcvrCountrySubDivision, rcvrTownName, rcvrStreetName). For the exchange wallet belongs to business recipient, rcvrFirstName may input the company name, rcvrLastName may input "N/A", location info may input the registered address of the company. The examples are as follows:

2025-02-12

• Added new parameters
  • Get balance
  • Get sub-account trading balance
  • Account channel

2024-11-14

• Adjusted response parameters
  • Get currencies

Before

After

• Added new endpoint
  • Get sub-account fee rates

2024-10-10

• Added new response parameters
  • Get currencies

• Added new response parameters
  • Get non-tradable assets

• Nitro spread supports market orders, the request and response parameter ordType adds the enumeration value market.

  • Place order
  • Get order details
  • Get active orders
  • Get orders (last 21 days)
  • Get orders history (last 3 months)
  • WS / Place order
  • Order channel

• Nitro spread adds a new order cancellation scenario, the cancelSource response parameter adds the enumeration value 15: Order canceled: The order price is beyond the limit.

  • Get order details
  • Get active orders
  • Get orders (last 21 days)
  • Get orders history (last 3 months)
  • Order channel

2024-10-04

• Added call auction details WebSocket channel
  • WS / Call auction details channel

2024-10-01

• Added public feature for endpoint:
  • GET / Announcements

2024-09-19

• Added new response parameters
  • Get account configuration

• Added new response parameters
  • Get leverage

• Added new response parameters
  
  • Algo order details
  • Algo order list
  • Algo order history
  • Algo orders channel
  • Advance algo orders channel

2024-09-18

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