Method

Cricket data guide

How records move from a server-side provider request to a clear public data state.

The server-only path

The browser calls Star Buzz through typed application procedures. The server makes fixed-profile requests to Sportmonks Cricket API v2.0, applies a nine-second timeout, validates endpoint-specific response shapes and publishes a bounded public model.

Validation and normalization

Fixture identifiers, team identifiers, start times and statuses pass strict checks. The public model focuses on text records and provider-supplied player names. The normalizer preserves the provider status, score values and result note while labelling optional field availability.

Adaptive freshness

Live information uses a shared five-second cache while visible pages apply a small stable timing variation. Upcoming fixtures, recent results and non-live Match Centre records use a sixty-second fresh window. Saved validated snapshots may be labelled stale within bounded resilience windows.

Six public states

Fresh
A current validated response.
Stale
A saved validated response displayed with its prior checked time.
Empty
A complete request returned zero covered records.
Partial
Core facts are available while optional fields are pending.
Restricted
The view is outside current data access.
Unavailable
The current request awaits a usable provider response.

Local time and corrections

Stored instants remain UTC. The initial public view formats them in Asia/Kolkata. To request a correction, use the data-correction form and include the fixture or field details needed for review.