Product overview
Verified competitive data infrastructure
One verified outcome flows across your overlays, brackets, APIs, and leaderboards.
StatForge verified core
sf_match_12845
Published · 21:14 UTC
Admin console
Team site
Leaderboard
Broadcast overlay
Tournament bracket
Illustrative fan-out after verification and publish
Your stack sets real order and latency.
Publish
21:14:02
Overlay refreshed
API cache updated
Webhook delivered
Leaderboard updated
Bracket advanced
Mobile app synced
Broadcast overlay
21 - 14
Final
Leaderboard
| # | Team | W-L | Pts |
|---|---|---|---|
| 1 | Northwind | 8-1 | 24 |
| 2 | Aurora | 6-2 | 17 |
| 3 | Obsidian | 5-3 | 11 |
W-L and Pts are season standings, not the match scoreline (21-14).
#1 Northwind · official 21-14 vs Aurora
Admin console
Operators see the live canonical row.
Verified outcome payload
Stable response shapes designed for overlays, ladders, and automation. Verified match payloads stay consistent across downstream systems.
{
"match_id": "sf_match_12845",
"status": "verified",
"score": {
"northwind": 21,
"aurora": 14
},
"published_at": "2026-04-12T21:14:00Z",
"schema_version": 2
}Webhook events
Rolling out next: subscribe per environment. Payloads mirror the same verified read schemas you poll today; not a second contract.
Poll today
Why teams build on StatForge
Engineering and ops assumptions that hold under load.
Canonical records
One authoritative row per match across read paths.
Operational consistency
Leaderboards, brackets, and apps stay on the same outcome.
Developer-first integrations
Predictable HTTP payloads and documentation that matches reality.
Auditability
Timestamped publication your operators can trace.
Scale
Peak traffic days and global tournaments included.
Detection, disputes, and publication rules live in Matches and developer documentation.
Ready to integrate verified outcomes?
Keys, sandbox, and backend wiring.
API behavior, auth, and integration guides.