FIX Protocol Message 35=1: Test Request
Asks the counterparty to send a Heartbeat that echoes TestReqID (112). A side sends it when it has received nothing for longer than the heartbeat interval, before deciding the connection is lost.
- MsgType (tag 35)
- 1
- FIX name
- TestRequest
- Category
- Session (administrative)
- FIX versions
- FIX 4.0 to 4.4 and FIXT 1.1
Test Request in each FIX version
The full field layout as defined in a specific version.
Required fields
Body fields that every Test Request message must carry in FIX 4.4, in addition to the standard header and trailer.
- 112TestReqID
Field layout
All body fields in the order of the FIX 4.4 definition, with components and repeating groups indented. A field inside an optional component or group is required only when that component or group is present.
| Tag | Field | Required |
|---|---|---|
| 112 | TestReqID | Required |
Standard header and trailer
Every FIX message starts with the standard header, whose required fields are BeginString (8), BodyLength (9), MsgType (35), SenderCompID (49), TargetCompID (56), MsgSeqNum (34) and SendingTime (52), and ends with the trailer field CheckSum (10).
Decode a Test Request messageAll FIX message types · All FIX tags
Field and message data comes from the QuickFIX data dictionaries for FIX 4.0 to 5.0 SP2 and FIXT 1.1, used under the QuickFIX Software License. This product includes software developed by quickfixengine.org (http://www.quickfixengine.org/). Enumerated value names are converted to plain text for reading.