faq:logon

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
faq:logon [2025/01/16 13:46] – robfaq:logon [2025/01/16 20:17] (current) – rob
Line 1: Line 1:
 ====== Logon ====== ====== Logon ======
-If at anytime you require assistance from CTS you must send in your FIX messages to [[:[email protected]|<span style="color:blue;">[email protected]]].+If at anytime you require assistance from CTS you must send in your FIX messages to [[:[email protected]|[email protected]]].
  
-===== Our API support will not answer if the messages aren't delimited in a reasonable way for readability =====+<WRAP center round alert 100%> 
 +Our API support will reject your messages are not delimited in a reasonable way for readability 
 +</WRAP> 
 + 
  
 ==== Session Initiation ==== ==== Session Initiation ====
Line 23: Line 26:
 | SecureDataLen | 90 | Length of License Code string | | SecureDataLen | 90 | Length of License Code string |
  
-Failure to provide the correct parameters in the Logon message will result in a logon failure. Appropriately, a [[Logout|<span style="color:blue;">Logout</span>]] message will be sent to the client. The [[Logout|<span style="color:blue;">Logout</span>]] message will contain a short description of the failure to help determine the cause of failed authentication. Thereafter, a physical disconnection will occur. As the FIX Session failed, the T4 FIX API will expect a new attempt for a new FIX session. The next Logon message (from the client) must start with sequence number 1.+Failure to provide the correct parameters in the Logon message will result in a logon failure. Appropriately, a [[Logout|Logout]] message will be sent to the client. The [[Logout|Logout]] message will contain a short description of the failure to help determine the cause of failed authentication. Thereafter, a physical disconnection will occur. As the FIX Session failed, the T4 FIX API will expect a new attempt for a new FIX session. The next Logon message (from the client) must start with sequence number 1.
  
 ==== Setting FIX Session Properties upon Logon ==== ==== Setting FIX Session Properties upon Logon ====
Line 31: Line 34:
 ==== Default Logon Properties ==== ==== Default Logon Properties ====
  
-A successful FIX Session is acknowledged with the expected (echo) Logon message. In addition, if no RefMsgTypes (Tag 372) are specified in the Logon request, the T4 FIX API will automatically return the account portfolio (as [[Execution Report|<span style="color:blue;">Execution Reports</span>]]) and account details (as [[Collateral Report|<span style="color:blue;">Collateral Reports</span>]]). To disable automatic portfolio/account-details listing (a.k.a. AutoPortfolio Refresh), the Logon request message must explicitly include a RefMsgType equal to "d" (Tag 372=d). This option (Tag 372=d) provides minimum login message flow at the expense of potentially missing order/fill updates that occurred while disconnected. By default, the T4 FIX API will also automatically subscribe to __all__ accounts authorized for the logon user (unless disabled with RefMsgType equal to "BB" - Tag 372=BB).+A successful FIX Session is acknowledged with the expected (echo) Logon message. In addition, if no RefMsgTypes (Tag 372) are specified in the Logon request, the T4 FIX API will automatically return the account portfolio (as [[Execution Report|Execution Reports]]) and account details (as [[Collateral Report|Collateral Reports]]). To disable automatic portfolio/account-details listing (a.k.a. AutoPortfolio Refresh), the Logon request message must explicitly include a RefMsgType equal to "d" (Tag 372=d). This option (Tag 372=d) provides minimum login message flow at the expense of potentially missing order/fill updates that occurred while disconnected. By default, the T4 FIX API will also automatically subscribe to __all__ accounts authorized for the logon user (unless disabled with RefMsgType equal to "BB" - Tag 372=BB).
  
 ==== User Configuration ==== ==== User Configuration ====
Line 60: Line 63:
 |  |  |  | c = Enables security definitions requests. | |  |  |  | c = Enables security definitions requests. |
 |  |  |  | 8 = Enables Pending Execution reports for order submittal, cancel replaces, and cancel requests. | |  |  |  | 8 = Enables Pending Execution reports for order submittal, cancel replaces, and cancel requests. |
-|  |  |  | <span style="color: red;">D = Enables Decimal pricing in order entry, market, and chart data. This is required to use the 8 decimal place 2yr Note prices from January 2019 onwards.</span> |+|  |  |  | <color #ed1c24>D = Enables Decimal pricing in order entry, market, and chart data. This is required to use the 8 decimal place 2yr Note prices from January 2019 onwards.</color> |
 |  |  |  | BA = Enables Drop Copies only. All account events are reported but order submittal is disabled. | |  |  |  | BA = Enables Drop Copies only. All account events are reported but order submittal is disabled. |
 |  |  |  | BG = Enables dynamic account notifications. Position and Account collateral reports will be generated automatically. | |  |  |  | BG = Enables dynamic account notifications. Position and Account collateral reports will be generated automatically. |
Line 73: Line 76:
 In this example, the T4 FIX API client requests the start of a FIX Session. The client disables portfolio lists (Tag 372=d). Subsequently, the login request is successful as signaled by a Login message response from the T4 FIX API. In this example, the T4 FIX API client requests the start of a FIX Session. The client disables portfolio lists (Tag 372=d). Subsequently, the login request is successful as signaled by a Login message response from the T4 FIX API.
  
-<span style="color:green;">Login Request from T4 FIX API Client</span><br/>+<color #22b14c>Login Request from T4 FIX API Client</color>
  
 <code> <code>
Line 93: Line 96:
 </code> </code>
  
-<span style="color:green;">Successful Login Response from T4 FIX API</span>  +<color #22b14c>Successful Login Response from T4 FIX API</color>
 <code> <code>
 << 6/7/2013 9:47:24 AM  [fixlogin] 34=1|49=T4|56=T4Example|50=T4FIX|52=20130607-14:47:24.085|98=0|108=30|553=_username_|554=***|1408=4.1.1.1|   << 6/7/2013 9:47:24 AM  [fixlogin] 34=1|49=T4|56=T4Example|50=T4FIX|52=20130607-14:47:24.085|98=0|108=30|553=_username_|554=***|1408=4.1.1.1|  
  • faq/logon.1737035191.txt.gz
  • Last modified: 2025/01/16 13:46
  • by rob