From FIXwiki

FIX Message Heartbeat (MsgType=0)

MsgType	FIX Specification	First introduced	Deprecated
MsgType=0	Session messages - Session	FIX.2.7

The Heartbeat monitors the status of the communication link and identifies when the last of a string of messages was not received.

When either end of a FIX connection has not sent any data for HeartBtInt seconds, it will transmit a Heartbeat message. When either end of the connection has not received any data for (HeartBtInt + "some reasonable transmission time") seconds, it will transmit a Test Request message. If there is still no Heartbeat message received after (HeartBtInt + "some reasonable transmission time") seconds then the connection should be considered lost and corrective action be initiated. If HeartBtInt is set to zero then no regular heartbeat messages will be generated. Note that a test request message can still be sent independent of the value of the HeartBtInt, which will force a Heartbeat message.

Heartbeats issued as the result of Test Request must contain the TestReqID transmitted in the Test Request message. This is useful to verify that the Heartbeat is the result of the Test Request and not as the result of a regular timeout.

Message Contents By FIX Version

Notes

Please post comments, clarifications, examples here. Click on the edit button on the right and away you go! 

Don't forget to refer to the FPL Discussion Groups to back up anything you write.
You will often find the authoritative statements on matters of FIX specification interpretation there.
Links from FIXwiki pages to relevant discussions on the FPL site are very valuable.

For example if you were writing a clarification on how to specify the "quantity" of an order in FIX, you might add the
following relevant link, http://www.fixprotocol.org/discuss/read/f5014573, to back up your points.