# 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](https://docs.sportradar.com/uof/data-and-features/messages/amqp-topic-filtering).

### 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**](https://docs.sportradar.com/uof/data-and-features/messages/system/alive)                                       | **Low**  | If not received, something is broken/not working.                                                                                                       |
| [**bet\_cancel**](https://docs.sportradar.com/uof/data-and-features/messages/event/bet-cancel)                             | **High** | Cancel a market due to an error.                                                                                                                        |
| [**bet\_settlement**](https://docs.sportradar.com/uof/data-and-features/messages/event/bet-settlement)                     | **Low**  | Settle/clear bets for the listed markets and outcomes for a particular event.                                                                           |
| [**bet\_stop**](https://docs.sportradar.com/uof/api-and-structure/api/betting-descriptions/betstop-descriptions)           | **High** | Specified group of markets for a specified sport event should all change their market status to either suspended or deactivated.                        |
| [**fixture\_change**](https://docs.sportradar.com/uof/data-and-features/messages/event/fixture-change)                     | **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**](https://docs.sportradar.com/uof/data-and-features/messages/event/odds-change)                           | **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**](https://docs.sportradar.com/uof/data-and-features/messages/event/rollback-bet-settlements) | **Low**  | Undo a previously sent bet settlement that was sent in error.                                                                                           |
| [**rollback\_bet\_cancel**](https://docs.sportradar.com/uof/data-and-features/messages/event/rollback-bet-cancel)          | **Low**  | Undo a bet cancel that was sent by mistake.                                                                                                             |
| [**snapshot\_complete**](https://docs.sportradar.com/uof/data-and-features/messages/system/snapshot-complete)              | **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](https://docs.sportradar.com/uof/data-and-features/messages/event/bet-settlement) first from our live-odds[ producer](https://docs.sportradar.com/uof/introduction/key-concepts/producers), where all outcomes are reported as losses, and a second bet\_settlement from the prematch producer, where all outcomes are reported as voided (refunded).