Skip to main content

What it streams

Metadata about long-term or season-based betting markets (called “futures”), scoped to a futureId. Includes tournament/season mapping, market metadata, timing window, and external provider IDs.

Routing

  • Entity key: payload.futureId
  • Filters: sportIds, tournamentIds, futureIds
  • Access: live vs pregame determined by your apiKey

Payload fields


Example: future metadata

Example: sports future


Notes

  • Odds are streamed separately via the oddsFutures channel
  • Use futureId to join with:
    • oddsFutures (for prices)
    • bookmakersFutures (for status per bookmaker)
  • Most market fields may be null for legacy or non-structured markets