Scoreboards
Bowling Scoreboards
Bowling scoreboards can be divided into S1
, S2
, S3
, S4
(S3 and S4 only for test matches). They can be added to any fixtures related response by adding &include=bowling
to your request url. A. bowling record will contains data bout runs
, wickets
, overs
, player
, team
and much more.
You can request all the bowling scoreboards we have on a fixture or livescores endpoint. For example:
Batting Scoreboards
Batting scoreboards can be divided into S1
, S2
, S3
, S4
(S3 and S4 only for test matches). They can be added to any fixtures related response by adding &include=batting
to your request url. A. bowling record will contains data bout fout_x
, six_x
, score
, ball
, player
, team
and much more.
You can request all the batting scoreboards we have on a fixture or livescores endpoint. For example:
Runs
Runs basically are an aggregated/calculated total of an inning of the game. The inning
property equals the scoreboard
property on bowling
and batting
data.
You can request all the runs we have on a fixture or livescores endpoint. For example:
Line-ups
The lineup
include represent an array of player that playing the game for both away and home team. We provide information about the players as well as information captain
and wicketkeeper
.
You can request all the lineups we have on a fixture or livescores endpoint:
Ball by Ball
To follow a game Ball By Ball you can easily include balls
to your fixture or livescores related request. As you can see below it will only return id so to gain more information you can use nested includes to enrich the dataset.
You can request all the ball by ball information we have on a fixture or livescores endpoint:
Last updated