Every FIX message must include a standard header and trailer. The header contains essential routing and sequence information, while the trailer provides message integrity verification.Documentation Index
Fetch the complete documentation index at: https://kraken-sandbox.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- FIX Specification
FIX.4.4. Must be the first field in the message.
Must be the second field in the message.
Must be the third field in the message.
Provided by Customer during onboarding.
Provided by Customer during onboarding.
Message sequence number.
Always required for retransmitted messages, whether prompted by the sending system or as the result of a resend request.
Required when the message may be duplicate of another message sent under a different sequence number.
Time of message transmission expressed in UTC. Format: YYYYMMDD-HH:MM:SS.uuu (required).
Required for message re-sent as a result of a ResendRequest. If data is not available set to same value as SendingTime (52). Format: YYYYMMDD-HH:MM:SS.uuu
Three byte, simple checksum. See the FIX spec for details.