Outbound Data Structures — Event

Queue Configuration

Property	Value
Topic name	{customerPrefix}.event.queue
Description	Messages containing full event details. Upon arrival, it should fully override the existing snapshot after version check.
Routing patterns	customerPrefix - customer unique prefix
Produces	Event

Event Model Structure

Field	Data Type	Description
eventId	string	A unique id for the event.
name	string	A display name for the event.
startTime	string	The event start time in UTC zone. E.g. '2025-05-06T18:00'
sportId	string	Sport id
categoryId	string	The category/competition reference
competitors	Competitor[]	A list of competitors that are involved in this event.
externalIds	EventMapping[]	A possibly empty list of other providers event ids. The list may change at any time as no mapping should be assumed as static not unique. Example providers; Betfair, Sportradar.
status	string	Event status enum. One of: CANCELLED - the game was cancelled; POSTPONED - the game was postponed;
version	long	Version of event. This can be used for deduplication and ordering of updates downstream.

Event Proto

message Event {
  string eventId = 1;
  string name = 2;
  string startTime = 3;
  string categoryId = 4;
  repeated Competitor competitors = 5;
  repeated EventMapping externalIds = 6;
  string status = 7;
  int64 version = 8;
  string sportId = 9;
}

---

Event Mapping Model

Field	Data Type	Description
provider	string	Provider of the id e.g. Betfair
eventId	string	The id of the event for the provider.

Event Mapping Proto

message EventMapping {
  string provider = 1;
  string eventId = 2;
}

---

Competitor / Team Model

Field	Data Type	Description
id	string	Competitor id
shortName	string	Competitor short name e.g. 'ENG'
fullName	string	Competitor full name e.g. 'England'

Competitor Proto

message Competitor {
  string id = 1;
  string shortName = 2;
  string fullName = 3;
}