Sport Event Information

Sport Event

A Sport event is a match/race/competition. Every message contains information about exactly one Sport event. So for example, an odds change message typically includes odds changes to any markets for a particular match (Sports event).

Example Odds change message (XML example)

<odds_change product="1" event_id="sr:match:14011583" timestamp="1522772129383">
  <sport_event_status status="0" match_status="0"/>
  <odds>
.... Info about markets....
 </odds>
</odds_change>

Sport Event Information

All sport events have a unique ID. This unique ID is how the Sport Event is identified in the messages. The API then provides endpoints that allow you to look up fixture information for a given SportsEvent ID.

AMQP messages contain basic information about an event like event IDs, event status, market odds and probabilities, whereas additional information can be obtained from the API. The complete information about a sport event can only be tapped by using AMQP message data and API information.

API

• Fixture info : Date, Time, Venue

• Info about competitors

• Extra info : Period length, overtime length, neutral ground

AMQP

• Event ID, Event status, Product ID,

• Markets identifiers (ID, type, specifier) with outcomes, odds, and probabilities

• Results

UOF ID / URN

UOF introduces a new format of sport event IDs which is called URN. This is nothing but event_id

URN has three components: a prefix, sport event type, and the actual sport event ID separated by a colon.

• Prefix can be : sr, wns, vf, vbl, etc

• Sport event types can be sport, category, tournament, simple_tournament, season, stage, match, competitor, player, venue, etc

• Sport event ID is a long integer that is assigned to that particular sports event.

Syntax

[ prefix ] : [ sport event type ] : [ sport event ID ]

For example, sr:match:8412480 where sr is the prefix, match is the sport event type, and 8412480 is the sport event ID.

In order to prevent any confusion, URN should always be treated as a whole, as IDs might overlap over various sport event types.

Sport_event statuses

Event Status

The status specifies the current status of the sport event. This is made available in the AMQP messages for a given event in the attribute

• 0 = not_started – The match is scheduled to be played

• 1 = live – The match is currently in progress

• 2 = suspended - The match has been suspended

• 3 = ended – The match is over

• 4 = closed – The match results have been confirmed

Example XML

<sport_event_status status="0" match_status="0"/>

match_status

This is Sports-specific integer code the represents the live match status i.e. what period or break the match is currently in (first period, 2nd break,etc.)

See the API endpoint descriptions/(lang)/match_status.xml for a mapping of these codes to translatable human-readable text in the languages Betradar supports.