How to Find the BTC/USDT Market on OKX?

Market Symbol Mapping

1. OKX uses a standardized instrument ID format that differs from common trading pair notation. The symbol BTC-USDT is the official instrument ID used across all OKX API endpoints and UI elements.

2. Legacy notations like BTC/USDT or BTCUSDT are not recognized by OKX’s backend systems. Attempting to use them in API calls will result in an OkxParamsException with error code 51000.

3. The hyphenated format is strictly enforced for all spot, margin, and perpetual instruments. This includes ETH-USDT, SOL-USDT, and XRP-USDT — no slashes, no concatenation, no underscores.

4. When retrieving market data via python-okx, the MarketAPI.get_ticker() method requires the exact instrument ID. A malformed string triggers immediate rejection before any network request is dispatched.

5. Frontend users can locate BTC-USDT by typing “BTC” into the search bar on OKX’s web or mobile interface. The auto-suggestion list displays only valid instrument IDs, filtering out non-compliant variants.

API Endpoint Navigation

1. The RESTful endpoint for ticker data is /api/v5/market/ticker?instId=BTC-USDT. This path is case-sensitive and does not accept query parameters like base or quote separately.

2. K-line retrieval uses /api/v5/market/candles?instId=BTC-USDT&bar=1H. The bar parameter must be one of OKX’s predefined intervals: 1m, 3m, 5m, 15m, 30m, 1H, 2H, 4H, 6H, 12H, 1D, 1W, 1M.

3. Order placement endpoints require identical instId formatting. A trade request with instId: 'BTC/USDT' returns HTTP 400 with message “Instrument ID invalid”.

4. WebSocket subscription messages follow the same rule. The channel tickers expects JSON payload {'channel':'tickers','instId':'BTC-USDT'}. Any deviation causes silent disconnection without error notification.

5. CCXT abstracts this mapping internally but exposes it transparently through the exchange.markets object. Developers can inspect exchange.markets['BTC/USDT'].id to verify the resolved OKX-native symbol.

Frontend Interface Behavior

1. On OKX’s main trading page, BTC-USDT appears under the Spot tab by default. Switching to Margin or Futures changes the visible instrument set without altering the underlying symbol structure.

2. The order book depth chart renders only when the correct instrument ID is active. If the URL contains ?instrument_id=BTC%2FUSDT, the chart remains blank and no API requests fire.

3. Mobile app navigation relies on persistent instrument ID caching. Scrolling past BTC-USDT in the asset list does not reload the symbol — it preserves the last valid instId state until manually changed.

4. Historical trade logs in the Account > History section reference all transactions using BTC-USDT exclusively. Exported CSV files retain this format without conversion.

5. Price alerts configured through the UI store triggers using the native instrument ID. Editing an alert for BTC/USDT automatically converts it to BTC-USDT before persistence.

Data Consistency Across Modules

1. MarketData.py, Trade.py, and Account.py modules in python-okx share a unified symbol registry. There is no separate configuration per module — inconsistency would break internal validation checks.

2. Websocket streams for books5 and candle1m channels emit messages containing 'instId':'BTC-USDT' in every payload. Clients parsing raw JSON must match this exact string to route correctly.

3. Batch queries for multiple instruments require comma-separated BTC-USDT,ETH-USDT,SOL-USDT. Spaces, semicolons, or brackets invalidate the entire request.

4. Error responses from failed orders include 'instId': 'BTC-USDT' in the response body even when the original request used an incorrect format — the system normalizes before logging.

5. OKX’s public documentation examples consistently use BTC-USDT. Deviations in community tutorials often cause integration failures due to copy-paste propagation of outdated patterns.

Frequently Asked Questions

Q: Can I use BTCUSDT instead of BTC-USDT?A: No. BTCUSDT is rejected by all OKX APIs and frontend components. Only BTC-USDT is accepted.

Q: Does the hyphen affect WebSocket reconnection logic?A: Yes. Subscription payloads with incorrect instId cause the server to drop the connection without sending a close frame. Reconnection attempts must correct the symbol before resubscribing.

Q: Why does CCXT convert BTC/USDT internally but python-okx does not?A: CCXT is designed as a multi-exchange abstraction layer; python-okx is exchange-specific and assumes developers work directly with OKX’s native conventions.

Q: Is BTC-USDT case-sensitive in API calls?A: Yes. btc-usdt or Btc-Usdt will return error code 51000. Uppercase letters and hyphen placement are mandatory.