Private WebSocket
The Private WebSocket endpoint provides real-time updates for user-specific data including orders, positions, account balances, and RFQs. Enabled RFQ subscribers also receive anonymous trade prints shared across participants.Endpoint
Subscription Types
Order Subscriptions
Subscribe to Orders
marketSlugs empty to subscribe to all markets.
Order Snapshot Response
Initial snapshot of open orders:Order Update Response
Real-time order execution updates:lastShares is a string and may also contain a decimal quantity.
Position Subscriptions
Subscribe to Positions
Position Update Response
netPositionDecimal, qtyBoughtDecimal, qtySoldDecimal, bodPositionDecimal, and qtyAvailableDecimal, matching GET /v1/portfolio/positions. Use those fields when present; the older integer fields are rounded and remain for backward compatibility.
Account Balance Subscriptions
Subscribe to Balances
Balance Snapshot Response
Balance Update Response
description field is reserved and currently always empty.
RFQ Subscriptions
Subscribe to RFQs
Subscribe withoutmarketSlugs. RFQ and quote visibility follows the participant associated with the authenticated API key. Anonymous rfqTrade prints are shared across participants.
RFQ Event Response
No separate success acknowledgment is sent. Events use therfqEvent envelope, and each message contains exactly one event variant:
rfqCreated and rfqClosed includes optional tickSize, the price increment in dollars. See RFQ price ticks for pricing rules.
Confirm or decline using
quoteAccepted.quote.id. See quote replacement.
RFQ Trade Response
rfqTrade.trade uses the same fields as RFQ trade history:
SUBSCRIPTION_TYPE_ORDER for your own order activity.
Recovery
The stream is live and best effort, with no replay or durable cursor. Unsubscribing, disconnecting, or an upstream failure ends it. Recover missed trades through RFQ trade history, and reconcile RFQ and quote state withGET /v1/rfqs and GET /v1/rfqs/quotes.