Message Structure

This section documents the complete structure of all message types delivered through the TRADE RabbitMQ feed.

Overview

TRADE sends data in structured messages, each with a specific type identifier. Messages are delivered in either JSON or XML format based on your package configuration.

Message Categories

Standard Messages

Message Type	Type ID	Description
Fixture	1	Fixture metadata updates
Livescore	2	Live score and period updates
Market	3	Odds and market updates
Settlement	35	Bet settlement information
Heartbeat	32	Connection health indicator
Keep Alive	-	Active fixtures list

Outright Messages

Message Type	Type ID	Description
Outright Fixture	37	Outright event metadata
Outright Livescore	-	Outright live updates
Outright Market	39	Outright odds updates
Outright Settlement	-	Outright settlements

Outright League Messages

Message Type	Type ID	Description
Outright League Fixture	45	League outright metadata
Outright League Market	47	League outright odds
Outright League Settlement	-	League outright settlements

Message Headers

All messages contain headers with routing and metadata information:

• RabbitMQ Header - Transport-level headers

• TRADE Message Header - Application-level headers

New: RabbitMQ headers now include SportId, allowing you to route or filter messages by sport without deserializing the message body. Available on all message types except Keep Alive and Heartbeat.

Message Format

Messages follow a consistent structure:

{
  "Header": {
    "Type": 3,
    "MsgSeq": 12345,
    "MsgGuid": "uuid-here",
    "ServerTimestamp": 1234567890
  },
  "Body": {
    // Message-specific content
  }
}

Additional Resources

• Message Types Overview - Complete type reference

• Example Messages - Sample messages by sport