> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/imga-dl-trading-odds-distribution/odds-distribution-service/heartbeats.md).

# Heartbeats

Clients will receive regular heartbeats once connected. Heartbeats will come every 3 seconds. If the last heartbeat received by a client was more than 10 seconds ago, the client should assume that there is either a network problem or they are lagging behind in processing messages. The client should suspend all markets which it is receiving from the feed until it receives another heartbeat message. Additionally, if no messages at all have been received in a 10 second period, the client should assume there is a network problem, disconnect from the feed and attempt to open a new connection.

Below is an example of a heartbeat message::

```
{
  "mode": "push",
  "publish_time": "2025-03-20 10:05:18.924114",
  "type": "heartbeat",
  "msg": {
    "timestamp": "2025-03-20 10:05:18.924114"
  }
}
```


---

# 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 dynamically by asking a question.

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

```
GET https://docs.sportradar.com/imga-dl-trading-odds-distribution/odds-distribution-service/heartbeats.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.