The taker's own RFQs with their quotes
Full view: open RFQs first, and closed ones (settled / cancelled / expired) for the book's retention window, each with every quote the RFQ received — terminal quote statuses included. Unanchored quotes of external makers are filtered out (not acceptable yet).
Full view: open RFQs first, and closed ones (settled / cancelled / expired) for the book's retention window, each with every quote the RFQ received — terminal quote statuses included. Unanchored quotes of external makers are filtered out (not acceptable yet).
Authorization
ApiKeyAuth In: header
Response Body
application/json
application/json
curl -X GET "https://example.com/rfq/mine"[ { "rfqId": "string", "taker": "taker", "direction": "SELL", "qty": "5.0", "base": "cbtc", "quote": "usdcx", "deadline": "2019-08-24T14:15:22Z", "invitedMakers": [ "string" ], "feeBps": 25, "open": true, "quotes": [ { "quoteId": "string", "rfqId": "string", "maker": "acme-mm-4f2a91", "price": "97300.0", "validUntil": "2019-08-24T14:15:22Z", "status": "pending", "settling": true, "proposalCid": "string" } ] }]{ "error": "string", "code": "INSUFFICIENT_FUNDS"}Active incoming RFQs of the key's party (REST alternative to the stream) GET
The same RFQs as the /maker/stream snapshot, plus `myQuote` — this party's quote (or null). Polling is legitimate for simple bots, but the canonical path is the WebSocket: it also carries quote statuses and settlement progress.
The taker's RFQs that closed without a settled trade GET
Expired and cancelled RFQs plus failed settlements — the outcomes that are not trades. The settled blotter is `GET /trades`; rows here never overlap with it. Caller-scoped: no `taker` field in the rows.