Sportmonks data guide

How match data travels from source to screen.

This guide explains what Starbuzz retrieves from Sportmonks, how records are validated and cached, and why some fields or competitions may be unavailable.

Data source and relationship

Starbuzz score-cric retrieves eligible cricket records through a separately configured Sportmonks Cricket API account. Sportmonks supplies the source data; Starbuzz independently validates, normalizes, caches and presents it. Starbuzz is not owned by Sportmonks and does not claim that Sportmonks endorses this website.

External data sourceSportmonks Cricket API
Live-page browser checkEvery 8 seconds while visible
Shared live cacheApproximately 7 seconds
Fixture cacheApproximately 5 minutes
Result cacheApproximately 10 minutes
Cricket ball, magnifying glass and paper records at a neutral verification workstation
A fictional verification scene; no provider interface, score or ownership relationship is depicted.

Fields that may appear

InformationWhere usedAvailability rule
Teams, competition and start timeLists and match pagesRequired for a usable Starbuzz match record.
Match state, runs, wickets and oversLive scores and resultsShown as supplied; missing values remain unavailable.
Venue and cityFixture and match factsShown only when the provider relation is present.
Batting and bowling figuresMatch detailConditional; not every covered match has a full scorecard.
LineupsMatch detailConditional; player roles may also be incomplete.
Provider update timeMatch factsDisplayed separately when the provider supplies it.

Match states

Starbuzz preserves meaningful provider distinctions such as scheduled, starting, innings in progress, innings or scheduled break, delayed, interrupted, postponed, abandoned, cancelled and finished. Unknown provider states are labelled neutrally rather than forced into an incorrect category.

Refresh timing

A visible live page asks the Starbuzz backend for a new snapshot every eight seconds. The backend shares a short-lived cache among visitors and coalesces concurrent requests to reduce duplicate provider calls. The displayed cache age and Starbuzz retrieval time describe the website’s own data path. They do not promise that Sportmonks changes a record every eight seconds.

Coverage and corrections

Coverage depends on the connected subscription and the provider record for each fixture. If a field looks incorrect, send the match URL and field through the Contact page. Starbuzz can inspect its normalization and display but may need to wait for or report an upstream correction.

Official provider references

Developers can review the official Sportmonks Cricket API documentation, including its endpoint, include, response-code and rate-limit guidance.