Creates block trade
The whole request have to be exact the same as in private/verify_block_trade, only role field should be set appropriately - it basically means that both sides have to agree on the same timestamp, nonce, trades fields and server will assure that role field is different between sides (each party accepted own role).
Using the same timestamp and nonce by both sides in private/verify_block_trade assures that even if unintentionally both sides execute given block trade with valid counterparty_signature, the given 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 Support Article: Block Trading
Scope: block_trade:read_write
Timestamp, shared with other party (milliseconds since the UNIX epoch) The timestamp (milliseconds since the Unix epoch)
1536569522277
Nonce
"bF1_gfgcsd"
Describes if user wants to be maker or taker of trades
Trade role of the user: maker or taker
maker, taker List of trades for block trade JSON string containing array of objects
Signature of block trade generated by private/verify_block_trade_method
Signature of block trade
It is valid only for 5 minutes around given timestamp
"1565173369982.1M9tO0Q-.z9n9WyZUU5op9pEz6Jtd2CI71QxQMMsCZAexnIfK9HQRT1pKH3clxeIbY7Bqm-yMcWIoE3IfCDPW5VEdiN-6oS0YkKUyXPD500MUf3ULKhfkmH81EZs"