Turnkeyxgaming

Product · Cricket scores

Live cricket score API, scoreboard and widget

The cricket score API is the live score a player looks at: a scoreboard on the exchange or sportsbook page, dropped in as an iframe or drawn from score messages in your own layout.

score.update (illustrative)
{
  "match": "IND v AUS",
  "innings": 1,
  "score": "214/4",
  "overs": "38.2",
  "striker": { "runs": 71, "balls": 64 },
  "last_ball": "4"
}
Illustrative message. Coverage and latency depend on the data licence.

Two ways to show the score

Cricket score widget

  • Cricket scoreboard iframe you embed above the market
  • No front-end work beyond sizing and placement
  • Styling limited to the widget's theme options

Real-time cricket score API

  • Score messages for a board you design
  • You place the total, overs and last ball
  • Needs a renderer and a reconnect strategy

Latency, suspensions and fair play

It shows the innings, the total, the overs and the last ball. Fixtures, markets and settlement results are the wider feed on the cricket data API.

On an exchange or in-play page, a score that arrives late is a risk: a player can act on a total your board has not shown yet. Use the score event to hold the market on a boundary or a wicket, and reopen it when the price has caught up. The widget is the view beside the lobby or the market. Which tournaments are covered, and what latency is contracted, depends on the data rights for each competition.

A board that has stopped moving

When messages stop, the iframe or your own renderer should say the board is stale. Keep the last total on screen and show the time of the last ball, so a frozen overs figure is not read as the live over. On reconnect, replace the board from the next full snapshot. Appending a delivery you are not sure you missed will invent a ball. The sample on this page is a shape. Contracted delay, and which competitions are in it, sit in the data licence.

Fields a scoreboard paints

These are display fields. They do not price a market and they do not close one.

FieldCricket score widgetA board you draw
Innings and totalShown in the cricket scoreboard iframeYou place both, and you keep them on one match id
OversShown beside the totalYou follow the decimal the message uses
StrikerRuns and balls when the message includes a strikerOmit the line when the striker is absent
Last ballThe last delivery, such as a fourClear it until the next delivery arrives, instead of repeating the previous one

Scoreboard and widget only

This product is the live cricket score API: the scoreboard iframe, the score widget, and the score messages behind a layout you design. Fixtures, priced markets and settlement results, including fancy and session lines, are the cricket data API.

Ball-by-ball data runs behind the broadcast, and that is normal

A television picture reaches the viewer through a distribution chain with its own seconds of delay, while a scoring feed is keyed by the scorer at the ground. The two pictures rarely agree to the second, and which one leads can change during an innings. Anyone quoting an exact universal gap is guessing; the contracted delay for your competitions sits in the data licence and is confirmed in writing during onboarding.

Design for the gap instead of denying it. The widget shows the score it received, at the time it arrived, and the market beside it suspends on the event rather than on the picture. A player who believes the scoreboard is trading against the broadcast will discover that during a wicket. Your job is narrower and achievable: the market must not move on a score the board had not yet shown.

Display, not decisions

The widget and the score messages are presentation products. Where operators try to stretch them, and what to use instead:

Tempting useWhy it failsThe right product
Settling a session line from the totalA line can depend on an over being completed, which a total cannot tell youResult messages on the cricket data API
Pricing in-play markets from the scoreA price needs market state and trading rules, not just a totalThe priced feed your book settles from
Voiding a fancy bet because the board stoppedA stale board is a display condition, not a settlement conditionThe void rule on the market, applied to the result file
Auto-posting scores to social channelsA frozen board will publish a stale total as newsA staleness check before anything publishes

Placing the scoreboard so it is used, not scrolled past

  • Above the match odds and the fancy rows on the event page, not inside a tab the player has to open.
  • A fixed height in your layout, so the page does not shift when the iframe loads and a stake never lands on a button that moved.
  • The words live score beside it, with the time of the last update, so a paused board is not mistaken for a paused match.
  • One match id binding the board to the market block, so a delayed start does not leave yesterday's score next to today's coupon.
  • A fallback line when no messages arrive: say the feed is delayed. Do not render an empty rectangle.

FAQ

Questions operators ask

Does the widget work on mobile?

Yes. The scoreboard iframe is responsive. Give it a fixed height in your layout so the page does not shift when it loads.

Which competitions are covered?

Coverage depends on the data licence and is confirmed per contract. We do not publish a blanket list.

Can the score widget settle a session or fancy line?

It shows the innings. Settlement of session and fancy lines uses the result messages on the cricket data API. Place the widget beside a market when the player should see the score while they bet.

Is the widget faster than building our own board from the score messages?

The widget and the messages come from the same score source. The widget saves you the renderer and the reconnect logic; your own board buys layout control. Latency between them is not the deciding factor, the build cost is.

Can we change the colours and fonts inside the iframe?

Within the widget's theme options. Anything beyond that theming surface means rendering your own board from the score messages.

Does the widget include commentary or video?

No. It is a scoreboard: innings, total, overs, striker and last ball where the licence supplies them. Streams and video rights are a separate question entirely.

References

Sources and further reading

Primary regulator, standards or studio documentation behind the technical and regulatory points on this page. External links open in a new tab. Links checked 2026-11-15.

  • ESPNcricinfo

    Published scorecards and match data used to check feed behaviour.

    www.espncricinfo.com

  • UK Gambling Commission

    Remote gambling and software technical standards.

    www.gamblingcommission.gov.uk

Keep reading

Related pages

  • Data · Cricket dataCricket dataCricket fixtures, markets, scores and results, including the ball-by-ball facts used to settle fancy and session markets correctly.Read
  • Product · ExchangeDiamond exchangeBack and lay on cricket match odds, bookmaker and fancy markets, with lay liability reserved on the same wallet. Not the card games.Read
  • Product · Sports dataSports dataFixtures, pre-match and live odds, scores and results for operators who build their own sportsbook front end and settle bets themselves.Read
  • Product · SportsbookSportsbookAdd pre-match, in-play, esports and virtual sport as a wallet iframe, or take the odds feed and build a betslip your traders run.Read

Get a written quote and sandbox access

Tell us your licence, target markets and products. You get the GGR rate in writing, the studio list for your markets and sandbox credentials.

Telegram @turnkeyxhub WhatsApp Email Contact form