> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/integration/message-structure/heartbeat.md).

# 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: Under normal conditions, heartbeat messages carry no body (header only). A body is added only when a feed interruption is in effect — see Feed Interruption Indication below.`

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

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

{% endtab %}
{% endtabs %}

### Feed Interruption Indication (FeedInterrupted)

The heartbeat can also tell you when LSports has flagged an active feed interruption for your package.

When an interruption is in effect, the heartbeat message includes an additional `Body` with a `FeedInterrupted` array, currently containing `1`. Outside of an active interruption, the heartbeat keeps its normal header-only form — no `Body` is sent at all.

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

```json
{
  "Header": {
    "Type": 32,
    "MsgGuid": "ef3a5979-46ef-4f94-ae60-90c063ab3440",
    "ServerTimestamp": 1516013721
  },
  "Body": {
    "FeedInterrupted": [1]
  }
}
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
This is an indication only. LSports does not automatically suspend markets or take any other action when this flag is set. Treat it as a signal to check with LSports on the status of your feed.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.