What you get
Football is served under its own/soccer/v1/* namespace, on the same transport, auth, and message contract as every other Ticktock sport. If you already consume our CS2 feed, football slots in with no new plumbing — only new endpoints and a wider match-status set.
REST catalog
Matches, competitors, tournaments, and categories — resolvable by id.
XML feed
UOF/Betradar-compatible envelopes: sports, tournaments, competitor profiles, summaries, schedules.
Live lifecycle
sport_event_status drives the match through its full football lifecycle over AMQP.AMQP transport
Same exchange + routing-key layout as every sport — only the sport id differs (
1 = Soccer).The sport → category → tournament → match model
Football follows the provider hierarchy shared across the platform (see Sport model):
The category (country) travels nested inside the tournament — never as a routing-key field. This mirrors the client’s own football model so fuzzy match-pairing resolves.
Identifiers
A match resolves by its SportRadar URN, the bare integer, or our UUID — so you can look it up by whatever id you already hold.
Coverage
Required scope
Football endpoints authenticate with the sameX-API-Key as the rest of the platform. Your key’s sport_allowlist must include soccer. Verify anytime with GET /v1/whoami.
The transport — authentication, AMQP routing keys, settlement, recovery — is identical across sports and documented under Platform. This section covers only what is football-specific.