Sign in

v3

latestOpenAPI 3.0.02026-07-311784111.3 MB
Block RFQ
Private

Taker method

Creates a new Block RFQ. Use private/get_block_rfqs to retrieve Block RFQ information.

Block RFQ pre-allocation: The taker can split the total amount between different (sub)accounts using the trade_allocations parameter. The taker can also allocate to himself. Each allocation must specify either user_id (for direct allocation) or client_info object (for broker allocation), and amount.

📖 Related Article: Deribit Block RFQ API walkthrough

Scope: block_rfq:read_write

Try in API console

get/private/create_block_rfq

Query parameters

instrument_namestring

Unique instrument identifier

amountnumber

It represents the requested order size. For perpetual and inverse futures the amount is in USD units. For options and linear futures it is the underlying base currency coin.

direction'buy' | 'sell'

Direction: buy, or sell

List of legs used to create Block RFQ

[
  {
    "instrument_name": "BTC-PERPETUAL"
  }
]
user_idinteger

User ID (subaccount or main account) to allocate part of the RFQ amount.

amountnumber

Amount allocated to this user or client.

List of allocations for Block RFQ pre-allocation. Allows to split amount between different (sub)accounts or broker clients. Each allocation must specify either user_id (for direct allocation) or client_info object (for broker allocation), and amount.

hedgestring

JSON string containing: instrument_name, direction, price, amount

Hedge leg of the Block RFQ. There is only one hedge leg allowed per Block RFQ

labelstring

User defined label for the Block RFQ (maximum 64 characters)

makersstring[]

List of targeted Block RFQ makers. Only those makers will be notified about created Block RFQ. If the list is empty, all available makers will be targeted.

disclosedboolean

Determines whether the RFQ is non-anonymous, revealing both taker and maker aliases. It can be set to false (anonymous mode) only when at least 5 makers are targeted. Default value is true.

Response

Success response

jsonrpc'2.0' required

The JSON-RPC version (2.0)

idinteger

The id that was sent in the request

Example response

{
  "result": {
    "creation_timestamp": 1536569522277,
    "expiration_timestamp": 1536569522277,
    "asks": [
      {
        "last_update_timestamp": 1536569522277,
        "expires_at": 1745312540321
      }
    ],
    "bids": [
      {
        "last_update_timestamp": 1536569522277,
        "expires_at": 1745312540321
      }
    ],
    "legs": [
      {
        "instrument_name": "BTC-PERPETUAL"
      }
    ],
    "hedge": {
      "instrument_name": "BTC-PERPETUAL"
    },
    "combo_id": "BTC-FS-31DEC21-PERP",
    "app_name": "Example Application",
    "taker": "TAKER1"
  }
}