01Competitionscout · score · protocol
→02TPTevent_id · match_id · version
→03Data + Videostate · heartbeat · HLS
→04Distributionaggregators · sportsbooks · media
Match lifecycle
create → start → score → sets → status → result → protocol
Reliability
Versioning, 30-second heartbeat, idempotent repeats and stable identifiers.
Source
First-party point-by-point live data directly from the venue. The final result is backed by the official match protocol.
Security
Signing secrets, internal endpoints and service tokens are never exposed to the client.
Event contract
A clear integration package
The public layer can be connected through read-only REST/JSON or an agreed event stream. Internal keys and service endpoints stay server-side.
event_idmatch_idstatusstart_atscoresetsversionheartbeat{
"event_id": "matchcore-spin-32",
"match_id": "32",
"status": "finished",
"score": { "home": "3", "away": "0" },
"version": 12
}