> 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/ufc-media/stream-endpoints-websocket/fight-details.md).
# Fight Details
This web socket endpoint returns the event-by-event data per fight. Once a fight commences the live information will visible and you'll be able to view the live fight details.
## **Endpoint URL**
| Legacy - `wss://dde-streams.data.imgarena.com/media/mma/fights/{id}/details` (decommissioning on 30th Sept 2026) |
| ---------------------------------------------------------------------------------------------------------------- |
| **NEW** - `wss://dde-streams.data.srarena.io/media/mma/fights/{id}/details` |
**Process for connecting to the web socket endpoints**
* Connect to SSL websocket address
* Send JSON packet containing API token
* Receive response indicating that connection is authorised (or a response indicating why the connection cannot be made)
* Receive heartbeat packets every 10 seconds to verify the connection is live
* Receive data packets
Once you have the API token, any further data that you send over the connection will be ignored.
## Request Parameters
| **Parameter** | **Type** | **Purpose** |
| ------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| startPosition | integer | The position in the stream that you want to start from.
Each packet in the stream has a sequence number ('seqNum'), where 1 is the first packet in the stream. By default the stream will start from the beginning.
This is useful if you get disconnected from a stream and need to reconnect. When reconnecting, if you specify the seqNum of the last packet you received + 1, then you can pick up where you left off without need to reprocess all the events already received.
|
## Response Model
There are a number of different types of packets that can be sent through this endpoint. They are detailed in the [Fight Details Scenarios](https://img-arena.gitbook.io/mma/-M0NiZjZYQq5xFpHxi-5/fight-details-scenarios) section of this documentation.
| **Field Name** | **Type** | **Description** |
| ---------------- | -------- | --------------------------------------------- |
| stats | object | information of the fight |
| roundNum | object | number of rounds |
| timestamp | string | Date and time |
| roundTime | string | Time of each round |
| eventElementType | string | Status update of the fight |
| seqNum | integer | The sequence number of the packet in the feed |
| fightStatus | string | status of the round/fight |
## **Stats Object**
| **Field Name** | **Type** | **Description** |
| -------------- | -------- | --------------------------- |
| Fight | object | information about the fight |
| Round | object | information about the round |
## **Fight object**
| **Field Name** | **Type** | **Description** |
| ----------------- | -------- | ----------------------------- |
| red/blue | integer | fighter colour/class |
| takedownAttempt | integer | number of takedown attempts |
| submissionAttempt | integer | number of submission attempts |
| takedownLanded | integer | number of landed takedowns |
| knockdown | integer | number of knockdown |
| reversal | integer | number of reversals |
## **Round object**
stats broken down per round
| Field Name | Type | Description |
|---|
| Field Name | Type | Description |
| red/blue | integer | fighter colour/class |
| takedownAttempt | integer | number of takedown attempts |
| submissionAttempt | integer | number of submission attempts |
| takedownLanded | integer | number of landed takedowns |
| knockdown | integer | number of knockdown |
| reversal | integer | number of reversals |
## **Sample Websocket**
You can connect to a sample WS for fight details here:
| wss\://dde-streams.data.imgarena.com/media/mma/fights/999991/details |
| -------------------------------------------------------------------- |
---
# 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.sportradar.com/ufc-media/stream-endpoints-websocket/fight-details.md?ask=&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.