> 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/golf/round-details-scenarios/dis-connection-states.md).
# (Dis)connection States
There are three connection statuses for the golf live data:
**Connected**: Connection is healthy, all scoring devices currently scoring that team for that round are fully connected and operational
**Partially Disconnected:** There is an issue with connection on some devices or networks, we cannot be entirely sure that data will come through in a timely manner.
**Disconnected**: All scoring devices are disconnected and we should not expect data for that
## **1. Disconnected**
This packet will be sent to indicate that we are totally disconnected to all devices scoring for a team playing a round. You will only receive this packet once – Assume that the state of the round is disconnected until you receive either a Partially Disconnected or a Connected packet.
### **Response Model**
**Disconnected Object**
| Field Name | Type | Description |
| ---------------- | ------ | -------------------------------------------------------------- |
| timestamp | date | The timestamp of the event, in UTC |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged |
| state | string | The type of state, in this case “Disconnected” |
**Sample Event Packet**
```
{
"eventElementType": "ConnectionStateChanged",
"state": "Disconnected",
"timestamp": "2025-02-20T15:31:10.595Z"
}
```
**2. Partial Disconnection**
This packet will be sent to indicate that there is an issue with connection on some devices or networks and that we cannot be entirely sure that data will come through in a timely manner. You will only receive this packet once – Assume that the state of the round is partially disconnected until you receive either an Disconnected or Connected packet.
### **Response Model**
**Partially Disconnected Object**
```
{
"eventElementType": "ConnectionStateChanged",
"state": "PartiallyDisconnected",
"timestamp": "2025-02-20T15:31:10.595Z"
}
```
## **3. Connected**
This packet will be sent to indicate that we are now connected to all scoring devices via all networks for a team playing a round. It will be issued after a Disconnected packet to indicate connection is now back, or at any time after you have received a Partially Disconnected packet.
### **Response Model**
**Connected Object**
| Field Name | Type | Description |
| ---------------- | ------ | -------------------------------------------------------------- |
| timestamp | date | The timestamp of the event, in UTC |
| eventElementType | string | The type of event, in this case always “ConnectionStateChanged |
| state | string | The type of state, in this case “Connected” |
**Sample Event Packet**
```
{
"eventElementType": "ConnectionStateChanged",
"state": "Connected",
"timestamp": "2025-02-20T15:31:20.539Z"
}
```
## Doc navigation
[← Hole Score Update](/golf/round-details-scenarios/hole-score-update.md)
---
# 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/golf/round-details-scenarios/dis-connection-states.md?ask=&goal=
```
`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.