Cricket API – Super Overs Support
We've added an innings_type attribute to our Cricket API to explicitly identify Super Over innings.
Previously, when a limited-overs match went to a Super Over, the Super Over innings arrived as plain innings 3 and 4 with no flag identifying them, and allotted_overs carried the full-match value (20). Integrators had to infer the Super Over from the innings number. innings_type now carries this signal directly, and allotted_overs is set to 1 on Super Over innings to reflect the actual over allocation.
| Value | Meaning |
|---|---|
regular | A regular innings |
super_over | A Super Over tie-breaking innings |
innings_type is available in four places:
sport_event_status.period_scores[].innings_typestatistics.innings[].innings_typetimeline[].innings_type— present on everyperiod_startevent, identifying which innings the event belongs tosport_event_status.allotted_oversis set to1while a Super Over innings is in progress. Once the match is closed, this attribute reflects the match-level overs allocation (20in a T20); per-innings Super Over values remain1inperiod_scores[].
Values are available live from the innings start and are retained in the final match state.
⭐ Benefit
Reliably identify Super Over innings directly from the feed instead of inferring them from the innings number, and render the correct overs allocation (1, not 20) on tie-breaking Super Over play. Scoreboards, standings, and innings-level statistics line up with the actual match structure — both live and in the final state.
📋 Recommended Actions
- Read
innings_typefromperiod_scores[],statistics.innings[], and theperiod_starttimeline event on each innings. - Treat
innings_type="super_over"as the authoritative Super Over signal. Stop inferring Super Overs from the innings number (e.g. "innings > 2") — that heuristic no longer needs to exist in your integration. - Use
allotted_overs="1"on Super Over innings when rendering overs allocation, overs remaining, or run-rate denominators. The value is also reflected onsport_event_status.allotted_overswhile a Super Over innings is current. - Existing innings carry
innings_type="regular". If your integration ignores unknown attributes safely, no change is required to continue consuming regular innings.
🔢 Products
| Sport | Product | Version(s) |
|---|---|---|
| Cricket | Cricket API | v2 |
🔁 Endpoints Affected
Match feeds: Match Summary, Match Timeline, Match Timeline Delta
Any additional feed that embeds sport_event_status.period_scores[] (Daily Results, Team Results, Team vs Team, Tournament Results) will also carry innings_type on each period score.
☑️ Sample Request:
Match Timeline — IPL 2026 M38, LSG vs KKR (sr:match:70343160)
curl --request GET \
--url https://api.sportradar.com/cricket-t2/en/matches/sr:match:70343160/timeline.json \
--header 'accept: application/json' \
--header 'x-api-key: YOUR_API_KEY'⚙️ Return Samples
<sport_event_status match_status="ended" status="closed" display_score="4/0" winner_id="sr:competitor:152326" toss_won_by="sr:competitor:877929" toss_decision="bowl" current_inning="4" display_overs="0.1" required_run_rate="0" run_rate="24" allotted_overs="20">
<period_scores>
<period_score home_score="0" away_score="155" type="inning" number="1" innings_type="regular" allotted_overs="20" display_overs="20" away_wickets="7" display_score="155/7"/>
<period_score home_score="155" away_score="0" type="inning" number="2" innings_type="regular" allotted_overs="20" display_overs="20" home_wickets="8" display_score="155/8"/>
<period_score home_score="1" away_score="0" type="inning" number="3" innings_type="super_over" allotted_overs="1" home_wickets="2" display_score="1/2"/>
<period_score home_score="0" away_score="4" type="inning" number="4" innings_type="super_over" allotted_overs="1" display_score="4/0"/>
</period_scores>
</sport_event_status><event id="2341486640" type="period_start" time="2026-04-26T18:08:29+00:00" period_name="Third innings, home team" innings_type="super_over"/>{
"number": 3,
"innings_type": "super_over",
"batting_team": "sr:competitor:877929",
"bowling_team": "sr:competitor:152326",
"teams": [
{
"id": "sr:competitor:152326",
"name": "Kolkata Knight Riders",
"abbreviation": "KKR",
"statistics": {
"bowling": {
"bowling_spells": [
{
"spell_order": 1,
"start": 0.1,
"start_time": "2026-04-26T18:05:44.807Z",
"conceded_runs": 1,
"dot_balls": 2,
"economy_rate": 2,
"maidens": 0,
"no_balls": 0,
"overs_bowled": 0.3,
"wickets": 2,
"wides": 0,
"player": {
"id": "sr:player:637820",
"name": "Sunil Philip Narine"
}
}
]
...
}
}
}
]
...
}