MassOrder (35=DJ)
The MassOrder message, which we adopted from FIX 5.0 SP2, can be used to add or cancel multiple unrelated orders with a single message. Only the key order attributes for high performance trading are available.The behaviour of individual orders within a MassOrder (35=DJ) may vary depending upon its attributes, e.g. OrdType (40) and TimeInForce (59). Individual orders may be cancelled with single order messages such as OrderCancelRequest. Each of the orders in the MassOrder (35=DJ) are to be treated as stand-alone individual orders.
Response Attributes: MassOrder sends 35=D or 35=F in batch respectively. Each order will follow their respective execution report. See ExecutionReport for details.
Request
Body
required
- Array [
- ]
Request ID. Will be echoed back in the respective Pending New or Pending Cancel messages.
Must be 2: Ack each order
1 to 10
Fee currency for trade. Only present if this message was the result of a fill.
Valid Values: [SPOT] Buy - Base/Quote token/USD/USDT/EUR [SPOT] Sell - Quote token/USD/USDT/EUR [DERIV] Buy/Sell - USD/USDT/EUR
Example: If a client would like to BUY CRO/BTC, the default fee token is CRO, valid tokens are CRO/BTC/USD/USDT/EUR. If a client would like to SELL CRO/BTC, the default fee token is BTC, valid tokens are BTC/USD/USDT/EUR. If a client would like to BUY/SELL BTCUSD-PERP, the default fee token is USD, valid tokens are USD/USDT/EUR.
If a client has an insufficient balance in their preferred fee token, the system will switch to the default fee token.
Possible values: [Y, N]
Must be Y
OrderEntryGrp object[]required
Possible values: >= 1
Number of order entries.
Specifies the action to be taken for the given order.
Possible values: [DJ]
Message Type = DJ (Mass Order)
1 to 10. Must be the same as Tag 2432.
1: Add, 3: Cancel
Schema
Client-selected order ID.
ClOrdID of the previous non-rejected order. i.e. Response from OrderCancelReplaceRequest(35=G) or OrderCancelRequest(35=F).
Possible values: [6, 8]
Instructions for order handling on exchange. If more than one instruction is applicable to an order, this field can contain multiple instructions separated by space.
For CDC internal reference only
Server-assigned order ID
unique execution ID. Equal to Fill ID if this message was the result of a fill
Symbol name
Possible values: [1, 2]
"1": buy; "2": sell
Original order quantity
Original order price
Possible values: [0, 4, 6, 8, A, F, I]
Reason for this message (see below)
Possible values: [0, 1, 2, 4, 6, 8, A]
Order status (Please refer to standard FIX spec)
Quantity of order that has already been filled
Quantity of order that is still open
Possible values: [Y, N]
Indicates if the order is currently being worked.
Time of the order update. Only present on order updates. It is stamped in response flow [no matter there were trades or not]; our system stamp this time when there are updates for an order (so it is called update_time on Web Socket)
TransactTime when order is created with 39=0|150=0. it is stamped in request flow; when our system confirmed and accepted the order (i.e. it is called create_time on Web Socket)
Fill price. Only present if this message was the result of a fill
Fill quantity. Only present if this message was the result of a fill
"2": taker fill; "1": maker fill. Only present if this message was the result of a fill
Average fill price for all fills in order. Only present if this message was the result of a fill
Fee for trade. Only present if this message was the result of a fill
Fee currency for trade. Only present if this message was the result of a fill
Possible values: [3]
Always 3 (absolute)
Reason the order was rejected (see below). Only present on rejected NewOrderSingle (D) requests. i.e. 1 = Unkown symbol, 5 = Unknown Order, 99 = Other
Description of the reason the order was rejected (e.g., Too many requests). Only present on rejected NewOrderSingle (D) requests
Possible values: [1, 2, 3]
1: messages corresponds to a spot order. 2: messages corresponds to a margin order. 3: messages correspond to liquidation.
Trade match ID
TransactTime when order is getting partial filled or fullly filled. It is stamped in response flow [only when there has trade happened]; i.e. the trade time / order matching time of when the trade happened (i.e. the time of this order being matched with another order) [i.e. the transaction_time in Web Socket]
Number of orders matched for this trade execution. If it is Maker's Order, value is always 1. If it is Taker's Order, it is the number of orders matched for this trade execution
Only appears if it is Maker's order. It represents which order entry of corresponding price level was matched. This value is 0 base. If the matched order is on the top of the queue, it is shown 0.
Possible values: [8]
Message Type = 8 (Execution Report)