Overview
RFQ functionality involves two types of participants connecting via different FIX sessions: RFQ Creators - Users who want to trade via RFQ (connect via RT mode):- Create RFQ via QuoteRequest (35=R)
- Receive quotes from market makers via Quote (35=S)
- Accept a quote via AcceptQuote (35=UA)
- Receive trade execution via ExecutionReport (35=8)
- Receive QuoteRequest from exchange
- Respond with Quote (35=S)
- Receive acceptance notification
- Confirm execution via QuoteConfirm (35=U7)
RFQ Creators use the KalshiRT endpoint (same as order entry), which provides message persistence and retransmission support. Market Makers use the KalshiRFQ endpoint to receive RFQ broadcasts and submit quotes.
Message Flow
Full RFQ Flow (Creator via FIX)
QuoteRequest (35=R)
This message is used bidirectionally:- Creator → Exchange: Create a new RFQ
- Exchange → Market Makers: Notify of new RFQ
Creator → Exchange (Create RFQ)
Message body
Inside the
146=NoRelatedSym group
The delimiter is the first tag of a group entry: send
146, then 55 for a symbol RFQ
or 38/152 for an MVE RFQ (which omits 55). Note that 21015, 21016, and 21033
are dropped without a reject if they land outside the group — a misplaced 21016 surfaces
later as RFQ already exists on the next request rather than as an error on this one, and
a misplaced 21033 silently produces default fee-inclusive sizing.The published FIX dictionary
lists 55 first, since a dictionary can only declare one delimiter per group. MVE
requests legitimately omit 55, so a strict dictionary-driven validator may flag them —
relax the delimiter for the MVE case rather than adding an empty 55.MVE/Parlay Support: Instead of specifying a Symbol, you can submit MVE legs directly. The server will automatically resolve or create the parlay market and return the resolved market ticker in the QuoteRequestAck.
CashOrderQty sizing: By default the cash amount caps principal plus Kalshi
fees — quote sizes (BidSize/OfferSize) are the maximum contracts whose total
cost including your taker fee fits inside the cash amount, so your debit can
never exceed it. With
21033=Y the cash amount is principal only: sizes are
cash / price and your taker fee is charged on top of the cash amount.
OrderQty-sized RFQs are never reduced for fees under either mode.Exchange → Market Maker (RFQ Notification)
The exchange builds this message with the same structure market makers must parse:55, 38, 152, 60 and the nested 453=NoPartyIDs group are members of the
146=NoRelatedSym group, and the MVE tags sit in the message body.
Message body
Inside the
146=NoRelatedSym group
The obscured
PartyID is the SHA-256 hash of empty input (SHA256("")).
It is the same placeholder for every obscured requester across REST, WebSocket,
and FIX. The requester still sees their normal public communications
ID in their own notifications. The NoPartyIDs group remains present.
See Creator identity and privacy
for the visibility rules before and after execution.
A child RFQ of an RFQ batch arrives as an ordinary QuoteRequest, with no tag
naming its batch, and can be quoted like any RFQ. See
RFQ batch children for how such a
quote differs.
QuoteRequestAck (35=b)
Exchange response to an inbound QuoteRequest from an RFQ creator.The server-assigned RFQ ID is returned in tag 21023. Store it if you want to reconcile later Quote or QuoteStatusReport messages to the created RFQ. RFQCancel accepts either your original client-assigned QuoteReqId (tag 131) or the server-assigned RfqId (tag 21023).
When creating an RFQ with MVE legs instead of a Symbol, the resolved market ticker is returned in tag 55. This is the market that was created or looked up based on your leg selection.
Quote (35=S)
This message is used bidirectionally:- Market Maker → Exchange: Submit a quote for an RFQ
- Exchange → Creator: Notify creator of a new quote
Market Maker → Exchange (Submit Quote)
Exchange → Creator (Quote Notification)
Best Quote Only
A session that logs on withBestQuoteOnly<21036>=Y receives only the best quote of each RFQ it creates while the flag is set. The RFQ keeps this mode until it closes. The best quote arrives as the same Quote (35=S) described above, with no new fields.
- Ranking: quotes are ranked on the RFQ’s natural side:
OfferPx<133>(No) for an RFQ sized byCashOrderQty<152>,BidPx<132>(Yes) for one sized byOrderQty<38>. The highest price is best, then the earliest quote at that price, which is the quote an AcceptQuote on that side fills. A quote with no price on the natural side is never best, so an RFQ whose quotes all lack it sends no Quote. - When a Quote is sent: each time a different quote becomes best: a better quote arrives, the best is cancelled or stops quoting the natural side (the next best is sent, even at a worse price), or the best maker replaces its quote (a new
QuoteId<117>, even at the same price). Changes below the best send nothing. - Superseding: the latest Quote for a
QuoteReqId<131>replaces all earlier ones. Order them by MsgSeqNum:TransactTime<60>is the quote’s own creation time and can go backwards. - Nothing left: once no open quote has a price on the natural side, the last best is sent again with
BidSize<134>=0andOfferSize<135>=0: there is nothing to accept. - Accept and close: nothing extra is sent; AcceptQuoteStatus (35=UC) and the usual close messages end the RFQ. A Quote can arrive just after the close; ignore it.
- The other side: the Quote’s other price is that quote’s own. An accept on the other side follows that side’s ranking, so it can fill another quote at the same price.
- Missed updates: Quotes sent while the session is disconnected are kept for ResendRequest, like other KalshiRT messages. The current best is not re-sent at Logon: if an update is lost another way, for example during a Kalshi restart or when sequence numbers are reset, the next one arrives with the RFQ’s next best change.
QuoteStatusReport (35=AI)
A QuoteStatusReport is sent by the exchange:- In response to a Quote. Status will be PENDING if processed, or REJECTED if rejected
- When an accept fills your quote. Status will be ACCEPTED. Your quote can fill when the requester named another maker’s quote: one at the same price, if yours was there first, or, with PreferBetterQuote, one at a worse price than yours
- In response to a QuoteCancel. Status will be CANCELLED
Quote Status Values (297)
- ACCEPTED<0>: Requester accepted the quote
- REJECTED<5>: Exchange rejected the quote
- PENDING<10>: Quote processed, awaiting action
- CANCELLED<17>: Quote cancelled
QuoteCancel (35=Z)
Market maker cancels an active quote.Exchange responds with QuoteStatusReport (Status=CANCELLED).
QuoteCancelStatus (35=U9)
Response to QuoteCancel from exchange.QuoteConfirm (35=U7)
Market maker confirms willingness to execute after quote acceptance.QuoteConfirmStatus (35=U8)
Exchange response to quote confirmation.AcceptQuote (35=UA)
RFQ creator accepts a quote from a market maker. The exchange fills the earliest open quote at the named quote’s price on the accepted side, which can be another maker’s quote. AcceptedQuoteId (21024) on the AcceptQuoteStatus identifies it. See RFQs for how that quote is chosen.AcceptQuoteStatus (35=UC)
Exchange response to AcceptQuote.RFQCancel (35=UE)
RFQ creator cancels/deletes an active RFQ.RFQCancelStatus (35=UB)
Exchange response to RFQCancel, or unsolicited with EXPIRED(2) when the exchange closes the RFQ itself.QuoteRequestReject (35=AG)
Exchange notifies that an RFQ creation request was rejected or that a quote request was cancelled.Market makers do not send QuoteRequestReject when ignoring a request.