BUbullish
otc

Create OTC Trade

Creates an OTC trade, requires bearer token in authorization header.

This endpoint uses the signing format which does not require strict field ordering and addition of null fields in the request body. Prices do not require strict precision. E.g. for asset precision of 4 - 100, 100.0, 100.00, 100.000 and 100.0000 are all accepted.

post/v2/otc-trades

Request

Headers

BX-SIGNATUREstring required

signature obtained using the signing format

BX-TIMESTAMPstring required

timestamp is the number of milliseconds since EPOCH

BX-NONCEstring required

nonce is a client side incremented unsigned 64 bit integer

BX-REFERRERstring

A numeric referrer id if applicable

Request body

commandTypestring required

Specifies the command type and must be ‘V1CreateOtcTrade' to indicate the submission of an OTC trade.

clientOtcTradeIdstring

unique numeric (i64) identifier generated on the client side expressed as a string value

sharedMatchKeystring required

Unique shared key that is agreed between the two customers to represent their OTC trade to be matched on Bullish's OTC Clearing Facility. Must be a 12 to 64 characters alphanumeric value

tradingAccountIdstring required

unique trading account ID

isTakerboolean required
remarksstring

text field for client's internal reference to a trade, max length is 255 characters

Example request

{
  "commandType": "V1CreateOtcTrade",
  "clientOtcTradeId": "20050900225",
  "sharedMatchKey": "cfBtcXrpMatch001",
  "tradingAccountId": "111000000000001",
  "isTaker": true,
  "remarks": "first otc trade with xyz client",
  "trades": [
    {
      "symbol": "BTC-USDC-PERP",
      "side": "BUY",
      "price": "98213.0000",
      "quantity": "1.50000000"
    },
    {
      "symbol": "XRP-USDC-PERP",
      "side": "SELL",
      "price": "2.6600",
      "quantity": "50.000000"
    }
  ]
}

Response

Status OK. The create OTC trade command was successfully acknowledged. To check the current status of the OTC trade, query Get Trade by ID using otcTradeId or clientOtcTradeId received in the response payload.

messagestring required

message indicating the status of the request

requestIdstring required
otcTradeIdstring required

unique numeric (i64) identifier generated on Bullish side expressed as a string value

clientOtcTradeIdstring

unique numeric (i64) identifier generated on the client side expressed as a string value

sharedMatchKeystring required

Unique shared key that is agreed between the two customers to represent their OTC trade to be matched on Bullish's OTC Clearing Facility. Must be a 12 to 64 characters alphanumeric value

Example response

{
  "message": "Command acknowledged - CreateOtcTrade",
  "requestId": "197735387747975680",
  "otcTradeId": "200000000000000098",
  "clientOtcTradeId": "20050900225",
  "sharedMatchKey": "cfBtcXrpMatch001"
}

Changes

No recorded changes to this operation across all 1 revision of this API.