Execute RFQ
Queues a taker limit Fill-or-Kill order against an RFQ.
Execution 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 success or failure;
on success, `result.order_id` is the venue-issued order identifier.
`quantity` must be a positive decimal string. `side` is `BUY` or `SELL`.
`price` is the signed net strategy price, so zero and negative values are valid
for multi-leg credit strategies.
Validation or risk-check failures that occur after queueing are reported by
the WebSocket `RESULT` event.
Authentication
Authorizationstring
API Key authentication via header
Path parameters
rfq_id
Paradigm-issued RFQ id
Request
Order details
price
Signed decimal strategy price; zero and negative values are valid
quantity
Positive decimal strategy quantity
side
Taker order side
label
User-defined order label
Response
Accepted
accepted_at
Unix milliseconds when the request was queued
request_id
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.
Errors
400
Bad Request Error
401
Unauthorized Error
403
Forbidden Error