Real time and data channels

Totalis has four data channels. Pick one by the phase of the trade you are in and the delivery guarantee you need. All four authenticate with the same API key.

​

One trade, three phases

Pricing is SSE. Each quote request has its own stream at GET /v1/quote-requests/{id}/stream. Each cashout request has one at GET /v1/cashout-requests/{id}/stream. A stream exists only while its request is live and closes after a terminal event. Market makers watch the firehose variant, GET /v1/mm/quote-requests/stream. From commit onward it is events. When you commit, the quote request becomes an RFQ and the SSE stream ends. Acceptance, confirmation, on-chain execution, and settlement arrive on the WebSocket and as webhooks. State is always readable. The read endpoints return current truth whenever you ask. Use them to backfill after downtime and to reconcile what the push channels told you.

​

WebSocket or webhooks

Both deliver post-trade lifecycle events and overlap for most of the lifecycle. They differ in the delivery guarantee.

​

Typical integrations

​

Trading bot

1. Create a quote request with POST /v1/quote-requests.
2. Watch its SSE stream for best_quote events. Store book_seq and the quote id.
3. Commit when the price is right.
4. Follow the trade live on the WebSocket rfq:{rfq_id} channel, or durably via the parlay.status_changed webhook.
5. Record the outcome from the position.settled webhook, or read it from GET /v1/rfqs/{id}.

​

Read-only dashboard

1. Pull state with GET /v1/portfolio, GET /v1/rfqs, and GET /v1/pnl.
2. Subscribe to rfq:{rfq_id} for live position updates.
3. On reconnect, reconcile against the read endpoints.

​

Market maker

The maker loop, including cashout pricing, is on Market making.

​

Every event, side by side

The event catalog gives the exact event name each channel uses for every moment in a trade.