StrikerDuel

Data licensing

Licence the StrikerDuel dataset

The goal counts are public facts and belong to nobody. What is licensable is the layer on top: a canonical honours and competitions taxonomy spanning six decades and multiple confederations, per-season club and international splits reconciled where sources disagree, and an age-aligned career model with a documented rule set. Delivered as a maintained, versioned feed rather than a file.

Coverage

Players profiled
133
Nationalities
39
Season rows
2,759
Seasons covered
1937–2026
Distinct honours
1,627
Honours awarded
6,393

44 of those honours resolve to a canonical, hand-classified competition id; the remainder are preserved verbatim from source rather than discarded. The most recent verified refresh was Jul 27, 2026.

Schema

One record per player. Ids are stable and versioned from day one: a rename would be a breaking change for anyone who has integrated, so it does not happen.

FieldTypeNotes
slugstringStable canonical id. Never renamed once published.
namestringDisplay name, as commonly rendered in Latin script.
birthDatestring | nullISO date. Drives every age-aligned calculation.
seasons[]object[]Age-aligned season entries: age, season labels, clubs, club and international apps and goals.
seasonLines[]object[]Per-season club rows reconciled to a competition: season, start year, club, league id, league apps and goals, totals.
intlLines[]object[]Per-year international appearances and goals.
totalsobjectCareer club, international and combined appearances and goals.
honours[]object[]Canonical honour id, type, prestige tier, count and the winning editions.
unparsedHonours[]string[]Source strings the taxonomy did not match, surfaced rather than dropped.
warnings[]string[]Validation notes raised by the pipeline for this record.
updatedAtstringISO timestamp of the last verified refresh for this player.
wikipediaUrlstring | nullPublic source the record was compiled from, for provenance.

Sample

A real record, trimmed to one season and three honours. Nothing here is invented: these are the values the feed serves.

{
  "slug": "gerd-muller",
  "name": "Gerd Müller",
  "birthDate": "1945-11-03",
  "wikipediaUrl": "https://en.wikipedia.org/wiki/Gerd_M%C3%BCller",
  "totals": {
    "clubApps": 718, "clubGoals": 656,
    "intlApps":   62, "intlGoals":   68,
    "apps":      780, "goals":      724
  },
  "seasons": [
    {
      "age": 24,
      "labels": ["1969–70"],
      "clubs": ["Bayern Munich"],
      "clubApps": 38, "clubGoals": 42,
      "intlApps": 17, "intlGoals": 21
    }
  ],
  "honours": [
    { "id": "world-cup",  "kind": "team",       "tier": 1, "count": 1,
      "editions": ["1974"] },
    { "id": "ballon-dor", "kind": "individual", "tier": 1, "count": 1,
      "editions": ["1970"] },
    { "id": "bundesliga", "kind": "team",       "tier": 7, "count": 4,
      "editions": ["1968–69", "1971–72", "1972–73", "1973–74"] }
  ]
}

Delivery and terms

A feed, not a file. Active player totals change weekly. Licences are annual and non-exclusive, delivered as a versioned API or a scheduled feed, tiered by application count rather than seats. Field-limited tiers are available: honours taxonomy only, or full per-season splits.

Versioning. The schema is versioned with a published deprecation policy, so an integration can pin a version and upgrade deliberately.

Attribution. A credit link back to strikerduel.com is required.

Corrections, not warranties. Errors that originate upstream cannot be indemnified against. What is offered instead is a correction SLA: acknowledged and triaged on a defined timetable.

Explicitly not included

  • Player images and illustrations. They are not ours to sublicense, and they are excluded from every licence.
  • Player, club and competition trademarks. No endorsement or affiliation is implied or granted.
  • Prose and descriptive text. The licensed product ships data and taxonomy only, keeping it structurally separate from any share-alike source material.
  • Redistribution, sublicensing, or building a competing derivative database.

How the dataset was built is written up in the case study, and the sourcing and editorial rules are on the methodology page.