Batting card
Each batter includes runs, balls, fours, sixes, strike rate, and dismissal text when the player is out.
CricketLineAPI
Cricket Scorecard API for live and completed matches
Build match centers without scraping HTML. One scorecard request returns the innings total, batting card, bowling card, extras, fall of wickets, and partnerships for international and major domestic cricket.
What a scorecard response includes
Bowling card
Each bowler includes overs, maidens, runs, wickets, economy, wides, and no-balls.
Fall of wickets
Wicket number, team score, over, and the dismissed batter are listed in innings order.
Partnerships
Partnership runs, balls faced, and both batter names are available for match reports.
Example scorecard payload
{"match_id":"ind-eng-t20-2026-01","status":"live","innings":[{"team":"India","score":"148/4","overs":"17.2","extras":{"wides":3,"no_balls":1},"batting":[{"name":"Virat Kohli","runs":62,"balls":41,"fours":5,"sixes":2,"dismissal":"not out"}],"bowling":[{"name":"Jofra Archer","overs":"3.2","maidens":0,"runs":28,"wickets":1}]}]}Poll the same match ID while the match is live. After the result is final, the same endpoint continues to return the stored scorecard.
How developers use the scorecard API
Live match centers
Render batting and bowling tables beside the current score and refresh them on a short interval.
Completed match pages
Keep a permanent scorecard URL for every finished international or major domestic match.
Editorial tools
Drop dismissals, extras, and partnerships into reports instead of copying them from a broadcast.
Fantasy context
Show the scorecard behind a player's fantasy points so users can check the calculation.
Scorecard endpoints
GET /api/scorecard/{match_id}
Returns every available innings, including batting, bowling, extras, and totals.
GET /api/scorecard/{match_id}/batting
Returns batting rows only for a compact score widget.
GET /api/scorecard/{match_id}/bowling
Returns bowling figures only when the page does not need batter detail.
GET /api/scorecard/{match_id}/fow
Returns fall of wickets and partnership context.
Implementation notes
Start with the live or schedule endpoint to discover a match ID. Pass that ID to the scorecard endpoint and cache the response according to match state. A live match should be refreshed frequently, while a completed match can be cached for much longer because its batting and bowling rows no longer change.
Use the batting-only and bowling-only endpoints when a widget has limited space. Use the full endpoint for a match center that needs extras, fall of wickets, and partnerships together. If a field is unavailable from the source feed, the key is omitted or returned empty rather than filled with a guessed value.
The scorecard is complementary to ball-by-ball commentary. Use commentary when the product needs every delivery, and use the scorecard when it needs the current innings table. Both can be requested with the same match ID.
Scorecard questions
Which matches include scorecards?
Live and completed international matches are covered, plus major domestic competitions when the source feed provides a scorecard.
How current is a live scorecard?
The same match ID returns the latest processed batting, bowling, extras, and total fields.
Can I query old matches?
Yes. Completed matches remain available so historical match pages do not depend on a live connection.
Related cricket APIs
Live Cricket API
Open this related cricket API page.
Cricket Data API
Open this related cricket API page.
Ball-by-Ball API
Open this related cricket API page.
Fantasy Points API
Open this related cricket API page.
Player Stats API
Open this related cricket API page.
Schedule API
Open this related cricket API page.
Series API
Open this related cricket API page.
Rankings API
Open this related cricket API page.
API Pricing
Open this related cricket API page.
Start with the free cricket data tier
Create an API key, call the endpoint with a match, player, or series ID, and upgrade only when your traffic grows.
Compare API plans