Skip to main content

WebSocket API Basics

Status: Not yet implemented (空缺).

Status: Not yet implemented (空缺).

Industry-standard USD-margined perpetual futures exchanges publish both a WebSocket API (call-and-response over WS) and WebSocket streams (server-pushed market data). Rocky currently exposes neither — all interaction goes through REST today.

Planned shape​

When implemented, Rocky will follow the standard structure:

URLPurpose
wss://demo.rocky.exchange/ws-fapi/v1WebSocket API (request/response, signed)
wss://demo.rocky.exchange/ws/<stream>Single market stream
wss://demo.rocky.exchange/stream?streams=...Combined market streams

Subscribe / unsubscribe by sending JSON messages following the standard WebSocket convention.

Current alternatives​

  • Polling — call REST endpoints on a timer. Acceptable for low-frequency clients.
  • Backend NATS subjects — internal services subscribe to oracle.*, trade.matched, etc. directly. Not exposed externally.

Track this section's status in the Changelog.