Skip to main content
GET
Get event changes since a delta ID

Endpoint details

Returns the changes since last_id, one entry per change. Each entry is a raw delta producer envelope: an object with meta and data. meta.type names what changed, a line (moneyline, spread or total, with live and period variants such as moneyline_live or spread_first_half) or a score. data is structured JSON, not a JSON-encoded string, and holds that one change for one event: the current values, a _delta field for each value with its change since the previous update, and the identifiers to apply it (event_id, plus line_id for lines). The field names are V1-style, not V2 market objects. Apply each entry to the event you already hold, and fetch the full event when an entry names an event you do not hold or when meta.reset_required is true. The response is wrapped in a meta object containing the delta_last_id cursor for subsequent polling.

Authorizations

X-TheRundown-Key
string
header
required

Recommended API key request header for new integrations

Query Parameters

last_id
string
required

Delta cursor (36-character UUID). Use 00000000-0000-0000-0000-000000000000 for initial fetch, then pass the delta_last_id from the previous response.

Required string length: 36
sport_id
integer

Filter by sport ID

affiliate_ids
string

Comma-separated sportsbook/affiliate IDs to filter. Common values include DraftKings (19), FanDuel (23), BetMGM (22), BookMaker (7), BetCRIS (9), Pinnacle (3), Polymarket US (31), Circa Sports (32), Bet105 (33), and Heritage Sports (34). Availability varies by sport and market. On V2 event endpoints (/api/v2/sports/{sportID}/events/{date}, /api/v2/events/{eventID}, and their openers/closing siblings), affiliate_ids=0 is a scores-only sentinel: the response keeps events, scores, and status and omits markets and price objects. Other endpoints that share this parameter treat affiliate_ids as a sportsbook filter only.

Response

200 - application/json

Delta updates

meta
object
deltas
object[]