Football Markets

Football markets are in development. Match data, the REST catalog, the XML feed, and the full live lifecycle are available today; market generation and pricing ship next. This page describes the contract they will follow so you can plan your integration.

Multi-outcome by design

Unlike CS2’s single-outcome round propositions, football markets declare multiple outcomes. The market catalogue already supports this — each market lists every outcome with a stable id and a per-locale name template:

<market id="1" name="1X2">
  <outcomes>
    <outcome id="1" name="{home_team}"/>
    <outcome id="2" name="Draw"/>
    <outcome id="3" name="{away_team}"/>
  </outcomes>
  <specifiers/>
</market>

Contract guarantees (planned)

Guarantee	Behaviour
Stable outcome ids	An outcome’s `id` is fixed for the life of the market instance — so an open bet’s selection never loses its binding
Stable specifier set	The specifier set is fixed once the instance is first published (no mid-life mutation)
Settle every outcome	A multi-outcome `<bet_settlement>` lists all outcomes (winners and losers), each with `result` + `void_factor`
Localized names	`name` is a per-locale template; specifier ids resolve to rename-stable, localized names

How it slots in

Football markets ride the same AMQP transport, routing keys, and settlement contract as CS2 — <odds_change>, <bet_settlement>, <bet_cancel>, <rollback_*>. Only the outcome cardinality and the market catalogue differ. If you consume CS2 markets today, football markets need no new transport work. See Market Catalogue and Settlement for the shared mechanics.

Last modified on June 20, 2026

XML FeedUOF/Betradar-compatible REST envelopes for football

Overview

REST API

Live & Feed

Markets

Multi-outcome by design

Contract guarantees (planned)

How it slots in

​Multi-outcome by design

​Contract guarantees (planned)

​How it slots in

Multi-outcome by design

Contract guarantees (planned)

How it slots in