The taker's own RFQs with their quotes
Your RFQs: the open ones and those closed within the last 10 minutes (settled / cancelled / expired), each with every quote it received — terminal statuses included. A quote whose allocations have not landed yet is left out (it cannot be accepted).
Your RFQs: the open ones and those closed within the last 10 minutes (settled / cancelled / expired), each with every quote it received — terminal statuses included. A quote whose allocations have not landed yet is left out (it cannot be accepted).
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, "anchorCids": [ "string" ] } ] }]{ "error": "string", "code": "INSUFFICIENT_FUNDS"}Incoming RFQs of the key's party (REST alternative to the stream) GET
The RFQs the party is invited to: every open one, plus those closed in the last 10 minutes (`open: false`) so their outcome stays readable — `myQuote` is then your quote with its final status. To quote, take the entries with `open: true` whose `myQuote` is `null` or no longer `pending` (it expired or was revoked); quoting again replaces a live quote of yours. Polling is legitimate for simple bots; the WebSocket is faster and also carries 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.