V1 REST
GET endpoints that return odds accept the optional odds_format query parameter. It defaults to american; see Choose an odds format for supported values and which response fields change.V1 vs V2 Data Model
Store your key in the
THERUNDOWN_API_KEY environment variable and send it in the X-TheRundown-Key header. Legacy query authentication remains available for compatibility; use header authentication for new integrations. Do not put keys in URLs.Endpoints
GET /api/v1/events/{eventId} — Get a single event
GET /api/v1/events/{eventId} — Get a single event
GET /api/v1/sports/{sportID}/events/{date} — Events by sport and date
GET /api/v1/sports/{sportID}/events/{date} — Events by sport and date
GET /api/v1/sports/{sportID}/openers/{date} — Opening lines
GET /api/v1/sports/{sportID}/openers/{date} — Opening lines
GET /api/v1/sports/{sportID}/closing/{date} — Closing lines
GET /api/v1/sports/{sportID}/closing/{date} — Closing lines
Returns events with the final V1 line data recorded before event start.
GET /api/v1/sports/{sportID}/schedule — Event schedule
GET /api/v1/sports/{sportID}/schedule — Event schedule
Returns the event schedule for a sport with cursor-based pagination. Useful for loading upcoming games, filtering by team, conference, or division.
Parameters
MLB schedule rows include
game_number (1 or 2 for a true doubleheader) and game_type (doubleheader, makeup, or doubleheader_makeup). Both are omitted for ordinary games.V1 Line Structure
In V1 responses, each event contains alines object keyed by affiliate_id. Each affiliate’s line object has:
include=all_periods is used, lines may be omitted or null. Read period-specific data from line_periods, grouped by affiliate ID and then period key: