GET /providers, market data, createAction / executeAction), WebSocket connections are made directly to the provider for lowest latency. The SDK discovers the WebSocket URL from the GET /providers response and handles connection management, reconnection, and data normalization automatically.
All incoming data is normalized to the same types the SDK’s account and market reads return (OrderbookResponse, Order, Position, etc.), so your application logic works identically whether the data came from a read or a WebSocket event. Order is RegularOrder | TriggerOrder | TwapOrder, discriminated on type.
See SDK / Streaming for usage details, the channel support table per provider, and connection lifecycle.