# RabbitMQ Queue Setup As discussed on the previous article, you will be receiving multiple message types from our Odds Feed and to avoid discrepancies when it comes to which of the messages should be processed first. We recommend this type of setup: Queue Name: **q.uof.\**\ Routing Key: **uof.#.\** *Note: for the value of the \ see* [*Sports*](#sports) *table for the list of sports you want to subscribe. See screenshot for example*

You would need to also create another queue that would able to receive [OnBetStopGlobal](/odds-feed-documentation/odds-feed-integration/message-types/onbetstopglobal.md) and [OnHeartbeat](/odds-feed-documentation/odds-feed-integration/message-types/onheartbeat.md) messages Queue Name: **q.uof.utility**\ Routing Keys: **uof.onbetstopglobal | uof.onheartbeat**

### Sports | Name | Value | | ------ | ------ | | Soccer | soccer | Take note you can use a different queue name, but the important thing here is the routing key it should be the same as the one that we've provided to be able to receive our payload messages. Once the queue has been created, you would need to also create a consumer to be able to ingest the messages that we're passing via the routing keys. --- # 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://flyingcockatoo.gitbook.io/odds-feed-documentation/odds-feed-integration/rabbitmq-queue-setup.md?ask= ``` 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.