Submit RFQ response

Submit a response to a Request for Quote (RFQ) with your pricing.

Makers use this endpoint to provide pricing for RFQ requests they've received. The response structure uses a nested array format where each order is represented as a pair of elements.

Response Structure: The fills array structure mirrors the RFQ request structure with two categories:

• Basket of options response pairs only: Up to 6 option response pairs
• Single perpetual response pair only: Exactly 1 perpetual response pair

Each response pair consists of:

1. First element: A copy of the original RFQ request parameters (instrument_name, contracts/amount, direction)
2. Second element: The complete signed order with pricing and all execution details

Critical Requirements (MUST follow to avoid errors):

• Order type MUST be good_til_cancelled (GTC) - Using good_til_date (GTD) will cause validation errors
• post_only MUST be true - Setting to false will cause validation errors for RFQ responses

Important Validation Rules:

• All orders from the original RFQ request must be included in the response
• For each pair, the parameters in the first element must match those in the second element:
  • instrument_name must be identical
  • direction must be OPPOSITE (if request is "buy", response must be "sell" and vice versa)
  • contracts (for options) or amount (for perpetuals) must be identical
• The taker address must match across all locations (root level and in signed orders)
• The maker address must be consistent across all signed orders
• All signatures must be valid EIP-712 signatures and not expired

Key Fields in Signed Orders (second element of each pair):

• price: Your quoted price for this order
• type: MUST be "good_til_cancelled" (GTD not supported for RFQ)
• post_only: MUST be true (false will cause errors)
• signature: Valid EIP-712 signature for the order
• signature_deadline: Unix timestamp when the signature expires
• taker and maker: Must match the root-level addresses

Note: RFQ responses can be cancelled using the DELETE /orders endpoint with the order_id from this response.