developers:fixapi.testrequest [WIKI]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Test Request ======


===== Session Integrity Check =====

A Test Request message forces a response from the counterparty to acknowledge the continuation of FIX Session connectivity. Test requests can occur at any time during the FIX Session. When a test request is received, the party is obligated to respond to the Test Request message with a Heartbeat. Such heartbeat must also contain the **TestRequestID** (Tag 112) that originated in the Test Request message.

Test Request messages also provide an opportunity to check for out-of-sequence conditions. It permits checking for the expected outgoing sequence number (**Tag 34** of the Test Request) and expected incoming sequence number (**Tag 34** of the mandatory Heartbeat response).

The **TestRequestID** (Tag 112) can be text of any form. A unique string is recommended (e.g., the current time string) for pairing the Test Request with its corresponding Heartbeat.

===== Message Dictionary =====

^ Tag  ^ Field Name       ^ Req'd ^ Comments                                                                   ^
| **Standard Header**     | Y     | MsgType = 1                                                               |
| 112                     | TestReqID | Y     | Required when the heartbeat is the result of a Test Request message |
| **Standard Trailer**    | Y     |                                                                              |

===== Sample Messages =====

**Test Request generated by the client:**
<code>
34=123|49=T4Example|56=T4|50=TraderName|52=20120905-18:09:12.103|112=treqid.09.05.2012-13.09.12|
</code>

<code>
[FIXTESTREQUEST]
[MsgSeqNum] 34 = 123
[SenderCompID] 49 = T4Example
[TargetCompID] 56 = T4
[SenderSubID] 50 = TraderName
[SendingTime] 52 = 20120905-18:09:12.103
[TestReqID] 112 = treqid.09.05.2012-13.09.12
</code>

**Heartbeat response to the client's Test Request:**
<code>
34=72|49=T4|56=T4Example|50=T4FIX|52=20120905-18:09:12.119|112=treqid.09.05.2012-13.09.12|
</code>

<code>
[FIXHEARTBEAT]
[MsgSeqNum] 34 = 72
[SenderCompID] 49 = T4
[TargetCompID] 56 = T4Example
[SenderSubID] 50 = T4FIX
[SendingTime] 52 = 20120905-18:09:12.119
[TestReqID] 112 = treqid.09.05.2012-13.09.12
</code>

**Test Request generated by the T4 FIX API Server:**
<code>
34=122|49=T4|56=T4Example|50=T4FIX|52=20120905-18:34:21.398|112=cts-20120905-18:34:21.398|
</code>

<code>
[FIXTESTREQUEST]
[MsgSeqNum] 34 = 122
[SenderCompID] 49 = T4
[TargetCompID] 56 = T4Example
[SenderSubID] 50 = T4FIX
[SendingTime] 52 = 20120905-18:34:21.398
[TestReqID] 112 = cts-20120905-18:34:21.398
</code>

**Client Heartbeat response to the T4 FIX API Server Test Request:**
<code>
34=173|49=T4Example|56=T4|52=20120905-18:34:36.436|112=cts-20120905-18:34:21.398|
</code>

<code>
[FIXHEARTBEAT]
[MsgSeqNum] 34 = 173
[SenderCompID] 49 = T4Example
[TargetCompID] 56 = T4
[SendingTime] 52 = 20120905-18:34:36.436
[TestReqID] 112 = cts-20120905-18:34:21.398
</code>


[[developers:legacy_fix_api|T4 FIX API Home]]