Skip to main content

FIX Component Definitions

Standard Header & Trailer​

The Bullish platform expects standard FIX message header and trailer components on each FIX message sent and received.

Table 1: Standard Header component​

TagField NameReq'dTypeComments
8BeginStringYStringFIX.4.4
9BodyLengthYintStandard FIX message body length
35MsgTypeYStringThe message type. See relevant section.
49SenderCompIDYStringAgreed CompID of the party sending the message.
56TargetCompIDYStringAgreed CompID of the intended message recipient. BULLISH_PROD for production use. BULLISH_SIMNEXT for testing.
34MsgSeqNumYintFIX Message sequence number
50SenderSubIdCStringRequired when sent from Client into Bullish (non-session layer message only). The identity of the entering trader or system.
57TargetSubIdNStringEchoed from the Bullish system to the Client (where present), or ADMIN for administrative messages not intended for a specific user.
43PossDupFlagNBooleanWhether the message was previously transmitted under the same MsgSeqNum (34). Absence of this field is interpreted as Original Transmission (N).
97PossResendNBooleanWhether the message was previously transmitted under a different MsgSeqNum (34). Absence of this field is interpreted as Original Transmission (N).
52SendingTimeYUTCTimestampSending time in UTC
122OrigSendingTimeNUTCTimestampOriginal message transmission time in UTC where PossDupFlag (43) = Y. If the original time is not available, this should be the same value as SendingTime (52).

Table 2: Standard Trailer component​

TagField NameReq'dTypeComments
10ChecksumYStringStandard FIX checksum