private/approve_block_trade

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 to retrieve pending block trades that require approval.

To use the block trade approval feature, an additional API key setting 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

Scope: block_trade:read_write

Try in API console

cURL

cURL

curl --request GET \
  --url https://test.deribit.com/api/v2/private/approve_block_trade \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "private/approve_block_trade",
  "params": {
    "timestamp": 1711468813551,
    "nonce": "bt-468nha",
    "role": "maker"
  }
}
'

200

{
  "jsonrpc": "2.0",
  "id": 1569,
  "result": "ok"
}

Query Parameters

timestamp · integer · required

Timestamp, shared with other party (milliseconds since the UNIX epoch) The timestamp (milliseconds since the Unix epoch)

Example:

1536569522277

nonce · string · required

Nonce

Example:

"bF1_gfgcsd"

role · enum<string> · required

Describes if user wants to be maker or taker of trades Trade role of the user: maker or taker

Available options: maker, taker

Response

200 - application/json

Success response

jsonrpc · enum<string> · required

The JSON-RPC version (2.0)

Available options: 2.0

result · enum<string> · required

Result of method execution. ok in case of success

Available options: ok

id · integer

The id that was sent in the request