Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| developers:fixapi:start [2025/09/12 02:36] – chad | developers:fixapi:start [2026/06/11 03:59] (current) – [FIX Session Lifecycle] chad | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * SSL-encrypted TCP socket connection | * SSL-encrypted TCP socket connection | ||
| * Authentication via FIX Logon | * Authentication via FIX Logon | ||
| + | |||
| + | To connect your application to T4 you would need to establish an SSL connection to the appropriate system below: | ||
| + | |||
| + | ^ System | ||
| + | | Simulator | ||
| + | | Live | uhfix.t4login.com | ||
| + | |||
| + | |||
| + | |||
| ===== FIX Session Lifecycle ===== | ===== FIX Session Lifecycle ===== | ||
| Line 14: | Line 23: | ||
| Optional: Multiple [[developers: | Optional: Multiple [[developers: | ||
| + | <WRAP center round warning 100%> | ||
| + | The T4 FIX API does not support session recovery. All sessions begin with a sequence number of 1. A full account snapshot will be sent upon account subscription. | ||
| + | |||
| + | [[https:// | ||
| + | </ | ||
| ===== Message Integrity Requirements ===== | ===== Message Integrity Requirements ===== | ||
| * SOH delimiter (ASCII 001) between fields | * SOH delimiter (ASCII 001) between fields | ||