Skip to main content
The event WebSocket carries pending settlements, confirmation updates, Chainlink prices, combo lifecycle events, wallet activity, and other product events. send() resolves only after the server acknowledges the subscription.

Subscribe

Presets and filters

Current presets are settlements, trades, prices, dome, fills, combos, redemptions, redemption, deposits, blocks, wallets, markets, large_trades, global, oracle, and chainlink. Builder filters include wallets, tokens, market IDs, slugs, condition IDs, side, direction, status, size bounds, event types, initial snapshot count, reconnect since, Chainlink feeds and TWAP windows, combo and leg IDs, event IDs, module IDs, and action.

Reconnect behavior

When the socket reconnects, the SDK resubscribes with a cursor based on the latest accepted timestamp, requests a small overlap, and deduplicates the overlap. This is best-effort replay within the service’s retained history; it is not an unlimited delivery guarantee. Treat notice.guaranteed as false and backfill through REST if your application requires durable completeness. The async-iterator queue is bounded. If the consumer cannot keep up, onOverflow reports dropped events rather than hiding the loss. Short-form rotation is different: it deliberately closes its dedicated socket at each market boundary and reconnects to subscribe to the next market and Chainlink selection. See TypeScript short-form.

Cleanup

See the shared settlement guide for acknowledgement fields, replay semantics, and event handling patterns.