Home / FIX.4.1 / Messages / ListStatus

ListStatus

← ListExecute→ ListStatusRequest
MsgTypeN
CategoryProgramTrading
SectionTrade
AddedFIX.2.7
Fields35
Components2
The list status message is issued as the response to a List Status Request message and indicates the current state of the orders within the list as they exists at the broker's site.

Message Structure

35 fields, 2 components/groups — click any tag or field name for details
TagNameTypeReq DescriptionAdded
◈ StandardHeader [Component]YMsgType = NFIX.2.7
8BeginStringcharYFIX.4.1 (Always unencrypted, must be first field in message)FIX.4.0
9BodyLengthintY(Always unencrypted, must be second field in message)FIX.4.0
35MsgTypecharY(Always unencrypted, must be third field in message)
▶ 28 enum values
ValueNameDescription
0HeartbeatHeartbeat
1TestRequestTest Request
2ResendRequestResend Request
3RejectReject
4SequenceResetSequence Reset
5LogoutLogout
6IOIIndication of Interest
7AdvertisementAdvertisement
8ExecutionReportExecution Report
9OrderCancelRejectOrder Cancel Reject
ALogonLogon
BNewsNews
CEmailEmail
DNewOrderSingleOrder - Single
ENewOrderListOrder - List
FOrderCancelRequestOrder Cancel Request
GOrderCancelReplaceRequestOrder Cancel/Replace Request
HOrderStatusRequestOrder Status Request
JAllocationInstructionAllocation
KListCancelRequestList Cancel Request
LListExecuteList Execute
MListStatusRequestList Status Request
NListStatusList Status
PAllocationInstructionAckAllocation ACK
QDontKnowTradeDont Know Trade (DK)
RQuoteRequestQuote Request
SQuoteQuote
TSettlementInstructionsSettlement Instructions
FIX.4.0
49SenderCompIDcharY(Always unencrypted)FIX.4.0
56TargetCompIDcharY(Always unencrypted)FIX.4.0
115OnBehalfOfCompIDcharNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)FIX.4.0
128DeliverToCompIDcharNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)FIX.4.0
90SecureDataLenLengthNRequired to identify length of encrypted section of message. (Always unencrypted)FIX.4.0
91SecureDatadataNRequired when message body is encrypted. Always immediately follows SecureDataLen field.FIX.4.0
34MsgSeqNumintY(Can be embedded within encrypted data section.)FIX.4.0
50SenderSubIDcharN(Can be embedded within encrypted data section.)FIX.4.0
142SenderLocationIDcharNTrading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)FIX.4.1
57TargetSubIDcharN"ADMIN" reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)FIX.4.0
143TargetLocationIDcharNTrading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)FIX.4.1
116OnBehalfOfSubIDcharNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)FIX.4.0
144OnBehalfOfLocationIDcharNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)FIX.4.1
129DeliverToSubIDcharNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)FIX.4.0
145DeliverToLocationIDcharNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)FIX.4.1
43PossDupFlagcharNAlways required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)
▶ 2 enum values
ValueNameDescription
NOriginalTransmissionOriginal transmission
YPossibleDuplicatePossible duplicate
FIX.4.0
97PossResendcharNRequired when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)
▶ 2 enum values
ValueNameDescription
NOriginalTransmissionOriginal transmission
YPossibleResendPossible resend
FIX.4.0
52SendingTimetimeY(Can be embedded within encrypted data section.)FIX.4.0
122OrigSendingTimetimeNRequired for message resends. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)FIX.4.0
66ListIDcharYUnique identifier for list as assigned by institution, used to associate multiple individual orders. Uniqueness must be guaranteed within a single trading day. Firms which generate multi-day orders should consider embedding a date within the ListID field to assure uniqueness across days.FIX.2.7
105WaveNocharNIdentifier to aid in the management of multiple lists derived from a single, master list.FIX.3.0
82NoRptsintYTotal number of messages required to status complete list.FIX.2.7
83RptSeqintYSequence number of this report message.FIX.2.7
73NoOrdersintYNumber of orders statused in this message, i.e. number of repeating groups to follow.FIX.2.7
11ClOrdIDcharYUnique identifier for Order as assigned by institution. Uniqueness must be guaranteed within a single trading day. Firms which electronically submit multi-day orders should consider embedding a date within the ClOrdID field to assure uniqueness across days.FIX.4.0
14CumQtyintYTotal number of shares filled.FIX.4.0
151LeavesQtyintYAmount of shares open for further execution. LeavesQty = OrderQty - CumQty.FIX.4.1
84CxlQtyintYTotal number of shares canceled for this order.FIX.4.0
6AvgPxfloatYCalculated average price of all fills on this order.FIX.4.0
◈ StandardTrailer [Component]YThe standard FIX message trailerFIX.2.7
93SignatureLengthLengthNRequired when trailer contains signature. Note: Not to be included within SecureData fieldFIX.4.0
89SignaturedataNNote: Not to be included within SecureData fieldFIX.4.0
10CheckSumcharY(Always unencrypted, always last field in message)FIX.4.0