Delete RFQ
Queues cancellation of an RFQ.
Cancellation is asynchronous. Subscribe to the private WebSocket channel
rfq before sending the request. A 202 Accepted response contains a Paradex
request_id and confirms only that the command was queued. The later
WebSocket RESULT event with the same request_id reports whether the venue
accepted the cancellation. RFQ lifecycle events report the eventual closed
state.
The rfq_id is the venue-issued identifier returned by a successful create
result or by the RFQ list endpoint.
An account holds only one two-way RFQ open at a time, and a bounded number of
RFQs in total, so this is also the request that frees it to create the next
one. The RESULT event reporting the cancellation accepted is the point at
which it is normally free; a create sent immediately after may still be
rejected for the RFQ being open, and can be retried.
Authentication
Path parameters
Paradigm-issued RFQ id
Response
request_id identifies this request. It is echoed on the RESULT event delivered later on the WebSocket rfq channel, so a client with several requests in flight can match each outcome to the request that caused it. On Create it is the only identifier available until the venue issues the rfq_id.