The UK odds API with genuine domestic depth

A product built for UK bettors — an oddsmatcher, an arb scanner, a comparison site, a tipster platform — lives or dies on domestic coverage. The books your users hold accounts with are UK books, and a feed that carries a thin, US-skewed slice of them isn't a smaller dataset; it's the wrong dataset. Depth in the home market is the spec that matters, ahead of global breadth.

Most aggregators treat the UK as one region among many and cover its headline names only. OddsRelay inverts that: the UK is the home market, covered at full domestic depth — the high-street brands, the smaller independents, and the exchanges. Every book we carry is listed openly on the coverage dashboard, with freshness and uptime alongside, so the claim is checkable rather than asserted.

The feed carries 60+ UK bookmakers in one normalised JSON schema, with bet365 included as standard rather than paywalled. Alongside the sportsbooks sit three exchanges — Betfair, Smarkets and Matchbook — supplying the lay prices every back price is matched against, with a rating and qualifying loss already computed. Your product consumes finished pairs, not raw prices you still have to reconcile.

Field references, sample responses and the coverage endpoints live in the public API docs; most teams have a first call returning UK odds within an afternoon. The schema is the same shape across every book, so adding your tenth bookmaker column costs the same as your first.

UK betting has its own grammar — each-way terms, extra places on big-field races, best odds guaranteed, 2up offers, price boosts — and a generic match-odds feed speaks none of it. The feed ships seven feed types: standard, each-way, extra-place, BOG, dutching, 2up and price-boost. Racing markets, the heart of the UK matched-betting and value-betting economy, are first-class citizens rather than an afterthought.

That processing is what separates a UK-ready feed from a raw one. Each feed type arrives already matched to the exchange lay side, in the shape an oddsmatcher or scanner renders directly — the matched-betting page covers what that layer replaces in your build, and why it is usually the year of engineering teams underestimate.

The honest comparison axes for UK work are three: is bet365 present, how deep does the domestic list go, and do prices arrive raw or matched. The Odds API, a widely used raw aggregator, segments by region but does not list bet365 in its UK coverage — our comparison with The Odds API walks through what that means for a UK product in practice.

bet365 deserves its own scrutiny because it is the book UK users expect first and the one no provider can offer officially — there is no public bet365 API. In this feed it is a first-class book across all seven feed types, already matched; the bet365 spoke covers that story in full.

UK coverage is not a launch promise — it is what the feed serves now, on a pre-match polling cycle of roughly three seconds, monitored, with published freshness and uptime. The same pipeline powers a leading UK matched-betting platform in production. For the wider UK data story — market structure, the exchange landscape, who buys UK odds data — see the United Kingdom region page; for per-book detail, the bookmakers directory holds an entry for each operator.

South Africa and Nigeria are on the roadmap as the next regions, and we say so plainly rather than listing them as shipped. If the UK is your market, the shortest route to an answer is to test: a free trial key puts the live UK feed — bet365, exchanges and all seven feed types included — into your own product this week.