Upcoming Changes

WebSocket Orders Channel: Push Behavior Adjustment

Last update: Jul 22, 2026

To help clients more clearly determine the final status of post-only new orders (including mmp_and_post_only) and upcoming rpi new orders — and to avoid scenarios where an order is still canceled after the client has already received a state: live event — OKX will adjust the state: live event behavior for post-only and rpi orders in the Order channel.

Impact details

• The state: live event will be pushed only after the order has successfully entered the order book, instead of immediately upon order receipt (a delay of approximately 1 ms).
• In failed order placement scenarios (price crosses the BBO and is canceled), the state: live update will be removed entirely — only a state: canceled update will be pushed.

Effective date

• For rpi orders (including elp orders, which will be deprecated): demo trading — July 23, 2026; production — July 28, 2026.
• For post_only and mmp_and_post_only orders: both demo trading and production — mid-August, 2026.

Scope of impact

The order types affected are: post_only, mmp_and_post_only, and rpi (Retail Price Improvement).

Other order types — such as limit (regular limit orders), market (market orders), ioc, and fok — will have their push behavior remain unchanged.

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": []
  }
  ]
}

2026-07-28

Rebranding ELP to RPI (Retail Price Improvement) Program

OKX is rebranding Enhanced Liquidity Program (ELP) to Retail Price Improvement (RPI). This includes a new consolidated RPI order book (books-rpi) over WebSocket and REST, a renamed rpi maker order type (replacing elp), an expanded rpiTakerAccess order parameter (replacing isElpTakerAccess), a new rpiPxRound parameter for the RPI maker spacing rule, and renamed rpi/rpiMaker account fields.

ELP name deprecation deadline: October 31, 2026

OKX will run the ELP and RPI names in parallel until this date, in two distinct ways:

• Renamed fields — both accepted; the RPI-named field wins when a request or response carries both:
  • isElpTakerAccess → rpiTakerAccess
  • elp → rpi
  • elpMaker → rpiMaker
• Renamed values — mutually exclusive; send or expect one or the other, not both:
  • ordType: elp → ordType: rpi
  • books-elp → books-rpi

Existing integrations continue to operate without changes. The ELP names will be retired after the sunset date above — migrate every integration to the RPI names before then.

New consolidated order book: books-rpi (WS + REST)

• Added books-rpi, consolidating organic and RPI liquidity into a single depth stream — available as a public WebSocket channel (/ws/v5/public, 400 depth levels, full snapshot + incremental updates every 100 ms) and a REST endpoint (GET /api/v5/market/books-rpi, refreshed every 200 ms server-side). No checksum; WS sequencing relies on seqId/prevSeqId. Supersedes books-elp (see migration note above).
  • WS / Order book channel
  • GET / RPI order book

Each asks/bids element is [price, totalQty, nonRpiQty, count] — totalQty is the total depth at that price level, nonRpiQty is the organic-only portion, count is the aggregated order count at that level.

REST request: instId (required), sz (depth per side, max 400, default 1).

Taker parameter: rpiTakerAccess (replaces isElpTakerAccess)

• rpiTakerAccess renames and expands isElpTakerAccess to apply to all standard order types (limit, market, fok, ioc; previously ioc only) and to be settable on amend. isElpTakerAccess remains accepted as an alias until the sunset date (see migration note above).
• Error code 54045 (previously returned when a non-ioc order attempted to take RPI liquidity) is retired — unreachable now that rpiTakerAccess is valid on all order types.

Applies to place / amend, REST + WS: - POST / Place order - POST / Place multiple orders - POST / Amend order - POST / Amend multiple orders - WS / Place order - WS / Place multiple orders - WS / Amend order - WS / Amend multiple orders

Maker order type: rpi (replaces elp)

• To place an RPI maker order, set ordType to rpi instead of elp. elp remains accepted until the sunset date (see migration note above) — ordType takes a single value, so send one or the other, not both.

Applies to place, REST + WS: - POST / Place order - POST / Place multiple orders - WS / Place order - WS / Place multiple orders

Maker parameter: rpiPxRound

• rpiPxRound is a new parameter for the RPI maker spacing rule (see below). Effective only on RPI maker orders (ordType: rpi); silently ignored on non-RPI orders and on OPTION/EVENTS.

Applies to place / amend, REST + WS (same interfaces as rpiTakerAccess above).

• Added a new amendSource value 6 on the orders WS private channel: order price adjusted (rounded) by the system to satisfy the RPI maker spacing rule, triggered by rpiPxRound.
  • WS / Order channel

RPI maker spacing rule

RPI maker orders are subject to a spacing rule (rpiMinLevel / rpiMinPxBand below). An order that violates it is rejected unless rpiPxRound is true, in which case the price is auto-rounded to the nearest compliant level instead (see rpiPxRound above).

• Added new response parameters rpiMinLevel and rpiMinPxBand to expose the per-instrument spacing thresholds.
  • GET / Get instruments (public)

RPI maker permission field: rpi (replaces elp)

• Added new response parameter rpi to indicate RPI maker permission. elp remains accepted as an alias until the sunset date (see migration note above).
  • GET / Get instruments (private)

RPI maker fee rate field: rpiMaker (replaces elpMaker)

• Added new response parameter rpiMaker to indicate the RPI maker effective fee rate. elpMaker remains accepted as an alias until the sunset date (see migration note above).
  • GET / Get fee rates

Trade source field: source

• Response field source value 1 on GET /api/v5/market/trades is now described as RPI order (previously ELP order). The returned value 1 itself is unchanged — only the description text is updated.
  • GET / Trades

Error code changes

Error messages updated from ELP to RPI:

Deprecated error code:

2026-07-23

GLP Performance API for market makers

Two new read-only endpoints for Global Liquidity Program (GLP) market makers to query their assessment performance metrics. Only enrolled GLP accounts can access these endpoints; sub-accounts resolve to their master account.

• The following new endpoints have been added:
  • GET / Get GLP today performance
  • GET / Get GLP historical performance

GET / Get GLP today performance

Retrieve the current day and month-to-date (MTD) GLP performance snapshot for the authenticated account, covering all enrolled programs (Spot / Perp / Expiry & Nitro). No request parameters; the account is resolved from the API key.

Rate Limit: 5 requests per 2 seconds

Rate limit rule: User ID

Permission: Read

HTTP Request

GET /api/v5/users/glp/today-performance

Request Example

GET /api/v5/users/glp/today-performance

Request Parameters

None. The account is resolved from the authenticated session.

Response Example

{
    "code": "0",
    "msg": "",
    "data": [
        {
            "dataReady": true,
            "dataDate": "2026-07-13",
            "account": {
                "masterAccountId": "832545488879789797",
                "combinedAccountIds": ["832545488879789798"]
            },
            "programs": [
                {
                    "program": "SPOT",
                    "marketMakerBusinessId": "1",
                    "enrollmentStatus": "ENROLLED",
                    "marketMakerLevelId": "42",
                    "enrolledTierDisplay": "Tier 1 Class A",
                    "qualifyingPool": "TYPE_A",
                    "qualifyingRows": ["TOTAL"],
                    "daily": {
                        "volume": {
                            "typeA": {"maker": "1000000.00", "taker": "1000000.00"},
                            "typeBTotal": {"maker": "1000000.00", "taker": "1000000.00"},
                            "tradfiX2": {"maker": "1000000.00", "taker": "1000000.00"},
                            "total": {"maker": "2000000.00", "taker": "2000000.00"}
                        },
                        "share": {
                            "typeA": {"maker": "0.0000", "taker": "0.0000"},
                            "typeBAdj": {"maker": "0.0000", "taker": "0.0000"},
                            "total": {"maker": "0.0000", "taker": "0.0000"}
                        }
                    },
                    "mtd": {
                        "volume": {
                            "typeA": {"maker": "30000000.00", "taker": "30000000.00"},
                            "typeBTotal": {"maker": "30000000.00", "taker": "30000000.00"},
                            "tradfiX2": {"maker": "30000000.00", "taker": "30000000.00"},
                            "total": {"maker": "60000000.00", "taker": "60000000.00"}
                        },
                        "share": {
                            "typeA": {"maker": "0.0000", "taker": "0.0000"},
                            "typeBAdj": {"maker": "0.0000", "taker": "0.0000"},
                            "total": {"maker": "0.0000", "taker": "0.0000"}
                        },
                        "mtdStatus": "QUALIFIED",
                        "qualifyingShare": {"maker": "0.0000", "taker": "0.0000"}
                    }
                }
            ]
        }
    ]
}

Response Parameters

Volume and share structure

Both daily and mtd contain a volume Object and a share Object. Each Object holds category keys, and each category is itself an Object with maker (String) and taker (String) fields.

• volume values: USD notional as String with 2 decimal places (e.g. "1000000.00")
• share values: decimal string with 4 decimal places, no % suffix (e.g. "0.0000")

GET / Get GLP historical performance

Retrieve daily GLP performance history for a single program. Results are sorted newest-first (descending by date).

Rate Limit: 5 requests per 2 seconds

Rate limit rule: User ID

Permission: Read

HTTP Request

GET /api/v5/users/glp/historical-performance

Request Example

GET /api/v5/users/glp/historical-performance?program=SPOT
GET /api/v5/users/glp/historical-performance?program=SPOT&begin=1751299200000&end=1753804800000&limit=31

Request Parameters

Response Example

{
    "code": "0",
    "msg": "",
    "data": [
        {
            "date": "2026-07-13",
            "volume": {
                "typeA": {"maker": "1000000.00", "taker": "1000000.00"},
                "typeBTotal": {"maker": "1000000.00", "taker": "1000000.00"},
                "tradfiX2": {"maker": "1000000.00", "taker": "1000000.00"},
                "total": {"maker": "2000000.00", "taker": "2000000.00"}
            },
            "share": {
                "typeA": {"maker": "0.0012", "taker": "0.0010"},
                "typeBAdj": {"maker": "0.0008", "taker": "0.0007"},
                "total": {"maker": "0.0010", "taker": "0.0009"}
            }
        },
        {
            "date": "2026-07-12",
            "volume": {
                "typeA": {"maker": "950000.00", "taker": "980000.00"},
                "typeBTotal": {"maker": "850000.00", "taker": "900000.00"},
                "tradfiX2": {"maker": "800000.00", "taker": "820000.00"},
                "total": {"maker": "1800000.00", "taker": "1880000.00"}
            },
            "share": {
                "typeA": {"maker": "0.0011", "taker": "0.0009"},
                "typeBAdj": {"maker": "0.0007", "taker": "0.0006"},
                "total": {"maker": "0.0009", "taker": "0.0008"}
            }
        }
    ]
}

Response Parameters

Error Codes

Chase limit order for FUTURES/SWAP trigger orders

FUTURES and SWAP trigger orders now support a chase limit order as the post-trigger execution type. When advanceOrdType is set to chase, the trigger order places a chase order instead of a regular limit or market order once the trigger fires. The chase parameters are carried in a new advChaseParams array, and the read endpoints return the spawned chase order's algoId in a new subAlgoIdList field. Chase values can be amended while the trigger order is still pending (pre-trigger). Attached TP/SL (attachAlgoOrds) is not supported with chase in this iteration.

Place algo order

• Added a new advanceOrdType value chase and a new advChaseParams request parameter array; orderPx is now conditional (not applicable to a chase).
  • POST / Place algo order

Amend algo order

• Added advChaseParams amend fields to adjust the chase values while the trigger order is pending (pre-trigger). chaseType, maxChaseType, and the chase-price mode are fixed at placement and cannot be amended.
  • POST / Amend algo order

Read endpoints (order details, order lists, WS channel)

• Added advanceOrdType (with the new chase value), advChaseParams, and a new subAlgoIdList response parameter.
  • GET / Algo order details
  • GET / Algo order list
  • GET / Algo order history
  • WS / Algo orders channel

2026-06-23

Deprecation of checksum field in order book channels

To improve the efficiency and stability of the market data feed, the following order book channels have deprecated the checksum field in both snapshot and incremental updates. The checksum field is still present in snapshot and incremental updates, but its value is fixed to 0 and must no longer be used for integrity verification. Please use seqId/prevSeqId to verify the data continuity and accuracy.

• Deprecated the checksum field in both snapshot and incremental updates (the field remains in the push but its value is fixed to 0).
  • WS / Order book channel
    • books
    • books-l2-tbt
    • books50-l2-tbt

Note:
1. books5 and bbo-tbt channels do not carry a checksum field and are not affected by this change.
2. The WebSocket connection now fully enforces TLS (wss://), providing protection against eavesdropping and 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, providing integrity protection equivalent to or stronger than the original checksum mechanism.

2026-05-07

New Endpoints

• The following new endpoint is added. Only applicable to the demo trading environment:
  • Adjust demo account balance

Request Parameters

Response Parameters

Error Codes

2026-05-06

• OKX is introducing customisable slippage tolerance for spot and spot margin market-side orders via OpenAPI and WebSocket.
• A new post_only instrument state is added for SWAP contracts, restricting accepted order types to post-only limit orders.

Changes to Existing Endpoints

• New optional request parameter slippagePct for spot and spot margin market-side orders (where tgtCcy is the received currency: base_ccy for buy, quote_ccy for sell):
  • POST / Place order
  • POST / Place multiple orders
  • WS / Place order
  • WS / Place multiple orders

Request Parameters

Error Codes

• Response parameter state adds new enum value post_only. When a contract is in post_only, only post-only limit orders are accepted (along with amend and cancel of existing post-only orders); market, IOC, FOK and normal limit orders are rejected. Only applicable to SWAP:
  • Get instruments (private)
  • Get instruments (public)
  • Instruments channel

Response Parameters

2026-04-07

Trading Fee Tier Requirement Changes

• Channels that previously required VIP6/VIP5 or above are now accessible from VIP4 and above
  
• Error codes 60029 and 60030 have been deprecated and unified to error code 64003
  
• The following table shows the changes in VIP tier requirements for accessing various Open API features:

Deprecate instId Request Parameter in WS Order Operation Channels

To reduce latency in WS order operations, the instId request parameter from the following order operation channels has been deprecated.

• Deprecate instId request parameter in the following channels:
  • WS / Amend order
  • WS / Amend multiple orders
  • WS / Cancel order
  • WS / Cancel multiple orders

Request Parameters

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

KYC Level 2 Required for Placing Orders

OKX will require users to complete KYC Level 2 or above in order to place orders via WebSocket and REST API endpoints. Users who have not completed KYC Level 2 will receive error code 59113 when attempting to place orders. This requirement applies to live trading only — demo trading is not affected.

Affected Endpoints

Error Code

Notes:

• Users must complete KYC Level 2 verification before placing orders via WebSocket / REST API endpoints
  
• This requirement applies to live trading only — demo trading is not affected
  

2026-03-26

• Delisted instId request parameter from the following channels.
  • WS / Place order
  • WS / Place multiple orders

Request Parameters

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

2026-02-12

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

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