Livescore
The livescore element holds all scores and statistics:
<Livescore>
<Scoreboard Status="2" Description="0" CurrentPeriod="10" Time="0">
<Clock Status="1" Seconds="60" />
<Results>
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Results>
</Scoreboard>
<Periods>
<Period Type="10" IsFinished="false" IsConfirmed="false">
<Results>
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Results>
<Incidents>
<Incident Period="10" IncidentType="9" Seconds="0" ParticipantPosition="2" PlayerId="">
<Results>
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Results>
</Incident>
</Incidents>
</Period>
</Periods>
<Statistics />
<PlayerStatistics>
<PlayerStatistic PlayerId="12345" PlayerName="Lionel Messi" TeamId="780" HasPlayed="true">
<Statistics>
<Statistic Id="1" Name="Goals" Value="2" />
<Statistic Id="2" Name="Assists" Value="1" />
</Statistics>
</PlayerStatistic>
<PlayerStatistic PlayerId="67890" PlayerName="Cristiano Ronaldo" TeamId="786" HasPlayed="true">
<Statistics>
<Statistic Id="1" Name="Goals" Value="1" />
<Statistic Id="3" Name="Shots" Value="5" />
</Statistics>
</PlayerStatistic>
</PlayerStatistics>
<Statistics>
<Statistic Type="1">
<Value Position="1">5</Value>
<Value Position="2">6</Value>
<Incidents>
<Incident Period="10" IncidentType="1" Seconds="613" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Incident>
<Incident Period="10" IncidentType="1" Seconds="1489" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">0</Score>
<Score Position="2">2</Score>
</Incident>
<Incident Period="10" IncidentType="1" Seconds="1925" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">2</Score>
</Incident>
<Incident Period="10" IncidentType="1" Seconds="2041" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">3</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="3096" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">4</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="3183" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">2</Score>
<Score Position="2">4</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="3228" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">3</Score>
<Score Position="2">4</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="3855" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">3</Score>
<Score Position="2">5</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="3913" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">3</Score>
<Score Position="2">6</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="4587" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">4</Score>
<Score Position="2">6</Score>
</Incident>
<Incident Period="20" IncidentType="1" Seconds="4617" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">5</Score>
<Score Position="2">6</Score>
</Incident>
</Incidents>
</Statistic>
<Statistic Type="4">
<Value Position="1">106</Value>
<Value Position="2">91</Value>
</Statistic>
<Statistic Type="5">
<Value Position="1">79</Value>
<Value Position="2">78</Value>
</Statistic>
<Statistic Type="6">
<Value Position="1">2</Value>
<Value Position="2">1</Value>
<Incidents>
<Incident Period="10" IncidentType="6" Seconds="174" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Incident>
<Incident Period="20" IncidentType="6" Seconds="4271" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">1</Score>
</Incident>
<Incident Period="20" IncidentType="6" Seconds="5710" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">2</Score>
<Score Position="2">1</Score>
</Incident>
</Incidents>
</Statistic>
<Statistic Type="7">
<Value Position="1">0</Value>
<Value Position="2">0</Value>
</Statistic>
<Statistic Type="8">
<Value Position="1">0</Value>
<Value Position="2">0</Value>
</Statistic>
<Statistic Type="12">
<Value Position="1">9</Value>
<Value Position="2">7</Value>
</Statistic>
<Statistic Type="16">
<Value Position="1">0</Value>
<Value Position="2">0</Value>
</Statistic>
<Statistic Type="18">
<Value Position="1">0</Value>
<Value Position="2">0</Value>
</Statistic>
<Statistic Type="27">
<Value Position="1">2</Value>
<Value Position="2">2</Value>
<Incidents>
<Incident Period="20" IncidentType="27" Seconds="3965" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">0</Score>
<Score Position="2">1</Score>
</Incident>
<Incident Period="20" IncidentType="27" Seconds="4668" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">1</Score>
</Incident>
<Incident Period="20" IncidentType="27" Seconds="4959" ParticipantPosition="2" PlayerId="-1">
<Score Position="1">1</Score>
<Score Position="2">2</Score>
</Incident>
<Incident Period="20" IncidentType="27" Seconds="5580" ParticipantPosition="1" PlayerId="-1">
<Score Position="1">2</Score>
<Score Position="2">2</Score>
</Incident>
</Incidents>
</Statistic>
<Statistic Type="2005">
<Value Position="1">4</Value>
<Value Position="2">4</Value>
</Statistic>
<Statistic Type="2006">
<Value Position="1">6</Value>
<Value Position="2">6</Value>
</Statistic>
</Statistics>
<LivescoreExtraData />
<CurrentIncident>
<Id>5</Id>
<Name>DangerousAttacks</Name>
<LastUpdate>2025-02-03T15:54:38.6207474</LastUpdate>
</CurrentIncident>
<DangerTriggers>
<DangerTrigger>
<Type>1</Type>
<Status>1</Status>
<LastUpdate>2025-02-03T15:31:15.1049535</LastUpdate>
</DangerTrigger>
<DangerTrigger>
<Type>2</Type>
<Status>1</Status>
<LastUpdate>2025-02-03T15:31:15.104986</LastUpdate>
</DangerTrigger>
<DangerTrigger>
<Type>3</Type>
<Status>1</Status>
<LastUpdate>2025-02-03T15:31:15.1050175</LastUpdate>
</DangerTrigger>
</DangerTriggers>
</Livescore>Scoreboard Model
Attributes
Data Type
Description
CurrentPeriod
int
The current period or stage of the match.
Time
string
The time elapsed in the current period or stage of the match. Represented in seconds. *Will be depricated
Results
Array
An array containing results specific to the match
Clock
Object
Contains detailed match timing informatio
Results Model
Attributes
Data Type
Description
Position
string
The position or team identifier associated with the result. In 2-participant events, the positions will be 1 (home) or 2 (away) For outright events, the positions will represent the initial position of the participant
Value
string
The value or score associated with the respective position or team.
Clock Model
Attributes
Data Type
Description
Status
int
0 = Stopped, 1 = Running
Seconds
int
The time elapsed in the current period or stage of the match.
Represented in seconds. Available based on LSports’ coverage
PlayerStatistics Model
Attributes
Data Type
Description
PlayerId
int
Unique identifier for the player.
PlayerName
string
Name of the player.
ParticipantId
int
Identifier for the team to which the player belongs.
HasPlayed
boolean
Indicates whether the player participated in the event.
Statistics
array
List of player-related statistics.
Statistics Model
Attributes
Data Type
Description
Name
String
Name of the statistic
Value
int
The value of the statistic
Periods Model
Attributes
Data Type
Description
enum
The type of the period. Describe the nature of the period within the context of the sport (e.g., first half, second half).
IsFinished
bool
Indicates whether the period is finished or not
IsConfirmed
bool
Indicates whether the period and its scores are confirmed
Periods.Results
Array
An array containing period-specific results.
SubPeriods
Array
Relevant for tennis only, subperiod is the game inside a set.
SequenceNumber
int
A sequence number assigned to the period for ordering purposes.
Incidents
Array
An array of incidents related to this period.
Note: Delivering the IsFinished as true and the IsConfirmed as false means we couldn't validate the final result of the specific period
Incident Model
Every period element may contain a list of incidents (e.g. goals that were scored). Incidents will appear as long as we have the information.
Note: Incidents may be sent after a final status had been received.
Attributes
Data Type
Description
Period
enum
The type of period, in which the incident had occurred
Seconds
bool
Time of incident occurrence
ParticipantPosition
int
In 2-participant events, the positions will be 1 (home) or 2 (away) For outright events, the positions will represent the initial position of the participant
PlayerId
Int
The unique identifier of the player responsible for the incident
PlayerName
string
The name of the player responsible for the incident
Incident.Results
Array
An array containing results specific to the incident
For Cricket Only - SubPeriods represent the number of Runs made within the last Over in addition the number of Overs played so far will be shown under SequenceNumber - as can be seen in the following example Here Note: SequanceNumber is only relevant for Cricket at the moment.
Statistics Model
Attributes
Data Type
Description
Statistics.Results
enum
An array containing statistical results categorized by the type.
Incidents
Array
An array of incidents related to
this statistic type
Current Incident Model
The Current Incident provides context on what triggered the Danger Indicator to include the ID and the name of the incident that triggered it.
Attributes
Data Type
Description
Name
enum
Description of the incident (e.g., Yellow Card).
LastUpdate
Timestamp
The time when the incident occurred.
Danger Trigger Model
The Danger Trigger Model provides real-time safety status updates for specific market types, ensuring proactive risk management.
For full coverage and functionality, please refer to the detailed documentation.
Attributes
Data Type
Description
Type
enum
Market type: General (1), Cards (2), Corners (3).
Status
enum
Current market status: Safe (1), Dangerous (2).
LastUpdate
Timestamp
The latest update time for market safety indicators.
Note: To enable DangerTrigger please reach out to support or your CSM.
Livescore important notes
PreMatch package subscribers will only receive the final Live Score after the fixture has ended. Real-time LiveScore updates during an event are exclusive to InPlay package subscribers.
Periods, scores, statistics, and time MAY be reverted due to mistakes made by the data providers.
The current total score of the event can be found under the Scoreboard element. The score for every individual period can be found within the Period elements.
Note: Every period contains the score relevant to that period aloneAs a part of our data quality improvement, new periods and statistical types may be added all the time. Make sure your system is dynamic enough to cope with unidentified types.
A loss of coverage will occur if we are not able to provide data for an event due to technical difficulties or faulty data.
Note: Should a loss of coverage occur – all bets will be suspended.There are several events where we offer live up to 30 minutes before the event’s actual start time. Those events will be sent with the status “9”, which indicates that the event is about to start. The status is the attribute of the Scoreboard element.
The period type “80” stands for “BreakTime”. This period applies to ANY break during the live event. The type of the break will be in the Description attribute of the Scoreboard element, as seen below:
<Scoreboard Status="2" CurrentPeriod="80" Description=”1” Time="2700">
<Score Position="1">2</Score>
<Score Position="2">1</Score>
</Scoreboard>Football
Time
Time direction will be ascending until the end of the half.
During halftime, the time will always be 2700 seconds.
During overtime halftime, the time will always be 6300 seconds.
When the event is finished (without overtime), the time will always be 5400 seconds.
When the event is finished (after overtime), the time will always be 7200 seconds.
During penalties, there will be no time available.
Basketball
Time
Time direction will always be descending.
At the end of every period, the time will be set to 0.
Periods
During NCAA events (College male basketball), the periods will show as halves (10 – 1st Half, 20 – 2nd Half) instead of quarters as usual.
Tennis
Periods
When the Tennis match is finished, the period “60” (Game period) will be removed as it is no longer relevant.
The serving player will appear under the ExtraData element, within the “Turn” key. The possible values are 1 or 2 (according to the participant's position).
Last updated
Was this helpful?