> 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/pfl/fight-details-scenarios/connection-statuses.md).

# Connection Statuses

## Types

There are four connection statuses for MMA Fight Details:

**Connected**: Connection is healthy, our onsite team have no issues and are delivering data at the lowest latency (\~2/3s from real time)

**Disconnected**: We are disconnected to our onsite team however there is an issue with the data being sent to us in real time – data will not be coming through until connection is re-established.

**Market closed:** Indication from the data collectors that they are having issues collecting data and you should suspend markets.

**Market open:** Indication from the data collectors that on-site issues have been resloved and you can enable markets.

## **1. Disconnected**

This packet will be sent to indicate that we are totally disconnected to our onsite team. You will only receive this packet once – Assume that the state of the round is disconnected until you receive another “ConnectionStateChanged” 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-09-04T11:19:45.700Z"
}
```

## **2. Connected**

This packet will be sent to indicate that we are connected to our onsite team. You will only receive this packet once – Assume that the state of the round is connected until you receive another “ConnectionStateChanged” packet.

### **Respo**n**se 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-09-04T11:21:55.977Z"
}
```

## **3. Market closed**

### **Respo**n**se Model**

#### **MarketClose Object**

| Field Name       | Type    | Description                                         |
| ---------------- | ------- | --------------------------------------------------- |
| timestamp        | date    | The timestamp of the event, in UTC                  |
| eventElementType | string  | The type of event, in this case always “MarketOpen” |
| SeqNum           | integer | Seq number of the packet                            |

```
{
  "eventElementType": "MarketClose",
  "seqNum": 16,
  "timestamp": "2025-11-19T10:28:22.828916500Z"
}
```

## **4. Market Open**

### **Respo**n**se Model**

#### **MarketOpen Object**

| Field Name       | Type    | Description                                         |
| ---------------- | ------- | --------------------------------------------------- |
| timestamp        | date    | The timestamp of the event, in UTC                  |
| eventElementType | string  | The type of event, in this case always “MarketOpen” |
| SeqNum           | integer | Seq number of the packet                            |

```
{
  "eventElementType": "MarketOpen",
  "seqNum": 17,
  "timestamp": "2025-11-19T10:29:07.534412Z"
}
```


---

# 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/pfl/fight-details-scenarios/connection-statuses.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.