International and domestic cricket in one uniform JSON. Innings scores, batting and bowling cards, both XIs, every delivery and the venue, from Test matches to T20 leagues.
Tom Latham (c) not out
65986066.33
Devon Conway not out
6511011059.09
{
"data": {
"id": 67365,
"league_id": 111,
"season_id": 1682,
"round": "New Zealand tour of England, 3rd Test",
"localteam_id": 38,
"visitorteam_id": 42,
"starting_at": "2026-06-25T10:00:00.000000Z",
"type": "Test/5day",
"live": true,
"status": "1st Innings",
"note": "Day 1 - Session 2",
"toss_won_team_id": 42,
"elected": "batting",
"runs": [
{ "team_id": 42, "inning": 1, "score": 135, "wickets": 0, "overs": 34.2 }
],
"batting": [
{ "player_id": 205, "score": 65, "ball": 98, "four_x": 6, "six_x": 0 }, /* Tom Latham */
{ "player_id": 4817, "score": 65, "ball": 110, "four_x": 11, "six_x": 0 } /* Devon Conway */
],
"bowling": [
{ "player_id": 5177, "overs": 8, "medians": 0, "runs": 28, "wickets": 0, "rate": 3.5 },
{ "player_id": 424, "overs": 4.2, "medians": 0, "runs": 15, "wickets": 0, "noball": 1 }
// + Tongue, Bashir and Stokes
],
"lineup": [
{ "id": 205, "fullname": "Tom Latham",
"lineup": { "team_id": 42, "captain": true } }
// + 21 more players, both XIs, each with image_path
],
"balls": [
{ "ball": 34.2, "bowler_id": 424, "batsman_id": 4817,
"score": { "name": "No Run", "runs": 0, "is_wicket": false } }
// + 207 more deliveries, back to ball 0.1
],
"venue": { "name": "Trent Bridge", "city": "Nottingham", "capacity": 17000 }
}
}
"The speed, depth, and flexibility to create a world-class cricket app."
A real-time cricket app built on livescores, ball-by-ball, player and team stats, fixtures and fantasy data.


Case study
"The quality of the data itself stands out."
Once you start utilising it, you realise its excellence isn't just superficial.

Case study
"Data reliability has been constantly improving."
I particularly highlight the support team's agility and efficiency in resolving any issues.


Case study
"Sportmonks has proven to be a great partner."
Finding high-quality data is challenging. When available, it's often too expensive or hard to integrate.

Case study
"A clean, stable framework we can build on."
No worrying about inconsistent naming or missing relationships.
Case study
"Seven years. No major problems."
Other services provided the same data at much higher prices that we could not afford.
Case study
"Automated sports media at scale."
Player and schedule data that used to be entered by hand, per club.
"Sportmonks feels like a partner rather than just a service."
The support team is fast, helpful, and actually understands what you're trying to achieve.
Case study
"AI match commentary in 12+ languages."
Botbrains scales generative commentary across markets, powered by Sportmonks data.
Case study
"Middle East's fastest-growing fan platform."
Built on Sportmonks data to power live experiences for millions of fans.
"Fast and consistent, critical for live features."
Getting started was very smooth. Within a short time we were retrieving data and integrating it.
"Worldwide coverage, at that price point."
Depth of coverage on the worldwide package was unmatched at the price point.
Case study
"Sweden's most complete football site."
Fotboll.com is built end-to-end on Sportmonks data across all major leagues.
The Sportmonks Cricket API is a REST API that returns live and historical cricket data as JSON. Every match is a fixture with its own start time, format, venue and status, so a Test, a One Day International and a T20 league game all arrive in the same shape. The format is a field on the fixture, not a different product.
One fixture call assembles a whole scorecard. runs gives you the innings score, wickets and overs. batting gives you every batter with runs, balls faced, fours and sixes. bowling gives you overs, maidens, runs conceded and wickets. lineup gives you both XIs with player photos and the captain and wicketkeeper flags. balls gives you the delivery-by-delivery record, and venue gives you the ground. You choose what you need with includes, so you are not paying transfer for a ball-by-ball array on a fixture list.
That means one parser covers your whole product. Point it at a fixture ID and render whatever the surface needs: a live scorecard, a commentary feed, a player profile, a fantasy squad picker or a results archive. Already building with our Football API? Same account, same authentication style, same JSON conventions.
A real Test match, mid-innings. The card on the left is rendered from the response on the right. Same call, nothing added, nothing tidied up.
New Zealand · 1st Innings
135/0 (34.2 ov)
Tom Latham (c) not out
65986066.33
Devon Conway not out
6511011059.09
England · Bowling
Gus Atkinson
802803.50
Jofra Archer
4.201503.46
Josh Tongue
822903.63
Shoaib Bashir
913003.33
Ben Stokes (c)
503006.00
England
Ben Duckett
Emilio Gay
Jacob Bethell
Joe Root
Harry Brook
Jamie SmithWK
Ben StokesC
Gus Atkinson
Jofra Archer
Josh Tongue
Shoaib Bashir
New Zealand
Tom LathamC
Devon Conway
Henry Nicholls
Rachin Ravindra
Daryl Mitchell
Tom BlundellWK
Mitchell Santner
Nathan Smith
Blair Tickner
William O'Rourke
Ben Sears{
"data": {
"resource": "fixtures",
"id": 67365,
"league_id": 111,
"season_id": 1682,
"round": "New Zealand tour of England, 3rd Test",
"localteam_id": 38,
"visitorteam_id": 42,
"starting_at": "2026-06-25T10:00:00.000000Z",
"type": "Test/5day",
"live": true,
"status": "1st Innings",
"note": "Day 1 - Session 2",
"venue_id": 23,
"toss_won_team_id": 42,
"elected": "batting",
"localteam": { "id": 38, "name": "England", "code": "ENG" },
"visitorteam": { "id": 42, "name": "New Zealand", "code": "NZ" },
"scoreboards": [
{ "team_id": 42, "type": "total", "scoreboard": "S1", "total": 135, "overs": 34.2, "wickets": 0 },
{ "team_id": 42, "type": "extra", "leg_bye": 3, "noball_runs": 2 }
],
"runs": [
{ "team_id": 42, "inning": 1, "score": 135, "wickets": 0, "overs": 34.2 }
],
"batting": [
{ "player_id": 205, "score": 65, "ball": 98, "four_x": 6, "six_x": 0, "rate": 66 }, /* Tom Latham */
{ "player_id": 4817, "score": 65, "ball": 110, "four_x": 11, "six_x": 0, "rate": 59 } /* Devon Conway */
],
"bowling": [
{ "player_id": 5177, "overs": 8, "medians": 0, "runs": 28, "wickets": 0, "rate": 3.5 }, /* Atkinson */
{ "player_id": 424, "overs": 4.2, "medians": 0, "runs": 15, "wickets": 0, "noball": 1 },
// … Tongue, Bashir, Stokes
],
"lineup": [
{ "id": 205, "fullname": "Tom Latham", "position": { "name": "Wicketkeeper" },
"lineup": { "team_id": 42, "captain": true } },
// … 21 more players (both XIs, with image_path)
],
"balls": [
{ "ball": 34.2, "bowler_id": 424, "batsman_id": 4817,
"score": { "name": "No Run", "runs": 0, "is_wicket": false } },
// … 207 more deliveries from ball 0.1
],
"venue": { "id": 23, "name": "Trent Bridge", "city": "Nottingham", "capacity": 17000, "floodlight": true }
}
}
Values are printed exactly as the API returns them. Strike rates and economy rates are computed from the returned runs and balls, so 65 off 98 is 66.33 and 15 off 4.2 overs is 3.46. The extras split matters: leg byes are credited to the innings but not charged to a bowler, which is why the five bowlers concede 132 against an innings total of 135. Positions in the lineup tab are the career positions the API returns on each player, not the role in this match, which is why two New Zealand batters are marked WK while Tom Blundell keeps.
Every cricket plan returns the same data set. The plans differ in how many competitions your token can reach, never in what a match returns. These are the actual field names in the response, so you can map your models before you write a line of integration code.
You choose which arrays come back with includes, so a fixture list does not carry a ball-by-ball payload it does not need. Field availability follows the match: a completed Test returns all four innings where a game in progress returns the innings played so far, and the balls array grows as the match does. Full field definitions live in the Cricket API documentation.
These are the four things cricket builders actually ship. All four come out of the same fixture call, so you are not integrating four times to build four surfaces.
The innings score, wickets, overs and run rate that a fan opens the app for, plus both XIs and the toss. Refresh the fixture at the rate your product needs and the card moves with the match.
Every delivery with the over, the bowler, the batter and the outcome, including a wicket flag. Render it as a feed, as an over-by-over strip of dots and boundaries, or as the input to generated commentary.
Batting and bowling figures per match, so a player profile is an aggregation over matches rather than a separate data source. Photos come from the same response, so a profile page needs no image pipeline.
Squad selection needs both XIs before the first ball, and scoring needs runs, balls, wickets and maidens after it. Both arrive on the same fixture, so team locks and points settlement read from one source.
Sportmonks' API gave us the speed, depth, and flexibility to create a world-class cricket app, especially for the fans who live and breathe this game.
One base URL, one token, standard REST and JSON. If you can make an HTTP request, you can use the Cricket API. Already on the Sportmonks Football API? Same account, and the response conventions are the ones you know.
include=batting,bowling,lineup, and get the scorecard and both XIs in one response.balls when you want the delivery-by-delivery record, and leave it off when you do not, so a fixture list stays small.Cricket data is delivered over REST, so you request the match you are showing and refresh it at the rate your product needs. Every cricket plan allows 2,000 API calls per hour, which covers a live scorecard refreshing through a full day's play.
Stuck on an include or a field name? You talk to a person, 7 days a week. Sportmonks is the only sports data API with an actual face.
{
"data": {
"id": 67365,
"type": "Test/5day",
"status": "1st Innings",
"live": true,
"batting": [
{
"player_id": 205,
"score": 65,
"ball": 98,
"four_x": 6
}
// one object per batter in the innings
],
"bowling": [
{
"player_id": 5177,
"overs": 8,
"runs": 28,
"wickets": 0
}
// one object per bowler used
],
"lineup": [
{
"id": 205,
"fullname": "Tom Latham",
"lineup": { "captain": true }
}
// 22 players, both XIs
]
}
}
"Sportmonks gave us the best balance of quality, affordability, and scalability, making it the perfect choice to power CricBolt's mission of delivering a world-class cricket experience to fans worldwide."
"Once you start utilising it, you realise that its excellence isn't just superficial, the quality of the data itself stands out."
"Finding a provider with great quality and an affordable price was tough until we found Sportmonks. The balance between cost and coverage makes them the most valuable data partner we've worked with."
Read the full stories on our case studies page.
All three cricket plans return the same fields, the same formats and the same rate limit. The only thing that changes is how many competitions your token can reach, so you start where your product is today and move up when it grows.
For a product built around the competitions your audience already follows.
per month
For a product covering international cricket and the major domestic leagues together.
per month
For a global cricket product that cannot afford a competition it does not cover.
per month
No contracts and no minimums. Move up a plan when your product needs more competitions, and cancel before the end of a billing cycle without a fee. All prices are exclusive of VAT and, where applicable, VAT will be applied at the standard rate.
Quick answers before you sign up. Want the long version? It is all in the Cricket API documentation.
The Sportmonks Cricket API is a REST API that returns live and historical cricket data as JSON. Every match is a fixture with its own start time, format, venue and status, so a Test, a One Day International and a T20 league game all arrive in the same shape.
One fixture call can assemble a whole scorecard: runs for the innings score, batting and bowling for the cards, lineup for both XIs, balls for the delivery-by-delivery record and venue for the ground. You choose which of those come back using includes.
Per match you get the innings score with wickets and overs, extras broken out by type, a batting card with runs, balls faced, fours and sixes per batter, and a bowling card with overs, maidens, runs conceded and wickets per bowler.
Alongside that you get both named XIs with captain flags and player photos served from our CDN, every delivery with the bowler, the batter, the runs and a wicket flag, plus the toss, the format, the match state and the venue with its capacity.
International and domestic cricket across formats: Test matches, One Day Internationals and T20, including competitions such as the ICC World Test Championship, One Day Internationals and the major domestic T20 leagues. The format is returned as a field on the fixture, so you do not integrate differently per format.
How many competitions your token can reach depends on your plan: 26 leagues on Major, 64 on World, and every league we cover on Enterprise. The data set itself is identical on all three.
Yes. A live fixture carries a live flag along with a status and a note, so you know it is Day 1 Session 2 in the first innings, and the score, the cards and the balls array all move as the match does.
Data is delivered over REST, so you request the match you are displaying and refresh it at the rate your product needs. Every cricket plan allows 2,000 API calls per hour, which covers a live scorecard refreshing through a full day's play.
There are three cricket plans: Major at 29 euro per month for 26 leagues, World at 75 euro per month for 64 leagues, and Enterprise at 125 euro per month for every cricket league we cover. Prices are exclusive of VAT.
All three return the same data set and the same 2,000 API calls per hour, so the plan you choose is about competition reach and nothing else. No contracts and no minimums, and you can move up a plan whenever your product needs more competitions.
Yes. Sign up and you get an API token instantly, with no credit card and no sales call, so you can make real calls against real matches before you decide. Every cricket plan also carries a 14-day free trial.
The trial starts when you subscribe to a plan. After 14 days your card is charged unless you cancel in time, and you are permitted one free trial. If you get stuck at any point, you talk to a person, 7 days a week.
Cricket, football and Formula 1 all live on one Sportmonks account, with the same authentication style and the same JSON conventions, so adding a sport does not mean adding a vendor or a second integration pattern.
Each sport is its own subscription, and cricket runs on our Cricket API where football runs on Football API v3, so the base URL and the include syntax differ. Check your plan in MySportmonks for exactly which sports your token is entitled to.
We manage all our data in the Sportmonks Scout Application Platform. Dedicated scout teams around the world add, manage and validate the data collected through that platform, and we work with data partners to keep cricket data reliable and up to date.
That is the same infrastructure behind 6.4 billion API requests a month and 99.99% uptime measured across our platform. Those are measured figures rather than a contractual guarantee.
Cricket is really three sports wearing one name, and most data providers make you feel it. Here the format is a value in the type field on the fixture, so the same parser reads a five-day Test and a three-hour T20. What changes is how many innings rows come back and how much match state there is to show.
Up to four innings across five days, so the innings array is the longest of the three formats and a side can bat twice. This is also the only format with day and session state to render, which is what makes a Test scorecard the hardest surface to build and a good one to test your integration against.
Two innings, one per side, capped at 50 overs each. The innings array is short and predictable, which makes ODIs the simplest format to model first. Run rate and required run rate both matter to a viewer here, and both follow from the runs and overs the API already returns.
Two innings of 20 overs, where the whole match turns on individual deliveries. This is the format where the ball-by-ball array earns its keep: with only 120 legal deliveries a side, a boundary or a wicket is a meaningful share of the game, and most fantasy and engagement products are built on exactly that granularity.
Practically, this means you write one renderer and branch on the format rather than maintaining three. The fields do not change between formats: a batting row is a batting row whether it took 98 balls in a Test or 12 in a T20. What changes is how many runs rows you loop over, and whether note carries day and session information as it does on a Test. Shortened or rain-affected matches return the overs actually bowled, so never hardcode an overs limit as a display assumption. Exact format values and the full field reference are in the Cricket API documentation.
Professional-grade cricket data on the most approachable sports data API. Get a token, call a real match, and see the response before you commit to anything.