# Heartbeat

### RMQ HeartBeat message (type 32)

This is an actual data message sent by LSports through the RabbitMQ feed every 5 seconds. Its purpose is to indicate that the data feed is alive and operational.

The message has a specific structure, typically containing only a header with fields like Type (set to 32), `MsgGuid`, and `ServerTimestamp`.

You can use the presence (or absence) of these messages to monitor the health of your data feed and take action if they stop arriving.

`Note: Heartbeat messages are without Body (only Header)`

{% tabs %}
{% tab title="JSON" %}

```json
{
   "Message": {
      "Header": {
         "Type": "32",
         "MsgGuid": "ef3a5979-46ef-4f94-ae60-90c063ab3440",
         "ServerTimestamp": "1516013721"
      }
   }
}
```

{% endtab %}

{% tab title="XML" %}

```xml
<Message>
  <Header>
    <Type>32</Type>
    <MsgGuid>ef3a5979-46ef-4f94-ae60-90c063ab3440</MsgGuid>
    <ServerTimestamp>1516013721</ServerTimestamp>
  </Header>
</Message>
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lsports.eu/u/trade/integration/message-structure/heartbeat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.