Turnkeyxgaming

Data · Cricket data

Cricket data API: fixtures, markets, scores and results

A cricket data feed is the record a sportsbook or exchange reads: the fixture, the markets on it, the score as it changes, and the result those markets settle from.

What a cricket data feed contains

Ball-by-ball facts sit inside that record when a line depends on them. The live scoreboard and the embeddable score widget are a separate product on the cricket score API.

A fixture needs a stable id, the competition, the format and the two sides. Markets hang off that id: match odds and, where the feed carries them, session and fancy lines. Scores update against the same id. Results are a later message, and a corrected result is the one you settle from. A session or fancy line that never arrived in the feed is a price you composed, and it should not be offered.

Fancy and session lines settle from the ball, not from a total alone. A ball event needs the over, the ball in that over, the runs, and whether it was a wicket, a wide or a no-ball. An innings total cannot settle a line that depends on a particular over being bowled. Store the format on the fixture, because a T20, a one-day match and a Test do not share a session structure. When an over is not bowled, the market's void rule decides, which is the subject of the fancy void note. A late ball is a late suspension: someone with a faster picture can bet a price you have not moved.

Rights vary by competition. We do not list a set of tours as included. Your contract does. The Diamond exchange uses cricket markets heavily, and the sports data page is the wider feed those markets sit beside. None of this is a promise that a competition whose rights you have not bought will appear.

Keep the ball log, including a corrected delivery

Store each delivery in order against the fixture id. A corrected ball replaces that delivery and can move a line that already looked finished. When the feed says the over was not bowled, wait for the void or result message. Do not fill the gap from the previous over.

Which cricket message does which job

MessageUse it forDo not use it to
FixtureId, format, competition and the two sidesGuess a session length from the team names
MarketMatch odds, or a session or fancy line the file containsInsert a fancy line the feed never sent
BallOver, ball, runs, wicket, wide or no-ballClose a session line from the innings total alone
ResultThe outcome, including a later correctionIgnore the correction because an earlier file already paid

Using the fixture, not the graphic

  1. 01

    Key the fixture

    Attach markets, scores and results to the fixture id, not to the team names.

  2. 02

    Format on the fixture

    Store T20, one-day or multi-day so session rules can be applied.

  3. 03

    Suspend on the ball

    Treat a wicket or a boundary as a reason to suspend, then reopen when prices catch up.

Legal markets only

Cricket products are offered to operators licensed to provide them. India's ban on online money games, described on the Asia page, is unchanged by the existence of a data feed.

A worked fancy settlement, including the case that goes wrong

Take a line of 49 runs on the sixth over, quoted as 49/50, with a player backing the over. If the over completes on 51 runs, the over wins and the wallet pays from the ball log. If a wicket falls on the last ball and the sixth over is cut short, the line's void rule decides: some operators void, some settle from the runs actually scored. Either is defensible. Inventing a rule after the fact is not.

The subtler failure is the definition. A wide is a ball, but it is not a run off the bat, and a line that reads runs in the over while the player assumed runs off the bat will produce the same complaint either way. The definition published next to the price has to say which of the two it means, and the ball event you settle from has to carry extras separately. That is why each delivery stores runs, wicket, wide and no-ball as distinct facts rather than one blended number.

Reading a cricket data contract without a lawyer's patience

Six questions, and the answer that should make you walk away:

  • Which formats are included: T20, one-day and multi-day carry different session structures. Cricket as a single answer is not an answer.
  • Which competitions, named, in writing. A rights list that lives in a sales deck will not survive its first league season.
  • Whether every ball event carries over, ball-within-over, runs and the extras flag. A total-only feed cannot settle a fancy line.
  • How a corrected delivery arrives: as a replacement for that ball, with the original retained for audit.
  • What happens to open session lines when an over is not completed. There should be a written rule, not an ops judgement.
  • Whether session lines exist pre-match for the longer formats, or whether in-play only is the honest description.

Which cricket market settles from what

MarketSettles fromFrequent mis-settlement
Match oddsThe official match result, corrections includedPaying from a projected result while the match is still live
Completed-over fancy lineThe ball log for that over, once it completedSettling from the innings total because the over file was missing
Session lineThe runs in the stated over spanBorrowing a session span from a different format's structure
Top batsmanThe scorecard's batting recordIgnoring a retired-hurt batter who later returned
Innings totalThe completed innings or the official resultVoiding the market because the target was not chased, which is not a void

FAQ

Questions operators ask

Can I rebuild the widget myself from this feed?

If your contract includes the ball and scorecard fields, you can render your own scoreboard. The hosted widget remains the faster option when you do not want a renderer.

Is this the embeddable scoreboard?

The scoreboard iframe and the score widget are the cricket score API. This feed is the fixture, the markets, the ball and score facts, and the result those markets settle from.

Can one market schema cover a T20 and a Test?

The fixture id can be shared as a keying scheme. The session rules cannot. Persist the format, and apply the void and session structure that belongs to that format.

Do you supply line definitions for the fancy markets, or do we write our own?

The lines the feed carries arrive with their own definitions, and your job is to publish the definition beside the price. A line you defined yourself is a market you invented, whatever the feed called it.

What should a support agent answer when a player disputes a fancy settlement?

The ball log for the over, the line definition published at bet time and the void rule. Three records, all stored against the fixture id, answer it without a trading person in the room.

Can the same feed power both our exchange and our sportsbook?

The fixture, ball and result records can. The exchange adds back and lay state and lay liability, which belongs to the Diamond exchange contract, not to the data file.

Keep reading

Related pages

  • Product · Cricket scoresCricket scoresA cricket scoreboard iframe and widget for exchange pages, with ball-by-ball detail where the data licence allows display.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
  • Data · Exchange dataExchange dataExchange data is market state plus back and lay prices. It is not a fixed-odds feed, and it is not Betfair's Exchange API either.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