latestOpenAPI 3.0.0raw.githubusercontent.com2026-08-20125174417.3 KB

e8fca3e578c7

Rfqs

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.

post/rfqs/{rfq_id}/execute

Path parameters

rfq_idstring required

Paradigm-issued RFQ id

Request body

labelstring

User-defined order label

pricestring required

Signed decimal strategy price; zero and negative values are valid

quantitystring required

Positive decimal strategy quantity

side'BUY' | 'SELL' required

Taker order side

Example request

{
  "label": "my-order",
  "price": "0.1",
  "quantity": "0.1",
  "side": "BUY"
}

Response

Accepted

accepted_atinteger

Unix milliseconds when the request was queued

request_idstring

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.

Example response

{
  "accepted_at": 1640995200000,
  "request_id": "1739923200000000000"
}