Coverage API

Soccer odds captured from Hard Rock Bet and Winamax, aligned market-by-market so the same bet can be compared across both books.

Base URL and authentication

https://datarium.top/coverage/api/

Data endpoints use HTTP Basic auth. Credentials are issued per consumer — ask the operator; they are not published here.

curl -u 'USER:PASSWORD' \
  'https://datarium.top/coverage/api/fixtures?day=2026-08-31'

Games

GET /fixtures

{"fixtures": [{
  "name": "Dijon vs Saint-Étienne",
  "kickoff": "2026-08-31 18:45:00",
  "competition": "France - Ligue 2",
  "books": ["hrb", "winamax"],
  "phases": ["morning", "lineup"],
  "rows": 1879, "markets": 141,
  "captured_at": "2026-08-31 11:03:51.734000",
  "lineup_confirmed": false
}]}

books tells you whether a game is comparable at all — ["hrb","winamax"] means both priced it. name and kickoff together address the game in the next call, and must be passed back verbatim.

Markets and odds

GET /fixture

curl -s -u 'USER:PASSWORD' -G \
  'https://datarium.top/coverage/api/fixture' \
  --data-urlencode 'name=Dijon vs Saint-Étienne' \
  --data-urlencode 'kickoff=2026-08-31 18:45:00'

{
  "fixture": {
    "name": "Dijon vs Saint-Étienne",
    "kickoff": "2026-08-31 18:45:00",
    "competition": "France - Ligue 2",
    "books": ["hrb", "winamax"],
    "lineup_confirmed": false,
    "lineup_source": "unknown",
    "event_ids": {"hrb": "992687190473572603", "winamax": "72572050"}
  },
  "totals": {"markets": 141, "selections": 1879, "both_books": 19, "suspect": 0},
  "markets": [ ... ]
}

Market fields

Selection fields

Push a lineup confirmation

POST /lineup/confirm

Each game is captured twice: once in the morning, once near kickoff. The second capture is meant to fire when the starting lineups are published — but the upstream lineup feed is rate-limited during exactly that window, and not every game maps to it, so most captures fall back to a blind timer instead.

If your service already knows lineups are out, say so and the collector captures that game on its next poll rather than waiting.

curl -s -u 'USER:PASSWORD' -X POST -G \
  'https://datarium.top/coverage/api/lineup/confirm' \
  --data-urlencode 'name=Benfica vs Estoril' \
  --data-urlencode 'kickoff=2026-08-31 19:15:00' \
  --data-urlencode 'source=my-service'

{
  "ok": true,
  "signal": {
    "event_id": "5638672854720577792",
    "event_name": "Benfica vs Estoril",
    "kickoff": "2026-08-31 19:15:00",
    "source": "my-service",
    "received_at": "2026-08-31 18:12:32"
  },
  "minutes_to_kickoff": 62.5,
  "effect": "capture on the watcher's next poll"
}

effect tells you plainly what your call will do: capture on the watcher's next poll, none - lineup snapshot already captured, or none - kickoff has passed.

GET /lineup/signals?limit=50 returns recent confirmations and who sent them.

Mapping audit

GET /pairs?status=approved|auto|rejected

Every HRB↔Winamax market pairing with the evidence behind it: how it was matched, how many selections lined up, how often it has been seen, and whether a human confirmed or rejected it. Use it to audit any comparison that looks surprising.

Leagues

Competition coverage is returned in GET /coverage under leagues. Note its own caveat: a 0% overlap figure means discovery missed the competition, not that Winamax does not price it.

Rules for consumers

Known limits

“Both books” overstates comparability. A game can be listed under both books while one of them priced only a handful of markets. Depth is heavily skewed — a US-facing book does not price minor European leagues deeply. Use totals.both_books, which counts genuinely paired markets, rather than counting fixtures.

History has gaps. Collection has not been continuous since inception; some days are partial and at least one is missing entirely. Time-series queries should tolerate holes rather than assume a uniform series.

Two snapshots per game, not a live feed. Each fixture is captured once in the morning and once near kickoff (phases). This is an archive for analysis, not a streaming price feed.