Skip to main content
V1 delta endpoints accept the optional odds_format query parameter. It defaults to american; the delta fields remain in American-point difference units. See Choose an odds format for details.

Overview

Delta endpoints return only events that have changed since your last request, identified by a cursor (last_id). This is dramatically more efficient than re-fetching all events on every poll cycle and keeps you well within your rate limit. TheRundown provides two V1 delta endpoints:
For new integrations, consider using GET /api/v2/delta or GET /api/v2/markets/delta instead. These V1 delta endpoints are maintained for backward compatibility.
Delta feeds are not a way to remove a plan’s data delay. Use cursor polling only when the API confirms zero-delay access for that key. Delayed or unknown access should repeat narrow snapshots at an interval appropriate to its returned data delay. See Efficient Polling for the V2 market-delta bootstrap rules.

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

Returns events that have changed since the specified cursor, using the V1 line-based response format.

Parameters

Returns the same per-change entries as /api/v2/delta, one per changed line or score, accessed via the V1 path. This is useful while you migrate a V1 polling integration.

Parameters


Delta Polling Pattern

The delta pattern works as a cursor-based feed. Here is the recommended approach:

Step 1: Initial load

Load current state from a V1 events response (for example GET /api/v1/sports/{sportID}/events/{date}) and keep its meta.delta_last_id as your cursor. /api/v1/delta rejects a zeroed-out UUID with HTTP 400. If you only need a cursor, /api/v1/deltaV2 returns the current one for a zeroed-out last_id, with no events.

Step 2: Poll for changes

On each subsequent poll (e.g., every 3-5 seconds), pass the meta.delta_last_id from the previous response. The API returns only events that changed since that cursor.

Step 3: Update your local state

Apply the changes from each delta response to your local data store. Each delta entry contains the full event object, so you can replace your cached version entirely.

Choosing Between Delta Endpoints