Current first-party scope examples
| Source | Publicly documented signal | Access note |
|---|---|---|
| Opta | Event, tracking and prediction products | Commercial access; confirm contracted coverage |
| StatsBomb | Event and contextual 360 products | Commercial products plus selected open data |
| Wyscout | Versioned API resources and definitions | Authenticated product; inspect current API docs |
| Sportmonks | Football API and expected-data endpoints | Subscription and league coverage vary |
Opta, StatsBomb, Wyscout and Sportmonks describe their current products in first-party material. This table records scope, not an endorsement or complete commercial comparison.
Acceptance criteria
- List mandatory competitions, seasons and women's, youth or lower-division coverage.
- Define required event, lineup, tracking, odds and expected-metric fields.
- Set latency, correction and outage requirements.
- Confirm historical backfill and identifier stability.
- Review display, storage, redistribution and model-training rights.
- Test support escalation and schema-change notice.
Sample-data test
Request the same fixtures from shortlisted providers. Reconcile score, lineup, event order, coordinate system, corrections and missingness. Do not treat one provider as wrong merely because definitions differ; decide which definition supports the product.
StatsBomb's open repository is useful for evaluating a documented event structure before commercial procurement, but its selected coverage should not be mistaken for the paid product.
Total cost record
Include licence, calls or delivery, historical add-ons, storage, transformation work, monitoring and migration risk. A lower feed price can cost more if identifiers or corrections require substantial operations.
Build a weighted selection test
Score providers against the actual use case before discussing brands:
| Criterion | Evidence to request | Example failure |
|---|---|---|
| Coverage | Competition and season inventory | Headline coverage excludes required history |
| Definitions | Data dictionary and sample payload | Same label has an incompatible rule |
| Corrections | Versioning and correction process | Historical values change without notice |
| Freshness | Timestamped delivery test | Feed arrives after the decision window |
| Rights | Written licence terms | Analysis cannot be published or retained |
| Reliability | Trial-period error log | Missing fixtures cluster in key leagues |
Assign weights before trials and keep the raw test results. A provider with more fields may be less suitable than a smaller source with stable identifiers, clear definitions and reproducible corrections.
Migration and lock-in controls
Store provider identifiers alongside internal canonical identifiers. Preserve raw payloads where the licence permits, map transformations in code, and maintain a field-level provenance record. During a migration, run sources in parallel on a fixed sample and quantify definition and coverage differences rather than assuming drop-in equivalence.
StatsBomb's open-data documentation illustrates why competition scope, file structure, and licence must be checked before production use.
Open repositories are valuable for learning and reproducible examples, but their selected competitions and licences may not support a production refresh. Commercial feeds can improve coverage and service guarantees, yet still require the same definition, timestamp and quality audits.
Related resources
Continue with building a stats dashboard or what model data means.
Continue learning
- Next guide: Football Prediction Models
- Related guide: Football Shot Statistics
Assumptions and limitations
Product details were checked on 14 July 2026 and can change before the review date. Only first-party pages and a non-exhaustive shortlist are shown. Contract terms, trial payloads and service levels control any purchase decision.
GambleAware
GamCare
Gambling Therapy
GAMSTOP