developers:fixapi:logout

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

developers:fixapi:logout [2025/09/12 01:09] – created chaddevelopers:fixapi:logout [2025/09/12 02:21] (current) – chad
Line 1: Line 1:
-==== Logout ====+====== LOGOUT [35=5] ======
  
-===== Session Termination =====+The Logout message terminates a FIX session.
  
-The Logout message requests or indicates the termination of a FIX session. The logout initiator should wait for a response and/or confirmation to the logout condition. This will permit the counterparty to gently close its connection and honor a potential message gap-fill.+===== Message Specification =====
  
-If the T4 FIX API server initiates a Logout, an issuing physical disconnection will follow. When possible, the T4 FIX API will provide information on the nature or cause of the termination. If the client sends a Logout message, no more messages should be sent by the client.+**Message Direction:** Bidirectional
  
-Under normal operating conditions, the client requests a logout and the T4 FIX API server honors the request. A physical disconnection without an exchange of Logout messages is considered an abnormal condition.+^ Tag ^ Field Name ^ Type ^ Req'd ^ Description ^ 
 +| | **Message Header** | | Y | MsgType = 5 | 
 +| 58 | Text | String | O | Logout reason or status | 
 +| | **Message Trailer** | | Y | |
  
-===== Failed Authentication ===== +===== Sample Messages =====
- +
-To start a new FIX session, the T4 FIX API will need to reach successful authentication of the client's Logon message. To provide as much information as possible, a failed authentication is responded (by the T4 FIX API) with a Logout message. +
- +
-A new FIX session (with sequence numbers reset to 1) will be required after the receipt of a Logout message and its subsequent physical disconnection. +
- +
-===== Message Dictionary ===== +
- +
-^ Tag             ^ Field Name       ^ Req'd  ^ Comments                                  ^ +
-| (Standard Header) | Y               | MsgType = 5                               | +
-| 58              | Text             | N      | Free format text string. Contains information related to the cause of the logout. | +
-| (Standard Trailer) | Y               |                                           | +
- +
-===== Sample Message ===== +
- +
-Client request to logout:+
  
 +**Client Logout Request:**
 <code> <code>
-34=2|49=CTS|56=T4Example|52=20120904-22:13:57.789|+8=FIX.4.2|9=50|35=5|49=T4Example|56=T4|52=20120904-22:13:57.789|10=123|
 </code> </code>
  
 +**Server Logout Response:**
 <code> <code>
-[FIXLOGOUT]   +8=FIX.4.2|9=100|35=5|49=T4|56=T4Example|50=T4FIX|52=20120904-22:13:57.789| 
-[MsgSeqNum] 34 = 2   +58=Successful logout upon request|10=234|
-[SenderCompID] 49 = CTS   +
-[TargetCompID] 56 = T4Example   +
-[SendingTime] 52 = 20120904-22:13:57.789  +
 </code> </code>
  
-Server Response: +===== Notes ===== 
- +  * Initiator should wait for response before disconnecting 
-<code> +  * Failed authentication returns Logout with error in Text (58) 
-34=2|49=T4Example|56=CTS|50=T4FIX|52=20120904-22:13:57.789|58=Successful logout upon request| +  * Physical disconnect without Logout is abnormal 
-</code> +  * New session requires sequence reset to 1
- +
-<code> +
-[FIXLOGOUT]   +
-[MsgSeqNum] 34 = 2   +
-[SenderCompID] 49 = T4Example   +
-[TargetCompID] 56 = CTS   +
-[SenderSubID] 50 = T4FIX   +
-[SendingTime] 52 = 20120904-22:13:57.789   +
-[Text] 58 = Successful logout upon request   +
-</code> +
- +
-[[developers:legacy_fix_api|T4 FIX API Home]] +
  • developers/fixapi/logout.txt
  • Last modified: 2025/09/12 02:21
  • by chad