Least Significant Bit (Bit 0): IsModifyOrder - indicate this is to Modify existing order if set to 1. Bit 1 through 7: Reserved for future use. For backward compatibility, client should always look at each individual bit for the corresponding flag. Otherwise problems might occur when bits 1 through 7 start to be utilized.

Indicate if this is an implied order or not.

Indicate whether it is just an RFQ or not. Client should filter the order if it doesn't care about RFQ.

Unique identifier of the market.

This field can be used to get the order modification time. The format is nanoseconds since Jan 1st, 1970, 00:00:00 GMT. The nanosecond part is currently 000 and might be supported later.

Order entry date time. Milliseconds since Jan 1st, 1970, 00:00:00 GMT.

Unique identifier of the order.

Sequence ID of the order. When an order is modified, this will be incremented while OrderID remains the same. It is for legacy reason and can be ignored.

Price of the bid/offer. OrderPriceDenominator for the market should be applied to get the real price.

Quantity.

This field can be used to get the time the trading engine received the request that triggers this message. The format is nanoseconds since Jan 1st, 1970, 00:00:00 GMT. The nanosecond part is currently 000 and might be supported later. Note: This field could be set to different values or `0` for some scenarios. Please refer to the FAQs for more details.

Date-time of the message sent.

Can be used in conjunction with `OrderEntryDateTime` field for priority of orders within same milliseconds time.

Tells whether order represents bid or offer.