Runs and extras
Separate bat runs, wides, no-balls, byes, and leg-byes so totals can be checked.
CricketLineAPI
Ball-by-ball cricket API for live commentary
Follow every delivery instead of waiting for the next scorecard refresh. Each event includes the batter, bowler, runs, extras, wicket detail, score, and commentary text when the source provides it.
Fields on every delivery
Wicket detail
Dismissal type, batter, bowler, and fielder are included when a wicket falls.
Commentary text
Short text is suitable for a live ticker, timeline, or notification.
Over context
Over number, ball number, score, and wickets show the match state after the delivery.
Example delivery
{"match_id":"ind-eng-t20-2026-01","over":17,"ball":3,"batsman":"Virat Kohli","bowler":"Jofra Archer","runs":6,"extras":0,"event":"boundary","score":"148/4","commentary":"Kohli clears long-on for six."}Products this endpoint supports
Live tickers
Show the newest deliveries without downloading the full scorecard.
Alerts
Notify users on wickets, fours, sixes, or a target being reached.
Over summaries
Group deliveries into runs and wickets for each over.
Match replay
Rebuild the innings from the stored delivery sequence after the match.
Commentary endpoints
GET /api/match/{id}/commentary
Returns the stored delivery list for a match.
GET /api/match/{id}/commentary/live
Returns the latest deliveries for polling clients.
GET /api/match/{id}/wickets
Returns wicket events without the rest of the commentary.
GET /api/live/stream
Publishes live events for clients that can consume a stream.
Implementation notes
Polling clients should store the last over and ball they rendered, then request only the newest deliveries. Streaming clients should treat the match ID as the subscription key and ignore duplicate events if the connection reconnects. Both patterns can sit beside a scorecard request if the page also shows batting and bowling tables.
Do not calculate the innings total only from commentary text. Use the numeric runs, extras, and score fields. Commentary is display copy and may be shortened for a ticker. Wicket alerts should use the event field so a mention of a wicket in text does not create a false notification.
Completed matches keep the stored sequence when the source supplied it. That makes the endpoint useful for recaps, content tools, and model training features that need the order of boundaries and wickets rather than only the final scorecard.
Ball-by-ball questions
Can I poll instead of streaming?
Yes. The live commentary endpoint is for clients that request the newest deliveries on an interval.
Are old deliveries retained?
Completed matches keep the stored sequence when the source feed provided ball-by-ball coverage.
Does every ball include text?
Runs, score, and event fields are the core response. Commentary text is included when available.
Related cricket APIs
Live Cricket API
Open this related cricket API page.
Cricket Data API
Open this related cricket API page.
Scorecard 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