Products

Schedules API

Canonical teams, competitions and fixtures — the schedule the network agrees on, with the evidence attached to every field.

One answer, with receipts

Several sources can describe the same game, and they disagree in exactly the ways that ruin a Saturday: kickoff moved an hour, field changed, one side spelled differently. The hub resolves those claims into one canonical fixture by source rank, then recency, then confidence — and the response tells you which observation won each field, so "where did this time come from?" is an API answer.

GET /v1/fixtures/{id} — abridged

{
  "start": "2027-04-10T14:00:00Z",
  "venue": { "name": "MoneyGram Soccer Park", "field": "Field 7" },
  "provenance": {
    "start":       { "source": "gotsport",          "confidence": 0.98 },
    "venue.field": { "source": "web:dallascup.com", "confidence": 0.71 }
  },
  "version": 7
}

Reads that stay cheap

Every response carries an ETag. Send it back as If-None-Match and an unchanged answer costs a 304 and almost no bytes — which matters when a team page is polled by every family calendar that embeds it.

Reads are scoped by team, competition or venue — nobody pages the whole database
All instants are UTC; venues carry IANA time zones; date-only fixtures say so honestly with time_status: tbd
Test and live modes on every key; test-mode data lives in an isolated, resettable partition

Built to be embedded

Publishable keys (pk_…) are read-only by construction and safe to ship in a browser. They are what the calendar widget uses; your secret keys never leave your server.

Ready to try it?

Test mode is free and resets on demand.

Start building Read the docs