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.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/delta — Event deltas (V1 format)
GET /api/v1/delta — Event deltas (V1 format)
GET /api/v1/deltaV2 — Event deltas (V2 format via V1 path)
GET /api/v1/deltaV2 — Event deltas (V2 format via V1 path)
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 exampleGET /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 themeta.delta_last_id from the previous response. The API returns only events that changed since that cursor.