The OKX trading platform continues to refine its API infrastructure to deliver a more seamless and transparent experience for developers and algorithmic traders. A recent update to the 'Get Fee Rates' interface introduces structural changes aimed at simplifying fee categorization while enhancing support for different margin types in derivatives trading. These improvements, effective May 7, 2022, reflect OKX's ongoing commitment to streamlining its trading systems and improving data accuracy across spot, margin, futures, and perpetual contracts.
This article walks you through the key changes, explains their implications for API users, and highlights how these updates align with evolving market demands for clarity in fee structures.
Understanding the Core Changes to the 'Get Fee Rates' Endpoint
The updated endpoint — GET /api/v5/account/trade-fee — retains its original path, ensuring backward compatibility for existing integrations. However, two major modifications have been introduced to better reflect the platform’s revised fee model following the 2022 fee rate system upgrade.
Removal of the 'category' Field
One of the most notable changes is the removal of the 'category' field from request parameters. Previously used to specify fee rate categories, this field is now obsolete because all currency pairs fall under a single, unified fee schedule. While the field will still be accepted in requests for compatibility reasons, it no longer influences the response.
This change simplifies API calls by eliminating redundant filtering options, reducing complexity for developers integrating fee data into trading bots or analytics tools.
Despite its deprecation in requests, the category parameter remains present in the response payload, where it continues to indicate the applicable fee schedule. This ensures continuity for applications that rely on historical parsing logic.
Introduction of New USDT-Margined Fee Parameters
To accommodate distinct fee structures between crypto-margined and USDT-margined futures and perpetual contracts, OKX has introduced two new return parameters:
takerU: Taker fee rate for USDT-margined futures and perpetualsmakerU: Maker fee rate for USDT-margined futures and perpetuals
Meanwhile, the original taker and maker fields now exclusively represent fee rates for crypto-margined derivative products.
👉 Discover how updated API responses can enhance your trading strategy precision.
This differentiation allows traders to accurately assess costs based on contract type and margin asset — a critical factor in optimizing high-frequency or arbitrage strategies where even minor fee differences impact profitability.
Updated Request and Response Parameters
For clarity and ease of integration, here are the finalized parameter specifications post-update.
Request Parameters (After Adjustment)
- instType (String, Required): Specifies the instrument type — valid values include
SPOT,MARGIN,SWAP,FUTURES,OPTION - instId (String, Optional): Instrument ID (e.g.,
BTC-USDT), applicable only toSPOTandMARGINtrading - uly (String, Optional): Underlying asset (e.g.,
BTC-USD), used forFUTURES,SWAP, andOPTIONinstruments - category (String, Optional): Deprecated; included for backward compatibility but will be ignored
Return Parameters (Enhanced Structure)
- category: Current fee schedule identifier
- taker: Taker fee rate for crypto-margined futures and perpetuals
- maker: Maker fee rate for crypto-margined futures and perpetuals
- takerU: Taker fee rate specific to USDT-margined contracts
- makerU: Maker fee rate specific to USDT-margined contracts
- delivery: Delivery fee rate (applicable to futures)
- exercise: Option exercise fee rate
- level: User’s current fee tier level
- instType: Type of financial instrument
- ts: Timestamp of data generation in Unix milliseconds
These enhancements ensure that developers receive granular, context-aware fee data tailored to each product type.
Why These Changes Matter for Traders and Developers
Accurate fee data is foundational to profitable algorithmic trading. With increasing diversity in contract types — especially between crypto-margined and stablecoin-margined derivatives — having clearly differentiated fee indicators prevents miscalculations that could erode margins.
For example:
- A trading bot executing swaps on BTC-USDT-SWAP must now reference
takerUinstead oftakerto get correct taker fees. - A cross-margin strategy involving ETH-BTC should continue using
takerandmaker, as those apply to crypto-margined instruments.
👉 Optimize your trading algorithms with real-time, accurate fee data from OKX.
Such distinctions empower developers to build smarter risk models, improve execution logic, and deliver more reliable performance analytics.
Frequently Asked Questions (FAQ)
Q: Does removing the 'category' parameter break existing API integrations?
A: No. Although the 'category' field is deprecated in requests, the API continues to accept it without error. Responses remain consistent whether or not the parameter is included, ensuring smooth transition for legacy systems.
Q: How do I know which fee field to use — taker/maker or takerU/makerU?
A: Use taker and maker for crypto-margined contracts (e.g., BTC-USD-SWAP). Use takerU and makerU for USDT-margined contracts (e.g., BTC-USDT-SWAP). Always check the instType and underlying (uly) to determine contract type.
Q: Are spot and margin trading fees affected by this update?
A: Spot and margin trading are not impacted in terms of functionality. Their fee rates are still returned via taker and maker, as they do not differentiate between margin types like derivatives do.
Q: When did these changes take effect?
A: The update was implemented on May 7, 2022. Users were advised to review their implementations ahead of this date.
Q: Where can I find documentation for other OKX API endpoints?
A: Comprehensive API documentation is available directly through the OKX developer portal, covering authentication, rate limits, error codes, and full endpoint references.
Q: Do these changes affect user fee tiers or rates?
A: No. This update only modifies how fee data is structured and returned via the API. Actual fee rates and tier calculations remain unchanged.
Final Recommendations for API Users
To ensure uninterrupted operation and accurate data processing:
- Update parsing logic in your applications to handle both
takerU/makerUand traditionaltaker/makerfields based on instrument type. - Remove reliance on the 'category' request parameter, as it may be fully phased out in future versions.
- Validate responses against known instruments to confirm correct interpretation of margin-specific fees.
- Monitor official announcements, as further refinements may follow based on user feedback and product evolution.
👉 Stay ahead with next-generation trading tools powered by transparent, developer-friendly APIs.
By adopting these best practices, traders and developers can maintain robust, future-proof integrations that fully leverage OKX’s advanced trading ecosystem.
Note: All information in this article is accurate as of the implementation date in 2022. For ongoing updates, always refer to the latest official API documentation.