OKX to adjust ELP taker eligibility

OKX will enhance the Enhanced Liquidity Program (ELP) by allowing API users to optionally take ELP liquidity via OpenAPI while introducing speed bumps for app, web, and OpenAPI to protect ELP orders, rolling out gradually effective from January 7, 2026.

API users can choose whether their orders interact with ELP liquidity. Opted-in orders will face a speed bump currently set at 20 milliseconds before entering OKX’s system, ensuring fair access.

Key changes for OpenAPI users

1. Optional ELP taker access: A new request parameter, elpTakerAccess (true/false), is introduced for OpenAPI place-order requests.

   1. true: The order may trade with ELP liquidity and will be subject to a speed bump.

   2. false (default): The order won’t trade with ELP liquidity and won’t experience delays.

2. IOC-only support: API users may take ELP liquidity only through IOC (immediate-or-cancel) orders. Other order types aren’t eligible to interact with ELP liquidity via OpenAPI.

3. Speed bump protection: When elpTakerAccess:true, a speed bump currently set at 20 milliseconds will be applied to the order before it enters OKX’s system. Speed bumps aren’t applied to:

   1. Users who opted in for elpTakerAccess as false or don't pass in this parameter.

   2. Orders on non-ELP symbols.

   3. Order cancellation requests.

4. Scope and availability: elpTakerAccess is supported across all symbols with ELP enabled.

For app and web users, a speed bump currently set at 20 milliseconds will be applied to the order before it enters OKX’s system. Speed bumps are applied to create, modify, cancel order requests of all order types for symbols with ELP enabled.

OKX reserves the right, in its sole discretion, to modify or suspend the speed bump at any time without prior notice.

By introducing controlled API access and speed bumps, OKX aims to expand participation in ELP liquidity while maintaining its original purpose to enhance execution quality for users, protect ELP orders, and improve overall market quality.

For more details, refer to the API changelog.