Current component check
This browser requests the public health endpoint when the page opens. The result is a point-in-time dependency check—not measured uptime, historical availability, or a contractual SLA.
Waiting for a fresh response from /healthz.
Current public contract
Stats API publishes 32 implemented operations covering service health, coverage, competitions, seasons and groups, standings, teams, players, fixtures and results, match and player statistics, lineups and timelines, injuries and suspensions, referee assignments, and odds. The OpenAPI document is the executable source of truth.
The roadmap lists 35 operations in all; the other 3 (a shot map and heat maps) are planned and not available. A roadmap entry never makes an operation available.
Two data sources are enabled: OpenFootball football.json, a community-maintained CC0 historical dataset, and API-Football, a licensed provider added on 30 Aug 2026. Customer requests read stored data only. Coverage varies by competition, season and match, and nothing here promises live delivery times or a maximum data age; check the coverage page before you build.
Release notes
| Date | Milestone | Verified boundary |
|---|---|---|
| 26 Oct 2026 | Availability flags, started and played, event order | Every match now carries details_available (timeline, lineups, statistics, player statistics: whether Stats API holds each for that match). Per-player match statistics gain started and played, where played is true, false or null for unknown. Timeline events gain a sequence number in the provider’s order. These are additive response fields; no operation was added or removed. |
| 25 Oct 2026 | Machine-readable articles and clearer limits | Blog articles can be read as Markdown (.md or Accept: text/markdown), the home page shows a real recent-results sample, and a request beyond the free allowance returns a 429 whose details link to the plans. No operation was added or removed. |
| 11 Oct 2026 | 32-operation contract and odds | Seven operations were added: season groups, referee assignment, team and player season statistics, prematch odds, live odds, and observed prematch goal-scorer odds. Odds are read from stored observations that carry freshness and expiry fields; bookmaker and market coverage varies. New accounts receive 200 free requests once. |
| 28 Sep 2026 | Paid plans and checkout | Starter, Growth and Scale monthly plans with signed-in checkout and a billing dashboard. The pricing page, not this note, states the current plan terms and the size of the free allowance. |
| 20 Sep 2026 | Accounts and hosted checkout | Account signup with Google sign-in, API keys, a one-time signup allowance and hosted checkout were enabled. The published contract was 25 operations. |
| 30 Aug 2026 | Licensed second data source | API-Football was enabled beside OpenFootball, adding match events, lineups and team match statistics. Coverage varies by competition. |
| 28 Jul 2026 | Public-preview foundation | Versioned football API contract, stable Stats API IDs, cache-first reads, account dashboard, usage controls, source ledger, agent-readable docs, blog, FAQ, and public health checks. |
Feature flags can keep account, API, or billing capabilities paused independently. A release note records what the software supports; the current documentation, coverage response, and checkout state remain authoritative for what a customer can use now.
Service and incident history
No customer-impacting incidents recorded
No verified customer-impacting incident has been recorded in this public history since it began. This describes the contents of the record; it does not claim 100% uptime or prove that no unobserved interruption occurred.
This public history begins on 28 July 2026. It is prospective and does not attempt to reconstruct uptime or incidents before that date. Incidents are never inferred from a missing probe or backfilled without a verified record, and the absence of an incident entry is not a guarantee of uninterrupted uptime.
Confirmed customer-impacting incidents will use the states investigating, identified, monitoring, and resolved. A published entry includes a neutral incident ID, severity, affected public components, customer-visible impact, UTC start and recovery times, a high-level resolution, and customer-relevant follow-up actions.
Public entries are sanitized. They never include secrets or API key material, customer or account identifiers, raw request or webhook payloads, database records, private hostnames, internal listeners, filesystem paths, protected co-tenant details, or exploitable security steps.
The machine-readable health endpoint reports the current database, required-schema, and cache dependency state. It is an operational signal, not a contractual SLA or a substitute for an independent external monitor.
How API changes are recorded
- Additive fields and operations appear in OpenAPI before examples or marketing copy rely on them.
- Breaking changes require a versioned contract or an announced migration path unless an urgent security, legal, or source-rights issue requires faster action.
- Corrections, reschedules, source limitations, and freshness boundaries remain visible in documentation rather than being described as guaranteed live data.
- Roadmap operations stay visibly separate from implemented operations until their data rights, ingestion, storage, tests, and public contract are complete.