File: WebAPI/order_statuses_2.proto
Message for holding TransactionStatus enum values as a namespace.
Description: Status of the transaction.
•IN_TRANSIT = 1
Original order is sent to the execution system.
•REJECTED = 2
Original order is rejected (exception).
•ACK_PLACE = 3
Order is acknowledged by the execution system.
•EXPIRED = 4
Order is expired (exception).
•IN_CANCEL = 5
Cancel request is sent to the execution system.
•ACK_CANCEL = 6
Cancel is acknowledged by the execution system.
•REJECT_CANCEL = 7
Cancel request is rejected (exception).
•IN_MODIFY = 8
Modify request is sent to the execution system.
•ACK_MODIFY = 9
Modify is acknowledged by the execution system.
•REJECT_MODIFY = 10
Modify request is rejected (exception).
•FILL = 11
Fill event is received from the execution system.
•SUSPEND = 12
Order is suspended (parked).
•FILL_CORRECT = 13
Referenced fill is corrected.
•FILL_CANCEL = 14
Referenced fill is canceled (exception).
•FILL_BUST = 15
Referenced fill is busted (exception).
•ACTIVEAT = 16
Acknowledgment that the order will activate at specified time.
•DISCONNECT = 17
Order may be canceled because a disconnect occurred (exception).
•SYNTHETIC_ACTIVATED = 18
Synthetic order was sent to the actual execution system.
•UPDATE = 19
Order status and/ or attributes are updated.
•SYNTHETIC_FAILED = 20
Synthetic strategy execution failed, expect ‘text_message’ attribute with further details. The client may identify outright orders used when attempting to execute the synthetic strategy by finding orders in its book where OrderStatus.origin_order_id == OrderStatus.order_id.
•SYNTHETIC_OVERFILL = 21
Synthetic strategy order has at least one overfilled leg, ‘synthetic_hang’ attribute is populated.
•SYNTHETIC_HANG = 22
Hanging quantity update for the synthetic strategy order.
•APPROVING = 23
Cross order is in OrderStatus.APPROVE_REQUIRED and TransactionStatus.APPROVING state when it is acknowledged by exchange but waiting for approval from counter-parties. Note: If the exchange does not support this status, APPROVED_BY_EXCHANGE status is sent instead.
•APPROVE_REQUESTED = 24
Cross order is in OrderStatus.APPROVE_REQUIRED and TransactionStatus.APPROVE_REQUESTED state when it is waiting for approval from the client (i.e. from the side/participant that received this transaction).
•APPROVED_BY_EXCHANGE = 25
The exchange approved the cross order. Note that this approval relates only to the sides/participants specified in the order. Thus, it is not implied that the exchange approved the other sides of the order (counter-parties).
•REJECTED_BY_USER = 26
Cross order is rejected by one of its participants. Note that if a participant rejects its own side of the cross order, the counter-parties may not receive any reject messages if exchange does not support this notification.
•MATCHED = 27
Cross order is executed on exchange.
•TRADE_BROKEN = 28
Cross order/leg have been broken by the exchange.
•TRADE_AMENDED = 29
Previously matched cross order/leg have been amended by the exchange.
•FILLS_ALLOCATION = 30
Fills of allocation order are allocated or previous fills allocation is canceled. See order_2.AllocationRequest for more details.
•ACCESS_REMOVED = 31
Indicates that this account has lost access to this order. Client applications may remove any stored information about this order, especially order fills, since they no longer relate to this account.
•ACCESS_RESTORED = 32
Indicates that this account’s access to this order has been restored. Client applications may use this order and its fills again. An order history may look like: IN_TRANSIT, ACK_PLACE, FILL, ACCESS_REMOVED, FILL, ACCESS_RESTORED.