Dear OKX Users,
To accommodate the integration of the USDC index, the following API adjustments will take effect during the maintenance window from 8:30 AM to 8:40 AM UTC on April 10, 2023. These updates ensure seamless trading and data retrieval for both USD and USDC-based instruments.
👉 Explore OKX's latest API enhancements
Key API Adjustments
REST API Updates
Trade, Account, and Public Data Endpoints
| Endpoint | Request Parameter (uly) | Response Parameter (uly) | Adjustment |
|---|---|---|---|
GET /trade/orders-pending | ✓ | ✗ | Filters orders by specified index (USD/USDC) |
GET /trade/orders-history | ✓ | ✗ | 7-day order history now index-specific |
GET /trade/orders-history-archive | ✓ | ✗ | 3-month archive supports index isolation |
GET /trade/fills | ✓ | ✗ | Transaction details segregated by index |
GET /public/mark-price | ✓ | ✗ | Returns mark price for requested index |
Key Change: For USDC derivatives, response parameters will reflect the corresponding USDC index (e.g., BTC-USDC).
Market Data Endpoints
Index Services
| Endpoint | New Support |
|---|---|
GET /market/index-tickers | quoteCcy=USDC and USDC indices |
GET /market/index-candles | USDC index candlestick data |
GET /market/index-components | USDC index constituent data |
Example: Requesting BTC-USDC returns data exclusively for the USDC index.
Grid Trading Updates
| Endpoint | Response Parameter (uly) |
|---|---|
GET /grid/orders-algo-pending | ✓ |
GET /grid/orders-algo-history | ✓ |
GET /grid/orders-algo-details | ✓ |
Note: Grid bots now return the corresponding USDC index in responses.
WebSocket Channel Modifications
| Channel | Subscription Parameter (instId) | Push Notification (uly) |
|---|---|---|
index-candle30m | ✓ | ✗ |
index-tickers | ✓ | ✗ |
instruments | ✗ | ✓ |
opt-summary | ✗ | ✓ |
👉 Master OKX WebSocket integrations
Core Keywords
- USDC Index Integration
- API Adjustments
- OKX Trading
- REST API Updates
- WebSocket Channels
- Grid Trading Bots
FAQ Section
Q: How does the USDC index affect existing USD positions?
A: All existing positions remain unchanged. New API calls must specify the desired index (USD/USDC).
Q: Can I retrieve mixed USD/USDC data in a single request?
A: No. Each request must target either USD or USDC indices exclusively.
Q: When will historical data reflect these changes?
A: Data segmentation applies retroactively to all records after the update.
Q: Are WebSocket subscriptions backward-compatible?
A: Yes, but new subscriptions should specify the index parameter.
Implementation Notes
- Fee Structure: Separate maker/taker rates for USD and USDC instruments
- Portfolio Margining: Isolated calculations per index
- Liquidation Data: Index-specific reporting
For developers: Update API clients to handle index-specific responses and implement proper parameter validation.
OKX remains committed to providing transparent, efficient trading infrastructure through these technical enhancements.