# RabbitMQ Header

RabbitMQ headers include key metadata fields designed to provide essential context for each message, enabling clients to perform efficient routing, filtering, and logging without the need to deserialize the full message payload.

### **Model**

| **Element**       | **Data Type** | **Description**                                                                                                                                                                                            |
| ----------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MessageGuid       | string        | Unique identifier for the message                                                                                                                                                                          |
| MessageType       | string        | Type/category of the message                                                                                                                                                                               |
| FixtureId         | string        | Unique identifier for the fixture. Not avaliable for [Keep Alive (31)](/u/trade/integration/message-structure/keep-alive.md) and [Heartbeat (31)](/u/trade/integration/message-structure/heartbeat.md).    |
| MessageSequence   | string        | Sequence number for message ordering. Not avaliable for [Keep Alive (31)](/u/trade/integration/message-structure/keep-alive.md) and [Heartbeat (31)](/u/trade/integration/message-structure/heartbeat.md). |
| timestamp\_in\_ms | string        | Time when the message is distributed to your RMQ                                                                                                                                                           |
| SportId           | string        | Unique identifier for the sport. Not available for [Keep Alive (31)](/u/trade/integration/message-structure/keep-alive.md) and [Heartbeat (32)](/u/trade/integration/message-structure/heartbeat.md).      |

**Usage Recommendation**

* **Faster Routing:** Use `MessageType`, `FixtureId`, and `SportId` in the header to direct messages to the appropriate consumer or handler before deserializing the payload.
* **Efficient Filtering:** Filter and partition messages at the broker or consumer level using header values, reducing unnecessary processing.
* **Improved Traceability:** Leverage `MessageGuid` and `MessageSequence` for logging, debugging, and tracing message flows.


---

# 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.lsports.eu/u/trade/integration/message-structure/rabbitmq-header.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.