Under 2 hours to kickoff
Odds refresh roughly every minute, the tightest cadence in the schedule, matching when lines move most.
Bookmakers covered
UK bookmakers and exchanges in one normalised odds feed.
Odds API Latency Comparison
Searching for an odds API latency comparison usually means one thing: you have been burned by a provider claiming 'real-time' with no numbers behind it. UK Odds API publishes its actual refresh cadence by time to kickoff, and it is a pre-match polling REST API, not a live trading feed.
Last 2h: ~1 min2-6h: ~3 min · 6-12h: ~5 min12-48h: ~10 min · then slower Cadence tightens as kickoff approaches; it never claims live in-play speed.
Why cadence matters
Teams building odds boards, price alerts, or comparison tables need to know exactly how stale a number might be before they trust it. Vague 'real-time' claims make it hard to size caching, set alert thresholds, or explain delays to your own users. Honest cadence numbers let you design around the actual data, not marketing copy.
Odds refresh roughly every minute, the tightest cadence in the schedule, matching when lines move most.
Refresh eases to every 3 to 5 minutes as markets are less volatile further from kickoff.
Cadence steps down to every 10 to 15 minutes, then hourly further out, matching how slowly early prices actually move.
Scraping a bookmaker site adds parsing delay, layout breakage risk, and inconsistent timing. Polling a documented API on a published cadence gives you a known worst-case delay you can plan around.
The same refresh schedule applies across pre-match odds endpoints, documented in full in the OpenAPI reference.
GET /v1/football/events?schedule_date=YYYY-MM-DD&has_odds=true&per_page=10
GET /v1/football/events/EVENT_ID/odds?package=core&odds_format=decimal
GET /v1/football/events/EVENT_ID/odds/best?odds_format=decimalNormalised JSON with stable bookmaker codes.
{
"event_id": "evt_123",
"captured_at": "2026-09-24T14:02:00Z",
"odds_format": "decimal",
"bookmakers": [
{ "code": "UO004", "name": "Bet365" },
{ "code": "UO018", "name": "Paddy Power" }
]
}What you can build
Once you know the actual cadence, you can build products that set expectations correctly instead of overpromising speed. That covers boards, alerts, and comparison tools that need dependable pre-match data.
Show bookmaker prices side by side with a visible last-updated time based on real cadence.
Open →Flag meaningful line moves using the tightened near-kickoff refresh window.
Open →Compare odds across 34 bookmakers to surface where prices diverge.
Open →Build match pages that refresh on a known schedule rather than guessing.
Open →UK-first odds feed
See the exact cadence and endpoints in the OpenAPI docs before you build.
Bookmakers covered
UK bookmakers and exchanges in one normalised odds feed.
Pricing
Starter, Pro and Business all run on the same published refresh schedule; higher plans add more markets and endpoints.
£79/month
Billed today · no trial
For prototypes and early builds
£149/month
7 days free · £0 due today
For production apps and dashboards
£359/month
Billed today · no trial
For arbitrage tools and revenue-generating systems
FAQ
No. It is a pre-match polling REST API with a published refresh cadence that tightens as kickoff approaches, not a live trading feed.
In the final 2 hours before kickoff, odds refresh roughly every minute.
Scraping adds parsing delay and breaks when layouts change. Polling a documented API gives a known, published worst-case delay instead.
No, the same schedule applies across all 34 bookmakers so comparisons stay consistent.