Skip to main content
The Session protocol assures client identification, sequential request processing, session state control, and the ability to restore the session after downtime.
Client and server use the following administrative/session messages:

Logon (35=A)

The Logon message initiates the connection from the client side and approves the connection if sent by the exchange.

Logout (35=5)

The Logout message initiates or confirms the termination of a FIX session.

Resend Request (35=2)

The Resend Request message can be used to recover an inbound session sequence if a message was missed.

Sequence Reset (35=4)

The Sequence Reset message can be used in two modes:

Reset Mode

  • Reset Mode forces the counterparty to adjust inbound message sequence, GapFillFlag = “N” or omitted.

Fill Gap Mode

  • Fill Gap Mode is used during retransmission of messages missed by a client. Administrative messages and rejected business messages are not to be retransmitted. Instead a Sequence Reset message with GapFillFlag = “Y” must be used.

Test Request (35=1)

Test Request lets you check sequence numbers, or verify the communication line status in conjunction with a Heartbeat message.
Test Request ❮❯ HeartbeatA connection participant receiving a Test Request message must reply with a Heartbeat message and refer to the TestReqID value of the initial message.

Heartbeat (35=0)

Heartbeat confirms the status of a communication line by replying to a Test Request message.

Reject (35=3)

A Reject message is issued by a party if an incoming FIX message is unsupported or not property formed. Rejected messages must not be resent if a Resend Request is received; instead a SequenceReset with GapFillFlag = “Y” is expected.