> 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/soccer-media/stream-endpoints-websocket/live-actions.md).

# Live Actions

The Live Actions websocket contains a live 'stream' of the team and player actions happening within the football match - this will include; goals, cards, shots and more.

You should receive a new update any time a key action is completed and this websocket is crucial for powering live scores and match actions.

The authentication token provided will be required to make a connection to this websocket endpoint.

Once you have the API token, any further data that you send over the connection will be ignored.

N.B – This endpoint sends heartbeats in-between data packets to let you know that it is still connected.

## Endpoint URL

Legacy - wss\://dde-streams.data.imgarena.com/media/soccer/fixtures/{fixtureId}/actions (Decommissioning on 30th Sept 2026)

**NEW -** wss\://dde-streams.data.srarena.io/media/soccer/fixtures/{fixtureId}/actions

N.B. – Please insert the relevant fixtureId returned from the fixtures API endpoint to return you the data. The authentication token provided will be required to make a connection to this websocket endpoint.

## 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. This endpoint sends heartbeats in-between data packets to let you know that it is still connected.

## Polling limits

IMG Arena monitor the incoming traffic from our customers and strive to ensure that traffic is controlled, in-keeping with our guidelines and not unnecessarily excessive. We would suggest a polling rate of 5 requests per second, whilst we strive towards implementing rate limiting.

## Request parameters

There are 2 optional params, that are in common with these Websocket endpoints:<br>

* “speed” - this can be “fast” or “normal”. Default is normal and only applicable for offline matches
* “startPosition” : integer value, default is 0. This is how many events to skip from the beginning of the list of events. e.g. 5 would be start sending events from the 5th event received for that websocket. This is a useful feature if you want to continue without getting all the events again from the beginning when you reconnect

## Action Type & Sub Action Types

The below information details the key fastpath actions and sub action types we will be collecting live and distributing via the live Actions websocket. An action type can be something like a goal, card, dangerous attack. The sub action type gives extra context to that initial action type. i.e. a goal (action type) scored from inside the box (sub action type).\
See [Soccer/Action Types.](/soccer/action-types.md)

## Response Model

This section details and describes the values within the actions payload (replaces the swagger actions websocket doc).\
See [Soccer/Objects/Live Objects](/soccer/objects/live-objects.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/soccer-media/stream-endpoints-websocket/live-actions.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.