# Messages

Messages in the Unified Feed are sent to various topics, allowing for easy and flexible filtering through the message queue (AMQP).\
You can find a complete list of message types provided by Betradar producers in the Unified Feed. Learn more about our **messaging system and AMQP integration** in our [detailed documentation](/uof/data-and-features/messages/amqp-topic-filtering.md).

### Basic message configuration <a href="#uofmessages-basicmessageconfiguration" id="uofmessages-basicmessageconfiguration"></a>

| **AMQP server**  | [mq.betradar.com](http://mq.betradar.com/)                                                                                                                            |
| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **AMQP port**    | 5671 (standard SSL for AMQP)                                                                                                                                          |
| **Virtual host** | `/unifiedfeed/<bookmaker_id>` (where \<bookmaker\_id> is your bookmaker id (see `users/whoami.xml` endpoint for how to find your bookmaker\_id if you are uncertain)) |
| **Exchange**     | unifiedfeed                                                                                                                                                           |
| **Username**     | \<your\_security\_access\_token>                                                                                                                                      |
| **Password**     | \<blank>                                                                                                                                                              |
| **Queue**        | You cannot create your own queues. Instead you have to request a server-named queue (empty queue name in the request). Passive, Exclusive, Non-durable.               |
| **Version**      | AMQP 0.9.1                                                                                                                                                            |

### Message types  <a href="#uofmessages-messagetypes" id="uofmessages-messagetypes"></a>

Here you will find more details about each individual message types available in Unified Feed.

| Name                                                                                               | Priority | Description                                                                                                                                             |
| -------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**alive**](/uof/data-and-features/messages/system/alive.md)                                       | **Low**  | If not received, something is broken/not working.                                                                                                       |
| [**bet\_cancel**](/uof/data-and-features/messages/event/bet-cancel.md)                             | **High** | Cancel a market due to an error.                                                                                                                        |
| [**bet\_settlement**](/uof/data-and-features/messages/event/bet-settlement.md)                     | **Low**  | Settle/clear bets for the listed markets and outcomes for a particular event.                                                                           |
| [**bet\_stop**](/uof/api-and-structure/api/betting-descriptions/betstop-descriptions.md)           | **High** | Specified group of markets for a specified sport event should all change their market status to either suspended or deactivated.                        |
| [**fixture\_change**](/uof/data-and-features/messages/event/fixture-change.md)                     | **High** | Sent when an important fixture change has happened (typically some near-term change, such as a new event or a change to an event (e.g. delayed match)). |
| [**odds\_change**](/uof/data-and-features/messages/event/odds-change.md)                           | **High** | Lists odds changes for some or all markets for a match and signal bet stop for the whole match, individual markets, or outcomes.                        |
| [**rollback\_bet\_settlement**](/uof/data-and-features/messages/event/rollback-bet-settlements.md) | **Low**  | Undo a previously sent bet settlement that was sent in error.                                                                                           |
| [**rollback\_bet\_cancel**](/uof/data-and-features/messages/event/rollback-bet-cancel.md)          | **Low**  | Undo a bet cancel that was sent by mistake.                                                                                                             |
| [**snapshot\_complete**](/uof/data-and-features/messages/system/snapshot-complete.md)              | **None** | Sent after all odds updates from a recovery API request has been sent                                                                                   |

### Special message cases  <a href="#uofmessages-specialmessagecases" id="uofmessages-specialmessagecases"></a>

**Bet settlements for another outcome for correct score markets**

Some correct score markets have limited outcomes. If the actual correct score is something different than the outcomes that were offered, there is a choice:

* The bets placed can be considered lost
* The bets placed can be refunded (as the winning outcome wasn’t offered).

Betradar intends this to be a configuration option going forward. As it is currently: You will receive a [bet\_settlement](/uof/data-and-features/messages/event/bet-settlement.md) first from our live-odds[ producer](/uof/introduction/key-concepts/producers.md), where all outcomes are reported as losses, and a second bet\_settlement from the prematch producer, where all outcomes are reported as voided (refunded).


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/uof/data-and-features/messages.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.