Test Request

8=FIX.4.2
9=66
34=5025
35=1
49=TEST1
52=20160131-16:10:10.614
56=DWFIX01
112=TEST
10=096
8=FIX.4.2
9=52
34=17
35=0
49=DWFIX01
52=20160201-19:35:42
56=TEST1
112=TEST
10=146

What does the Test Request <1> message do?

  • The Test Request <1> message forces a heartbeat from the opposing application and checks sequence numbers or verifies communication line status.

  • The opposite application responds to the Test Request <1> with a Heartbeat <0> containing the TestReqID <112>.

What does the TestReqID <112> message do?

  • The TestReqID <112> verifies that the opposite application is generating the heartbeat as the result of Test Request <1> and not a normal timeout.

  • The opposite application includes the TestReqID <112> in the resulting Heartbeat <0>. Any string can be used as the TestReqID <112> (one suggestion is to use a timestamp string).

TagTag DescriptionExample ValueValue DescriptionRequired
8BeginStringFIX.4.2FIX VersionYes
9BodyLength66Length of messageYes
34MsgSeqNum5025Message sequence numberYes
35MsgType1Test Request MessageYes
49SenderCompIDTEST1Sender IDYes
52SendingTime20160131-16:10:10.614Sending timestampYes
56TargetCompIDDWFIX01Target IDYes
112TestReqIDTESTIdentifier included this message to be returned in resulting Heartbeat <0>
10CheckSum{Checksum}Checksum of messageYes