> 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/protocol.md).

# Protocol

Communication with the IMG Arena odds distribution service involves a bidirectional stream of JSON messages, encoded as UTF-8, sent over SSH.

Example requests and responses in this documentation are pretty-printed in places for clarity. On the feed itself, JSON objects sent in either direction must not contain newlines but are terminated with a single newline character (ASCII char 10 or 0x0A).

There are two situations in which the server will send data to the client. One is that the client has made a request of some sort, in which case the server will send back response consisting of a JSON object containing a top-level key-value pair:

```
{ "mode": "resp", ... }
```

We refer to these as “Response” messages. The second situation is that the server just needs to push some data, such as a price change, to the client. In this case, the JSON object will contain top-level key-value pair:

```
{ "mode": "push", ... }
```

These are “Push” messages and may be sent by the server at any time after the initial login and registration requests are received and their responses sent, but never before.

Client requests will always receive a corresponding response message, but there may be Push messages sent in between the client sending the request and receiving the response, especially in the case where the client has subscribed to a data feed.


---

# 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/protocol.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.