Documentation

Documentation

7. v0.6.0 — OKX data provider

Created
Jun 17, 2026
Updated
Jun 17, 2026

Released 2026-06-17. This release adds OKX as a fully integrated crypto data provider with complete feature parity to Binance — spot pairs and linear perpetual swaps (USDⓈ-M equivalent), realtime streaming, symbol search, watchlist support, and provider addressing — all using OKX's public v5 endpoints with no API key required.

Added

  • OKX crypto spot provider. Historical bars, realtime bars, ticker overview (/api/v5/market/ticker), and the tradable SPOT instrument universe (/api/v5/public/instruments?instType=SPOT). Candle history spans OKX's /market/candles (recent window) and /market/history-candles (older data), paginated via the after cursor so deep history loads correctly.
  • OKX linear perpetual swaps. The same four capabilities for USDⓈ-margined perpetual swaps (instType=SWAP, ctType=linear), served from the same OKX v5 host. Inverse (coin-margined) contracts are excluded, mirroring Binance's USDⓈ-M scope.
  • OK: symbol prefix and ?provider=okx query parameter. Force OKX for any symbol: OK:BTC-USDT (spot), OK:FU:BTC-USDT-SWAP (perpetual swap), or /chart/BTC-USDT?provider=okx. The FU asset-class token pins the swap market the same way BI:FU:BTCUSDT pins Binance futures.
  • OKX in the symbol search dialog. OKX SPOT and SWAP instrument universes are loaded into the catalog and appear alongside Binance in symbol search. The search dialog now normalizes both dash-separated (BTC-USDT) and concatenated (BTCUSDT) forms so that typing either convention surfaces results from both providers.
  • OKX in the watchlist. Watchlist rows backed by OKX display an OK provider badge and fetch live quotes from OKX's public ticker endpoint.
  • OKX in Settings → Data provider. OKX appears in the Default provider dropdown. Its settings panel confirms no API key is required and shows the websocket streaming mode.
  • WebSocket keepalive. OKX's public websocket closes idle connections after ~30 seconds. The connector sends a ping frame every 25 seconds and expects pong, keeping the stream alive without reconnecting.

Changed

  • Symbol search matching now strips separators (dashes and slashes) before comparing, so a query in one provider's convention (BTCUSDT) matches tickers in the other's (BTC-USDT) and vice-versa. Exact literal matches still rank first.
  • Crypto symbol resolution order is now Binance → OKX → Massive → Alpaca. A bare BTCUSDT continues to resolve to Binance; BTC-USDT continues to resolve to OKX. Use the OK: or BI: prefix to force either provider.
  • Watchlist quote routing generalizes: any crypto provider (Binance or OKX) fetches quotes only from itself, never from equity fallbacks.
  • Workspace market/exchange mapping now returns exchange: "OKX" and market: "crypto-spot" / "crypto-futures" for OKX instruments, consistent with the existing Binance mapping.

Technical notes

  • OKX symbols use dash-separated instrument IDs (BTC-USDT, BTC-USDT-SWAP). Input in either form — BTC-USDT, BTCUSDT, or BTC/USDT — is normalized to the canonical dashed form before any API call.
  • OKX has no first-party browser JavaScript SDK, so both the browser and backend connectors use raw fetch + native WebSocket / ws, matching the pattern the Binance browser connector has always used. No new runtime dependencies were added.
  • The 10M timeframe is not natively available from OKX; the connector aggregates two consecutive 5m bars to produce it, the same technique used for Binance.
  • Daily and weekly bars use OKX's UTC-aligned variants (1Dutc, 1Wutc) so bar boundaries match the rest of the app.

Next steps

Back to the release list.

Next: Release Notes