Deribit Block Trade API

The Block Trade API from Deribit β€” 11 operation(s) for block trade.

OpenAPI Specification

deribit-block-trade-api-openapi.yml Raw ↑
openapi: 3.0.0
info:
  title: Deribit Account Management Block Trade API
  version: 2.1.1
servers:
- url: https://test.deribit.com/api/v2
tags:
- name: Block Trade
paths:
  /private/simulate_block_trade:
    get:
      parameters:
      - in: query
        name: role
        required: false
        schema:
          $ref: '#/components/schemas/role'
        description: Describes if user wants to be maker or taker of trades
      - in: query
        name: trades
        required: true
        schema:
          type: array
          items:
            type: object
            properties:
              instrument_name:
                $ref: '#/components/schemas/instrument_name'
                description: Instrument name
              price:
                type: number
                description: Price for trade
              amount:
                $ref: '#/components/schemas/amount'
                description: It represents the requested trade 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:
                $ref: '#/components/schemas/direction'
                description: Direction of trade from the maker perspective
        description: List of trades for block trade
        style: form
        explode: true
      responses:
        '200':
          $ref: '#/components/responses/PrivateSimulateBlockTradeResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/simulate_block_trade
                  params:
                    role: maker
                    trades:
                    - instrument_name: BTC-PERPETUAL
                      direction: buy
                      price: 11624
                      amount: 40
                    - instrument_name: BTC-9AUG19-10250-P
                      direction: buy
                      amount: 1.2
                      price: 0.0707
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Checks if a block trade can be executed without actually executing it. Use this method to verify that a block trade will succeed before proceeding with the actual execution.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fsimulate_block_trade)


        '
      x-mint:
        metadata:
          title: private/simulate_block_trade
          og:title: private/simulate_block_trade
          keywords:
          - private/simulate_block_trade
          - role
          - trades
        href: /api-reference/block-trade/private-simulate_block_trade
  /private/verify_block_trade:
    get:
      parameters:
      - in: query
        name: timestamp
        required: true
        schema:
          $ref: '#/components/schemas/timestamp'
        description: Timestamp, shared with other party (milliseconds since the UNIX epoch)
      - in: query
        name: nonce
        required: true
        schema:
          $ref: '#/components/schemas/nonce'
        description: Nonce, shared with other party
      - in: query
        name: role
        required: true
        schema:
          $ref: '#/components/schemas/role'
        description: Describes if user wants to be maker or taker of trades
      - in: query
        name: trades
        required: true
        schema:
          type: array
          items:
            type: object
            properties:
              instrument_name:
                $ref: '#/components/schemas/instrument_name'
                description: Instrument name
              price:
                type: number
                description: Price for trade
              amount:
                $ref: '#/components/schemas/amount'
                description: It represents the requested trade 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:
                $ref: '#/components/schemas/direction'
                description: Direction of trade from the maker perspective
        description: List of trades for block trade
        style: form
        explode: true
      responses:
        '200':
          $ref: '#/components/responses/PrivateVerifyBlockTradeResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/verify_block_trade
                  params:
                    nonce: okpdjkdo
                    timestamp: 1565172650935
                    role: maker
                    trades:
                    - instrument_name: BTC-PERPETUAL
                      direction: buy
                      price: 11624
                      amount: 40
                    - instrument_name: BTC-9AUG19-10250-P
                      direction: buy
                      amount: 1.2
                      price: 0.0707
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Verifies and creates a block trade signature. This is the first step in the block trade workflow - the first party calls this method to generate a signature that must be shared with the second party.


        **Note:** In the API, the `direction` field is always expressed from the maker''s perspective. This means that when you accept a block trade as a taker, the direction shown in the API represents the opposite side of your trade. For example, if you are buying puts as a taker, the API will show the operation as a "sell put" (maker''s perspective), and you will be verifying and accepting a "sell put" block trade.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fverify_block_trade)


        '
      x-mint:
        metadata:
          title: private/verify_block_trade
          og:title: private/verify_block_trade
          keywords:
          - private/verify_block_trade
          - timestamp
          - nonce
          - role
          - trades
          - signature
        href: /api-reference/block-trade/private-verify_block_trade
  /private/execute_block_trade:
    get:
      parameters:
      - in: query
        name: timestamp
        required: true
        schema:
          $ref: '#/components/schemas/timestamp'
        description: Timestamp, shared with other party (milliseconds since the UNIX epoch)
      - in: query
        name: nonce
        required: true
        schema:
          $ref: '#/components/schemas/nonce'
        description: Nonce, shared with other party
      - in: query
        name: role
        required: true
        schema:
          $ref: '#/components/schemas/role'
        description: Describes if user wants to be maker or taker of trades
      - in: query
        name: trades
        required: true
        schema:
          type: array
          items:
            type: object
            properties:
              instrument_name:
                $ref: '#/components/schemas/instrument_name'
                description: Instrument name
              price:
                type: number
                description: Price for trade
              amount:
                $ref: '#/components/schemas/amount'
                description: It represents the requested trade 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:
                $ref: '#/components/schemas/direction'
                description: Direction of trade from the maker perspective
        description: List of trades for block trade
        style: form
        explode: true
      - in: query
        name: counterparty_signature
        required: true
        schema:
          $ref: '#/components/schemas/block_trade_signature'
        description: Signature of block trade generated by `private/verify_block_trade_method`
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBlockTradeResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/execute_block_trade
                  params:
                    nonce: bszyprbq
                    timestamp: 1590485535899
                    role: maker
                    trades:
                    - instrument_name: BTC-PERPETUAL
                      direction: sell
                      price: 8900
                      amount: 200000
                    - instrument_name: BTC-28MAY20-9000-C
                      direction: sell
                      amount: 5
                      price: 0.0133
                    counterparty_signature: 1590485595899.1Mn52L_Q.lNyNBzXXo-_QBT_wDuMgnhA7uS9tBqdQ5TLN6rxbuoAiQhyaJYGJrm5IV_9enp9niY_x8D60AJLm3yEKPUY1Dv3T0TW0n5-ADPpJF7Fpj0eVDZpZ6QCdX8snBWrSJ0TtqevnO64RCBlN1dIm2T70PP9dlhiqPDAUYI4fpB1vLYI
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Executes a block trade. This is the second step in the block trade workflow - the second party calls this method with the signature received from the first party to execute the trade.


        The whole request must be exactly the same as in [private/verify_block_trade](https://docs.deribit.com/api-reference/block-trade/private-verify_block_trade), only the `role` field should be set appropriately - this means that both sides have to agree on the same `timestamp`, `nonce`, and `trades` fields, and the server will ensure that the `role` field is different between sides (each party accepts their own role).


        Using the same `timestamp` and `nonce` by both sides in [private/verify_block_trade](https://docs.deribit.com/api-reference/block-trade/private-verify_block_trade) ensures that even if unintentionally both sides execute the given block trade with a valid `counterparty_signature`, the block trade will be executed only once.


        **Note:** In the API, the `direction` field is always expressed from the maker''s perspective. This means that when you accept a block trade as a taker, the direction shown in the API represents the opposite side of your trade. For example, if you are buying puts as a taker, the API will show the operation as a "sell put" (maker''s perspective), and you will be verifying and accepting a "sell put" block trade.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read_write`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fexecute_block_trade)


        '
      x-mint:
        metadata:
          title: private/execute_block_trade
          og:title: private/execute_block_trade
          keywords:
          - private/execute_block_trade
          - timestamp
          - nonce
          - role
          - trades
          - counterparty_signature
          - app_name
          - broker_code
          - broker_name
          - trade_id
          - trade_seq
          - instrument_name
          - order_type
          - advanced
          - order_id
          - matching_id
          - direction
          - tick_direction
          - index_price
          - price
          - amount
          - contracts
          - iv
          - underlying_price
          - liquidation
          - liquidity
          - fee
          - fee_currency
          - label
          - state
          - block_trade_id
          - block_rfq_id
          - block_rfq_quote_id
          - reduce_only
          - post_only
          - mmp
          - risk_reducing
          - api
          - profit_loss
          - mark_price
          - legs
          - combo_id
          - combo_trade_id
          - quote_set_id
          - quote_id
          - trade_allocations
          - user_id
          - client_info
          - client_id
          - client_link_id
          - name
        href: /api-reference/block-trade/private-execute_block_trade
  /private/invalidate_block_trade_signature:
    get:
      parameters:
      - in: query
        name: signature
        required: true
        schema:
          $ref: '#/components/schemas/block_trade_signature'
        description: Signature of block trade that will be invalidated
      responses:
        '200':
          $ref: '#/components/responses/OkResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/invalidate_block_trade_signature
                  params:
                    signature: 1565173369982.1M9tO0Q-.z9n9WyZUU5op9pEz6Jtd2CI71QxQMMsCZAexnIfK9HQRT1pKH3clxeIbY7Bqm-yMcWIoE3IfCDPW5VEdiN-6oS0YkKUyXPD500MUf3ULKhfkmH81EZs
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Invalidates a block trade signature, effectively cancelling the block trade. This can be called at any time before [private/execute_block_trade](https://docs.deribit.com/api-reference/block-trade/private-execute_block_trade) is called.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read_write`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Finvalidate_block_trade_signature)


        '
      x-mint:
        metadata:
          title: private/invalidate_block_trade_signature
          og:title: private/invalidate_block_trade_signature
          keywords:
          - private/invalidate_block_trade_signature
          - signature
        href: /api-reference/block-trade/private-invalidate_block_trade_signature
  /private/get_block_trade:
    get:
      parameters:
      - in: query
        name: id
        required: true
        schema:
          $ref: '#/components/schemas/block_trade_id'
        description: Block trade id
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBlockTradeResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/get_block_trade
                  params:
                    id: '61'
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Returns information about a specific block trade identified by `block_trade_id`.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_block_trade)


        '
      x-mint:
        metadata:
          title: private/get_block_trade
          og:title: private/get_block_trade
          keywords:
          - private/get_block_trade
          - id
          - timestamp
          - trades
          - app_name
          - broker_code
          - broker_name
          - trade_id
          - trade_seq
          - instrument_name
          - order_type
          - advanced
          - order_id
          - matching_id
          - direction
          - tick_direction
          - index_price
          - price
          - amount
          - contracts
          - iv
          - underlying_price
          - liquidation
          - liquidity
          - fee
          - fee_currency
          - label
          - state
          - block_trade_id
          - block_rfq_id
          - block_rfq_quote_id
          - reduce_only
          - post_only
          - mmp
          - risk_reducing
          - api
          - profit_loss
          - mark_price
          - legs
          - combo_id
          - combo_trade_id
          - quote_set_id
          - quote_id
          - trade_allocations
          - user_id
          - client_info
          - client_id
          - client_link_id
          - name
        href: /api-reference/block-trade/private-get_block_trade
  /private/get_block_trades:
    get:
      parameters:
      - in: query
        name: currency
        required: false
        schema:
          $ref: '#/components/schemas/currency'
        description: The currency symbol
      - name: count
        in: query
        required: false
        schema:
          type: integer
          maximum: 101
          minimum: 1
        description: Count of Block Trades returned, maximum - `101`
      - name: start_id
        required: false
        in: query
        schema:
          $ref: '#/components/schemas/block_trade_id'
        description: Response will contain block trades older than the one provided in this field
      - name: end_id
        required: false
        in: query
        schema:
          $ref: '#/components/schemas/block_trade_id'
        description: The id of the oldest block trade to be returned, `start_id` is required with `end_id`
      - name: block_rfq_id
        required: false
        in: query
        schema:
          type: integer
        description: ID of the Block RFQ
      - name: broker_code
        in: query
        required: false
        schema:
          type: string
          example: 2krM7sJsx
        description: Broker code to filter block trades. Only broker clients can use `broker_code` to filter broker block trades. Use `any` for all block trades.
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBlockTradesResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/get_block_trades
                  params:
                    currency: BTC
                    count: 1
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Returns a list of the user''s block trades. If currency is not provided, returns block trades for all currencies. `block_rfq_id` can be provided to receive block trades related to that particular Block RFQ.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_block_trades)


        '
      x-mint:
        metadata:
          title: private/get_block_trades
          og:title: private/get_block_trades
          keywords:
          - private/get_block_trades
          - currency
          - count
          - start_id
          - end_id
          - block_rfq_id
          - broker_code
          - timestamp
          - trades
          - app_name
          - broker_name
          - trade_id
          - trade_seq
          - instrument_name
          - order_type
          - advanced
          - order_id
          - matching_id
          - direction
          - tick_direction
          - index_price
          - price
          - amount
          - contracts
          - iv
          - underlying_price
          - liquidation
          - liquidity
          - fee
          - fee_currency
          - label
          - state
          - block_trade_id
          - block_rfq_quote_id
          - reduce_only
          - post_only
          - mmp
          - risk_reducing
          - api
          - profit_loss
          - mark_price
          - legs
          - combo_id
          - combo_trade_id
          - quote_set_id
          - quote_id
          - trade_allocations
          - user_id
          - client_info
          - client_id
          - client_link_id
          - name
        href: /api-reference/block-trade/private-get_block_trades
  /private/get_block_trade_requests:
    get:
      parameters:
      - name: broker_code
        in: query
        required: false
        schema:
          type: string
          example: jpqYKgg1
        description: Broker code to filter block trade requests. Only broker clients can use `broker_code` to query for their executed broker block trades.
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBlockTradeRequestsResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/get_block_trade_requests
                  params:
                    broker_code: jpqYKgg1
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Provides a list of block trade requests including pending approvals, declined trades, and expired trades. `timestamp` and `nonce` received in response can be used with [private/approve_block_trade](https://docs.deribit.com/api-reference/block-trade/private-approve_block_trade) or [private/reject_block_trade](https://docs.deribit.com/api-reference/block-trade/private-reject_block_trade) to approve or reject the pending block trade.


        To use the block trade approval feature, an [additional API key setting feature](https://docs.deribit.com/articles/creating-api-key#block-trade-approval-feature) called `enabled_features: block_trade_approval` is required. This key has to be given to the broker/registered partner who performs the trades on behalf of the user for the feature to be active. If the user wants to approve the trade, they must approve it from a different API key that doesn''t have this feature enabled.


        Only broker clients can use `broker_code` to query for their broker block trade requests.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_block_trade_requests)


        '
      x-mint:
        metadata:
          title: private/get_block_trade_requests
          og:title: private/get_block_trade_requests
          keywords:
          - private/get_block_trade_requests
          - broker_code
          - nonce
          - timestamp
          - trades
          - app_name
          - username
          - role
          - user_id
          - broker_name
          - state
          - counterparty_state
          - combo_id
          - value
        href: /api-reference/block-trade/private-get_block_trade_requests
  /private/approve_block_trade:
    get:
      parameters:
      - in: query
        name: timestamp
        required: true
        schema:
          $ref: '#/components/schemas/timestamp'
        description: Timestamp, shared with other party (milliseconds since the UNIX epoch)
      - in: query
        name: nonce
        required: true
        schema:
          $ref: '#/components/schemas/nonce'
        description: Nonce, shared with other party
      - in: query
        name: role
        required: true
        schema:
          $ref: '#/components/schemas/role'
        description: Describes if user wants to be maker or taker of trades
      responses:
        '200':
          $ref: '#/components/responses/OkResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/approve_block_trade
                  params:
                    timestamp: 1711468813551
                    nonce: bt-468nha
                    role: maker
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Approves a pending block trade. `nonce` and `timestamp` are used to identify the block trade while `role` should be opposite to the trading counterparty.


        Use [private/get_block_trade_requests](https://docs.deribit.com/api-reference/block-trade/private-get_block_trade_requests) to retrieve pending block trades that require approval.


        To use the block trade approval feature, an [additional API key setting feature](https://docs.deribit.com/articles/creating-api-key#block-trade-approval-feature) called `enabled_features: block_trade_approval` is required. This key has to be given to the broker/registered partner who performs the trades on behalf of the user for the feature to be active. If the user wants to approve the trade, they must approve it from a different API key that doesn''t have this feature enabled.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read_write`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fapprove_block_trade)


        '
      x-mint:
        metadata:
          title: private/approve_block_trade
          og:title: private/approve_block_trade
          keywords:
          - private/approve_block_trade
          - timestamp
          - nonce
          - role
        href: /api-reference/block-trade/private-approve_block_trade
  /private/reject_block_trade:
    get:
      parameters:
      - in: query
        name: timestamp
        required: true
        schema:
          $ref: '#/components/schemas/timestamp'
        description: Timestamp, shared with other party (milliseconds since the UNIX epoch)
      - in: query
        name: nonce
        required: true
        schema:
          $ref: '#/components/schemas/nonce'
        description: Nonce, shared with other party
      - in: query
        name: role
        required: true
        schema:
          $ref: '#/components/schemas/role'
        description: Describes if user wants to be maker or taker of trades
      responses:
        '200':
          $ref: '#/components/responses/OkResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/reject_block_trade
                  params:
                    timestamp: 1711468813551
                    nonce: bt-468nha
                    role: maker
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: 'Rejects a pending block trade. `nonce` and `timestamp` are used to identify the block trade while `role` should be opposite to the trading counterparty.


        Use [private/get_block_trade_requests](https://docs.deribit.com/api-reference/block-trade/private-get_block_trade_requests) to retrieve pending block trades that require approval.


        To use the block trade approval feature, an [additional API key setting feature](https://docs.deribit.com/articles/creating-api-key#block-trade-approval-feature) called `enabled_features: block_trade_approval` is required. This key has to be given to the broker/registered partner who performs the trades on behalf of the user for the feature to be active. If the user wants to approve the trade, they must approve it from a different API key that doesn''t have this feature enabled.


        **πŸ“– Related Article:** [Block Trading](https://docs.deribit.com/articles/block-trading-api)


        **Scope:** `block_trade:read_write`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Freject_block_trade)


        '
      x-mint:
        metadata:
          title: private/reject_block_trade
          og:title: private/reject_block_trade
          keywords:
          - private/reject_block_trade
          - timestamp
          - nonce
          - role
        href: /api-reference/block-trade/private-reject_block_trade
  /private/get_broker_trades:
    get:
      parameters:
      - in: query
        name: currency
        required: false
        schema:
          $ref: '#/components/schemas/currency'
        description: The currency symbol
      - name: count
        required: false
        in: query
        schema:
          type: integer
          maximum: 1000
          minimum: 1
        description: Number of requested items, default - `20`, maximum - `1000`
      - name: start_id
        required: false
        in: query
        schema:
          $ref: '#/components/schemas/block_trade_id'
        description: Response will contain block trades older than the one provided in this field
      - name: end_id
        required: false
        in: query
        schema:
          $ref: '#/components/schemas/block_trade_id'
        description: The id of the oldest block trade to be returned, `start_id` is required with `end_id`
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBrokerTradesResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 1
                  method: private/get_broker_trades
                  params:
                    currency: BTC
                    count: 1
                description: JSON-RPC Request Example
        description: JSON-RPC request body
      description: '**Broker Method** Returns list of broker block trades. If currency is not provided, returns broker block trades for all currencies.


        **Scope:** `block_trade:read`


        [Try in API console](https://test.deribit.com/api_console?method=%2Fprivate%2Fget_broker_trades)


        '
      x-mint:
        metadata:
          title: private/get_broker_trades
          og:title: private/get_broker_trades
          keywords:
          - private/get_broker_trades
          - currency
          - count
          - start_id
          - end_id
          - history
          - next_start_id
          - timestamp
          - trades
          - maker
          - taker
          - app_name
          - broker_code
          - broker_name
          - trade_id
          - trade_seq
          - instrument_name
          - order_type
          - advanced
          - order_id
          - matching_id
          - direction
          - tick_direction
          - index_price
          - price
          - amount
          - contracts
          - iv
          - underlying_price
          - liquidation
          - liquidity
          - fee
          - fee_currency
          - label
          - state
          - block_trade_id
          - block_rfq_id
          - block_rfq_quote_id
          - reduce_only
          - post_only
          - mmp
          - risk_reducing
          - api
          - profit_loss
          - mark_price
          - legs
          - combo_id
          - combo_trade_id
          - quote_set_id
          - quote_id
          - trade_allocations
          - user_id
          - client_info
          - client_id
          - client_link_id
          - name
          - client_name
          - client_link_name
        href: /api-reference/block-trade/private-get_broker_trades
  /private/get_broker_trade_requests:
    get:
      responses:
        '200':
          $ref: '#/components/responses/PrivateGetBrokerTradeRequestsResponse'
      tags:
      - Block Trade
      requestBody:
        content:
          application/json:
            examples:
              request:
                value:
                  jsonrpc: '2.0'
                  id: 7
                  method: private/get_br

# --- truncated at 32 KB (64 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/deribit/refs/heads/main/openapi/deribit-block-trade-api-openapi.yml