Source and coverage
STARsBUZZ uses Sportmonks Cricket API as its external cricket-data source. The website can display only eligible records and relations returned to the connected account. A competition, team, fixture, inning, scorecard, lineup, venue, official, or image may be absent because it is outside the plan, unavailable for that match, delayed, or not supplied by the provider.
Server-side retrieval
The visitor’s browser does not contact Sportmonks directly. It asks the STARsBUZZ backend for a typed response. The backend authenticates with the provider, validates the returned envelope, converts supported fields into stable internal models, and stores a shared snapshot. This keeps the provider token outside React code, HTML, browser requests, and public logs.
Live-view checks and freshness
While an eligible live page is visible, the browser is configured to check the STARsBUZZ backend every 9 seconds. This is a website-to-backend check target, not a statement that the provider changes every score at the same interval. Background checks pause when the page is hidden. A manual Refresh action may request the latest eligible shared snapshot without allowing repeated concurrent clicks.
Live records use a short shared cache target. Fixtures, results, and completed match pages use longer targets because their data changes less frequently. During a provider fault, STARsBUZZ may show a bounded, previously validated snapshot only when it can be clearly labelled with retrieval and freshness context. Otherwise, it shows an unavailable state.
Match states
STARsBUZZ preserves material distinctions between upcoming, starting, live, scheduled break, delayed, interrupted, postponed, abandoned, cancelled, completed, and unknown records when they are returned in an eligible view. The Results page currently includes only exact provider Finished and Cancelled states. Delayed or interrupted play is not collapsed into a generic live state, and no winner is invented from incomplete data.
Scores, innings, and optional details
Match pages can show participant totals, wickets, overs, innings, start time, competition, format, venue, status, and provider result notes when those fields are returned and safely normalized. The current public interface also labels whether scoreboards, batting data, bowling data, or lineup data were returned; it does not present those detailed records as a complete scorecard or team sheet. No match is promised to have every field.
Time conversion
Provider timestamps are stored and transmitted as coordinated universal time. The browser converts a match start into the visitor’s local timezone for display. Match start time, provider update time, STARsBUZZ retrieval time, cache age, and the visitor’s current clock are separate values and are not presented as interchangeable.
Correction requests
If a displayed record appears inconsistent with the provider source, use the Contact page and select Match-data correction. Include the STARsBUZZ match URL, the field in question, and a concise explanation. Do not send passwords, payment-card data, API credentials, government identifiers, or unrelated sensitive information.