Event catalog

Each row below is one moment in a trade. Each column is one channel. Field names, identifiers, and their aliases are in the Glossary, along with the event naming rules for each channel.

quote:* WebSocket events (quote:accepted, quote:confirmed, quote:executed, quote:expired, quote:rejected, quote:withdrawn) go to the market maker whose quote they concern, on their private mm:quotes:{mm_id} channel. The bettor’s own authenticated connections also receive quote:confirmed and quote:executed for their trade. rfq:* and position:* events go to rfq:{rfq_id}, the channel a user or anyone tracking a specific trade subscribes to. vault:deposited and vault:withdrawn go to the account’s own connections and are not in the table.The two families are not interchangeable. Some rows have a WebSocket event for the maker and none for the user, or the reverse.

One trade, across every channel

Lifecycle moment	SSE, user stream	SSE, MM stream	WebSocket	Webhook	REST status
Quote request created	No dedicated created event. The stream opens after creation and the first frame is `best_quote`, often `null`.	`quote_request`	None. WebSocket starts at commit.	None. Webhooks are post-trade only.	Quote request `status: "active"` via `GET /v1/quote-requests/{id}`
Quote updated	`best_quote`	`quote_request:updated`, only when the request itself changes via `PATCH`. No MM stream event exists for an individual quote submission, yours or a competitor’s.	None	None	`version` and `book_seq` increment. `status` stays `"active"`.
Quote accepted, committed	`status` (`status: "committed"`), then the terminal `committed` event, then the stream closes.	`quote_request_expired` with `reason: "committed"`. `won: true` for the winning maker, `false` for everyone else.	`quote:accepted` and `mm_quote:accepted` to the maker. `rfq:status` with `status: "accepted"` on `rfq:{rfq_id}` for anyone watching the trade.	`parlay.status_changed` with `status: "accepted"` and `accepted_quote_id` set	RFQ `status: "accepted"`
Confirmed by maker	None. The stream closed at commit.	None	`quote:confirmed` to the maker. `rfq:status` with `status: "confirmed"` on `rfq:{rfq_id}`.	`parlay.status_changed` with `status: "confirmed"`	RFQ `status: "confirmed"`
Executed on-chain	None	None	`quote:executed` to the maker. `rfq:status` with `status: "executed"` and `position:created` with `position_pda` on `rfq:{rfq_id}`. A failed creation attempt that will be retried arrives as `position:failed`.	`parlay.status_changed` with `status: "executed"`	RFQ `status: "executed"`
Settled	None	None	`position:settled` with `outcome` and `tx_signature`	`position.settled`, the terminal outcome event. `parlay.status_changed` stops at `executed` and `cancelled` and never carries `"settled"`.	RFQ `status: "settled"`
Exited early	None. The separate cashout stream ends with a terminal `status` event reporting `"committed"`.	`cashout_request`, broadcast to every maker when the auction opens. No SSE event marks its completion.	`position:bought_back` on `rfq:{rfq_id}`, only when the winning bid closes the position. Nothing is delivered when a bid acquires it. See the acquisition gap.	`position.bought_back` with `amount`, `mm_pays_user`, `tx_signature` on a close. `position.transferred` goes to the seller only.	Depends on the outcome. A close sets `status: "bought_back"` and populates the `cashout` object. A transfer leaves the position active and repoints ownership, so the RFQ does not become `bought_back`.
Cancelled	`cancelled`, when the quote request is abandoned pre-commit via Cancel	`quote_request_expired` with `reason: "cancelled"`	`rfq:cancelled` and `rfq:status` with `status: "cancelled"` on `rfq:{rfq_id}`, plus `position:cancelled` when a funded position is cancelled. A pre-commit cancellation never reaches a position, so only the `rfq:*` events fire.	None pre-commit. Post-commit fires both `parlay.status_changed` (`status: "cancelled"`) and `position.cancelled`, with different event ids, so match the pair on `rfq_id`.	Quote request `status: "cancelled"` pre-commit, RFQ `status: "cancelled"` post-commit
Expired	`expired`, when the TTL lapsed with no commit	`quote_request_expired` with `reason: "expired"`	`rfq:expired` on `rfq:{rfq_id}` when the whole parlay expires. `quote:expired` to a maker means that maker’s accepted quote lapsed before confirmation.	None. No webhook event exists for expiry, before or after commit.	Quote request `status: "expired"` pre-commit, RFQ `status: "expired"` post-commit

The acquisition gap

An early cashout resolves one of two ways. Only one of them notifies you live.

A closing exit is well covered

position:bought_back carries rfq_id, position_pda, amount, mm_pays_user, tx_signature, and quote_id. It fans out to four places at once:

Destination	Needs a subscription
The `rfq:{rfq_id}` channel, the canonical one for `position:*` events	Yes. Subscribe to this one.
The `mm:quotes:{mm_id}` channel of the maker whose exposure closed	Yes
Any connection authenticated as the seller	No, it arrives on identity alone
Any connection authenticated as that maker	No

The last two arrive on identity alone. If you also hold the rfq:{rfq_id} subscription, you may see the same event twice. Dedupe on tx_signature. The position.bought_back webhook carries the same moment.

An acquiring bid notifies the buyer of nothing

One cashout outcome reaches the buyer on no channel: a bid that acquires a position instead of closing it.When the winning bid comes from a market maker that was not the position’s counterparty, the position transfers to them and stays open. There is no WebSocket event and no buyer-side webhook for that. position.transferred goes to the seller.If you bid on auctions for positions you do not already back, reconcile acquisitions from GET /v1/rfqs, where an acquired position appears on your account, rather than waiting for a push.

Polling the RFQ status does not help either. A transfer leaves it executed, so polling for bought_back never fires.

Delivery guarantees

Channel	Guarantee	On reconnect
SSE	Live only, for the life of the request	Resume with `last_event_id`
WebSocket	Live only, no redelivery	Reconcile against read endpoints
Webhooks	At-least-once, signed, retried	Replay by delivery id
REST	Current truth, on demand	n/a

Overview

Get started

Core concepts

Guides

Resources

One trade, across every channel

The acquisition gap

A closing exit is well covered

An acquiring bid notifies the buyer of nothing

Delivery guarantees

​One trade, across every channel

​The acquisition gap

​A closing exit is well covered

​An acquiring bid notifies the buyer of nothing

​Delivery guarantees

One trade, across every channel

The acquisition gap

A closing exit is well covered

An acquiring bid notifies the buyer of nothing

Delivery guarantees