Cancel an open RFQ (taker)
Authorization
ApiKeyAuth In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/rfq/string"{ "error": "string", "code": "INSUFFICIENT_FUNDS"}{ "error": "string", "code": "INSUFFICIENT_FUNDS"}{ "error": "string", "code": "INSUFFICIENT_FUNDS"}{ "error": "string", "code": "INSUFFICIENT_FUNDS"}Create an RFQ (taker) POST
Requests quotes for a `base`/`quote` swap from `invitedMakers` (party hints; every invited maker must currently be reachable — a listed but offline maker is a 400). `direction` is from the taker's side: SELL — you sell the base for the quote instrument. `base` / `quote` are catalog symbols (any case). The RFQ expires after `ttlSeconds` unless a trade settles first. You cannot invite yourself.
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.